OVERCODE

It’s getting hard to ignore the stories.

Writing code used to be slow.

After over a year of professional Rust — the books, the articles, the deep-dive conference talks, and a lot of practice — I have a genuine love for the language.

A while back, a salesperson from a well-known AI lab came to visit us.

Twice in a row Recently, in two separate meetings at a large tech company, I watched the same scene play out.

If there’s one topic guaranteed to split a room full of developers, it’s AI.

I don’t know if you’ve noticed, but in our profession, there are two types of people: doers who are too busy doing to talk much about it, and talkers who spend at least as much time discussing what they’ve done as actually doing it.

It’s easy to laugh at other people’s bad AI takes.

History rhymes Over the past few months, we’ve been witnessing a genuine revolution driven by AI.

AI has undeniably started to transform our profession.

In a previous post, I talked about the evolution of developers without really diving into each stage.

Two recent events inspired me to write this post.

You know that person on the team who always has an opinion—even on topics outside their expertise.

AI has evolved dramatically over the past few months.

The other day, I was tasked with figuring out why a particular error was flooding our logs — tens of thousands of occurrences.

The other day, I stumbled upon a piece of Go code that looked something like this: func StringToByteArray(s string) []byte { return unsafe.Slice(unsafe.StringData(s), len(s)) } At first glance, this seemed odd.

We all know that programming languages emerge and evolve over time.

Before I even started my career, I had already written a lot of code.

When you’re starting out in tech, there’s one question that doesn’t get nearly enough attention: should you work for a big company or a startup?

The era of hidden code When I started my career, open source barely existed—and the little that did wasn’t on anyone’s radar.

When bytes mattered When I started in computing, we talked about KiB and MHz.

The other day, I was working on improving some cache code when I stumbled upon something peculiar: a struct member that turned out to be a function.

Evaluating a human being is hard.

The rise and the rust Back in 1995, Java was nothing short of a revolution.

Programming languages have come a long way.

Few sentences are harder to say out loud than “I don’t know”.

The complexity myth There’s a curious belief among developers at large companies: they tend to think they’re solving far more complex technical problems than engineers at smaller shops.

The other day I met a relatively young developer who was talking to me about CQRS.

The brief You’re building a small multi-tenant SaaS product.

While scrolling through one of my favorite newsletters, I stumbled upon an article with a provocative title saying that Sentinel errors were slowing your code down by 3000%.

Google was founded in 1998 to revolutionize search—back when AltaVista and Yahoo dominated with their Yellow Pages-style directories.

There was a time when the all-powerful boss decided everything.

The other day, a young developer asked me what had changed in 30 years of software development.

Something never felt right I’ve always had a problem with technical interviews.

After spending many years working for myself, I’m regularly approached by people thinking about making the leap from a traditional job to freelancing or self-employment.

The spark that started it all Ever since I was a kid, I’ve been passionate about computers.

The other day, a junior developer made an observation: my code seemed to require fewer review rounds and generated fewer bugs than average.