My timeline...

Too many of us use the human brain as the yardstick to measure intelligence. They find it outlandish to imagine a machine that is smarter than us. Just like heliocentrism was considered an offensive idea back in Galileo's time, a machine that beats us in math, coding, or even creativity evokes strong negative emotions.

Most software engineers still underestimate the complexity of the systems we are about to develop in the coming months.

"I should be able to understand the code" Nope, that's not the case anymore. The code is no longer there for you. It's there for a machine that has no trouble understanding it.

"You can always tell by the fingers..." 🤯

Watching pi with Qwen3.8-flash-next on strata churn through 3 PRs simultaneously is quite a sight.

Rotate your nouls, people!

I had quite a few pet projects running. Software that I once built and maybe wanted to revisit later. In light of the current security issues, I have taken those servers offline. Whatever doesn't get maintained around the clock becomes an attack surface. Hobby projects don't justify the attention they require to keep their security up to date. It feels like the end of a more innocent era.

This week’s Black October event has put the final nail in the coffin of the AI-slop crowd. A lot of us, including me, predicted the big security apocalypse would come in the form of vibe-coded applications getting hacked. Non-techies would ignore Lovable’s security warnings and publish an app that would leak its credentials. Reality is quite different. The vulnerabilities and exploits that came to light in the last few days are found in old human-generated slop. Hand-crafted slop. Artisanal, professional, senior Clean Code look-Ma-I’m-doing-DDD slop. This week's We Should Do Something With AI is about how security issues will bring us the dreaded software factory. somethingwithai.substack.com…

Deployments on Railway blocked while the data is compromised. GitHub failing under the agentic workload, causing deployment pipelines to break. DevOps through CI/CD is a struggling paradigm.

We are leaving a naive era in cybersecurity where protection for most of us was mainly a checklist, best practises and keeping dependencies somewhat up to date. The enemy has fully automatic weapons now.

Unfortunately, the hackers got hold of my Jev API keys and were able to spend $0.72 overnight...

PHP, GitLab, OpenCode, LiteLLM, Railway.... Rotating keys today feels like cleaning up debris while the storm is still raging.

Engineers are using GitLab, Jira, Notion, Linear, and GitHub through their coding agents. Nobody is looking at tickets and Kanban board anymore. The days of the webapp UI are over.

When I was a teenager, I hated "sampling". It wasn't real music. It was just talentless people who couldn't play an instrument singing over someone else's song. As I got older, I learned that's not true. Artists use existing sounds to create new music. We're seeing a similar resistance to AI-art. That too will pass.

Will Smith eating spaghetti was 3 years ago... Extrapolating this to 2029 is not good for the stomach. What a rollercoaster!

A long time ago, I worked with a manager who had little understanding of how software development worked. In an attempt to speed up the delivery, they proposed adding a "night shift". Every evening, the "day devs" would clock out, and the night team would clock in to continue coding. Surely that would speed up development? It was a ludicrous, desperate idea by someone who just wanted to get things moving. We had a good laugh about it. One of my agents has just been chewing through a large refactor for over 24 hours now. Turns out the night shift was not a crazy idea. It was just early.

The craziest argument about the Tesla show here is "he won't be able to really ship this" Really? That's like watching an Evil Knievel show and concluding "This won't be safe for commuters"