What happened last week - issue #35

This week: AI, Modern Web, GitHub as a CMS and more

What happened last week

Last week was a rollercoaster. I learned that I will speak at WordCamp Gliwice (talk and a workshop) and at Atarim Web Summit. On the other hand, my talk got rejected by JS Nation and WordCamp Europe.

I also spent some time creating some documentation for Astro. A moment ago, my guide about integrating Astro and Statamic went live. Kudos to the Astro documentation team. It’s really amazing to see how quickly they respond and how helpful they are during the review process.

And last but not least - yesterday, I had a chance to take part in a coffee cupping organized by HotAir Cafe. It was really fun to try all this coffee.

Interesting links

The A.I. Dilemma — Tristan Harris and Aza Raskin

AI is right now the hottest topic out there. Not only in development but literally everywhere. And why it can truly be amazing and helpful in many cases, it also has a dark side about which we don’t talk enough.

This video is a great discussion explaining all the potential dangers (but also the benefits).

Rethinking the Modern Web — Oxford Harrison

Oxford really created an amazing sum up of the thing we call the “modern web”. I agree with him that the modern web is constantly battling the problems it created. As a result, our applications are becoming more and more complex.

Automate Screenshots with GitHub Actions — Colby Fayock

Colby created a really fun video about automating screenshots with Playwright and GitHub Actions.

Why we use GitHub as our CMS — Ian Vanagas

Ian explains why at PostHog they are using GitHub as a CMS. It really has a lot of sense. Having a clear history of changes, no additional CMS software and keeping the team more engineering-focused.

Load Balancing — Sam Rose

Sam explained how load balancing works and visualized it in a great way.

Your syntax highlighter is wrong — Jim Fisher

Two very interesting experiments about code highlighting. What would happen if comments would become more colorful, and what if git diff would use more neutral colors than red and green.

I’m not sure in both cases, but I’m far from saying that Jim is wrong. For sure, we got used to the current state, and we prefer to stay in our comfort zone.

---

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