What happened last week
It was a busy week. I’m finishing preparing to record my talks for the Warsaw IT Days - it will be an amazing conference and I’m a bit sad that I will only attend virtually (because I will be in Spain).
Also, I spent some time playing with Flow Launcher and learning how to build add-ons for it. I had a lot of fun building an addon that will search Astro Docs for me. I hope to release it soon.
And I’m testing some things for the upcoming season of the Code and Coffee Show - there will be some minor changes, but the amazing guests and coffee are here to stay :)
Interesting links
What’s new in WordPress 6.5: Font Library, DataViews, Block Bindings, Interactivity API, and much more! — Carlo Daniele
A lot of changes are coming to WP 6.5. I’m intrigued with DataViews and Interactivity API. Kudos to Carlo for summing everything up - it’s a huge release.
Mental Health in Open Source — Anthony Fu
Anthony wrote an essential article about mental health in Open Source. Many of us know how it is - we start with a dream and high hopes and end up with a job we don’t like, but others are counting on us. Anthony mentions many interesting things like the "Iron Triangle" of Velocity, Scope, and Quality.
Code Reviews in a Galaxy Far, Far Away — Hana Klingova
Star Wars archetypes in the code review world - I love it. Also, I’m seeing some dark side vibe in me too.
A syntax highlighter that doesn't suck — Brent Roose
First of all - that’s true that finding a perfect syntax highlighter is difficult. Of course, it all depends on how much can you let go. For Brent it was a critical feature, so he ended up writing his own.
Introducing Nue CSS - A scaleable alternative to Tailwind, BEM, and CSS-in-JS — Tero Piirainen
Tero isn’t a fan of Tailwind CSS - but instead of just writing that Tailwind sucks, he just proposed an alternative. Numbers look OK, but I will have to dive deeper.
Developers Don’t Know How to Ask For Help — Catalin Pit
Great article by Catalin on how to ask for help. It’s crucial to provide all the data, what you tried etc. I think this should be compressed into a checklist form and attached to every GH issue.
Husky: How to automatically format, lint and test before you commit or push — Nico Devs
This cool article explains how to use Husky to enforce some pre-commit rules.
And how was your week? Did you learn something interesting? Don’t hesitate to press the reply button or share your thoughts in the comment section.
Cheers,
Maciek