It’s not artificial intelligence. It’s intelligence, augmented.

Stop whining about robots taking over and go raise a robot army.

coding != programming

If you try to "learn then teach", you'll either stop learning or never teach.

Good code is deletable—trash it without tears, iterate fearlessly. Build solutions, not legacy liabilities.

The Github mobile app is better for reviews than the website🤦‍♂️

(That’s not a W)

Can’t believe this isn’t obvious:

A ‘hey’ doesn’t tell me if your concern is more important than what I’m doing.

Get your head out of your ass, respect my time, and add some context to your first message.

In the real world, there’s no culling—things don’t vanish just because you look away. Your model of reality will always be incomplete, but ignoring that won’t change it. Keep refining, not retreating.

We barely understand the neural networks we built, yet we think we can decode nature’s. Now that’s ambition.

You know that feeling of discomfort… yeah that’s called “learning”.

Clojure is dynamically typed but somehow not chaotic. Why does it actually feel… good? Is it opposite day, or am I finally losing it?

You know the story—$1 to tap, $999 to know where to tap?

That’s exactly how you should think about AI in engineering.

Found the besttt way to describe AI in tech

Great engineers know: just because you can build it doesn’t mean you should.

1/ After building several AI features (and yes, making my fair share of mistakes), here’s the process I keep coming back to.

It’s not fancy theory—it’s a practical, iterative workflow blending coding with hardcore QA. 👇