Last week, I started to post some photos to my photos section. Couldn’t make much time to photograph anything new, as we are in the midst of a very urgent client project, but looking forward to have this little space of mine to post my photos to in the future.
Also last week, I finished reading “How to Make Friends and Influence People” which I found pretty mediocre for all the hype it gets.
Oh, and I bought a ticket for WordCamp Europe 2023 in Athens this June!
⛓ Chain of tools
Another great post by Jeremy Keith. Haven’t read the post he referred to, but his conclusion that the ratio of what you are expected to know as a frontend developer is out of whack totally resonates with me.
That doesn’t seem right. We should change it.Jeremy Keith – Chain of tools
To be honest, this is one of the reasons why I’m so happy to be self employed rather than on the “open market” for a dev job. Our clients are interested first and foremost in their business and they hire us to solve a problem they have or drive some result and trust us to know how we are doing it. The last thing they care about is which tech stack we use. I cannot remember a single time we had to argue or even explain the decision to abstain from frameworks and building things with native web technologies. It’s just quite literally none of their business.
🖥 Browserslist visualized
If you are using
browserslist to autoprefix your CSS styles, chances are you are adding unnecessary stuff to your stylesheets. This site displays visually what the statements like
latest 2 versions etc. exactly mean and how they translate to the actual browser’s market shares.
I just played around with it for a bit and realized that we were using statements in at least two projects which added prefixes for browsers that are completely irrelevant today. One of the projects I tested was very simple with only 27 KB of CSS, and it came down to 25 KB (or: ~ 7.4 %) when I removed those unnecessary prefixes.
📜 A walk-through of layout classes in WordPress 6.1
This post covers the layout classes used by the WordPress Block Editor and what they are doing, which of them you could/should use to customize things and which of them you should avoid using if you care about them working in the future. We definitely had it more than once that a WordPress update broke style changes we did by targeting CSS-classes directly.
✉️ A letter from WordPress’ Executive Director, 2022
WordPress will celebrate its 20th birthday this year. Josepha Haden Chomphosy – the executive director of the project – took a step back and answered the question “Why WordPress?” for her and also looked back at the last year(s) and into the future of WordPress. It’s a great reminder of why the ideas of open software are so important, today more than ever.
… open source provides protections and freedoms to creators on the web that should be a given. There’s an extent to which the idea of owning your content and data online is a radical idea.Josepha Haden Chomphosy
She also briefly touches on what’s next for the block editor, which will focus on things like collaboration in Phase 3 of its development.
🤟 Extremely Hardcore
A pretty long read about the absolute shit show that happened at twitter after Musks’ takeover. I still wanted to believe that at least some innovations will happen faster under Musk, but with an $8/month blue checkmark being the most innovative thing on the horizon, maybe that was too much wishful thinking. You find me on Mastodon, if you look for me.