Links

GitHub CEO warns developers to embrace AI or quit, he said on X, referencing new research. The study reveals how AI is reshaping developer roles and workflows.

Once it’s well integrated into our lives, any new technology can be seen as an exchange. We lose something and get something else in return. When we started using our calculator app, we lost the ability to do basic operations by hand, but we got accurate results quickly. After some time, even making a basic addition without it seems like a struggle. I don’t remember the last time I used a map, other than in school when I was a kid and was learning about them. By the time I got my driver’s license, smartphones were fully out, so Google Maps was my navigator. I lost (or maybe even didn’t develop the capacity to navigate with a map in the first place?), but I got instant directions to any destination in return.

Stop vibe-coding blindly! Why reading AI-generated code is crucial in 2025. Avoid security flaws, architectural decay, and knowledge loss when using Claude Code or any other tool.

A clover, a bee, and a break

The title of this post is somewhat misleading. Local-first software rarely needs to be scaled at all.

What AI-optimized schools misunderstand about learning

Learn how AI transforms test-driven development (TDD) from a time-consuming chore into your secret weapon for building robust and bug-free applications.

A study into the workflows of experienced developers found that devs who use Cursor for bugfixes are around 19% slower than devs who use no AI tools at all. One possible takeaway is that AI tools can be harder work than we’re led to believe.

Serious learning requires friction, frustration... and other humans

Why I believe live coding is NOT fair

Writing about the big beautiful mess that is making things for the world wide web.

Native CSS transitions have quietly killed the strongest argument for client-side routing. Yet people keep building terrible apps instead of performant websites.

<h1 id="a-valid-html-zip-bomb"><a tabindex="0" class="anchor" href="/notes/html_zip_bomb">A valid HTML zip bomb</a></h1><p><img src="/notes/res/zip_bomb_file.svg" alt="Illustration d&#x27;une bombe zip" height="150" width="150"></p><a href="/notes/html_zip_bomb"></a>

Recently, I wrote an article about my journey in learning about robots.txt and its implications on the data rights in regards to what I write in my blog. I was confident that I wanted to ban all the crawlers from my website. Turned out there was an unintended consequence that I did not account for. My LinkedIn posts became broken Ever since I changed my robots.txt file, I started seeing that my LinkedIn posts no longer had the preview of the article available. I was not sure what the issue was initially, since before then it used to work just fine. In addition to that, I have noticed that LinkedIn’s algorithm has started serving my posts to fewer and fewer connections. I was a bit confused by the issue, thinking that it might have been a temporary problem. But over the next two weeks the missing post previews did not appear.

Know how good your code needs to be for the task at hand. Start with a rough draft. Try to soften requirements if you can. Don't get distracted. Make small changes. Practice specific skills.