Code Saiyan

Sign in Subscribe

Engineering Best Practices

Not the sanitized version from a conference talk — the version that survived contact with a real deadline. What holds up, what's cargo cult, and what only works if you squint and ignore the incident channel. Practical over pristine, every time.

🧮 Part 3: In Bots We Trust

🧮 Part 3: In Bots We Trust

A teammate told me he trusts a pull request more now that it's passed his review, plus a couple of agents built to catch what he might miss. Three layers of review sounds like safety. It might just be a receipt for a problem nobody fixed.

You're Not a User. You're a Cron Job.

You're Not a User. You're a Cron Job.

Most "automated" systems aren't. They're load-bearing people wearing a workflow disguise. And AI is just the latest version of the same compromise we've been shipping for years.

🪐 The Man Who Built Mars One Slice at a Time

🪐 The Man Who Built Mars One Slice at a Time

A founder wants a civilization on Mars. He didn't build it as one project — he built it as ten, each one fundable, sellable, and provable without the other nine. Most engineers can't do that with a single sprint.

Stop Flinching: Engineering Built a Culture That Can't Take a Punch 🥊

Stop Flinching: Engineering Built a Culture That Can't Take a Punch 🥊

Engineering optimized so hard for avoiding pain that it forgot how to take a punch. The result isn’t safety — it’s paralysis. And with AI mid-swing, flinching is the one thing you can’t afford.

Maximum Impact, Minimum Effort: The Art of Productive Laziness

Maximum Impact, Minimum Effort: The Art of Productive Laziness

The best engineers are “lazy”—they automate everything, use AI to the fullest, and refuse to overcomplicate. They’re not cutting corners—they’re cutting waste.

Why I Love Pull Requests (and How You Can Too) 📝💬

Why I Love Pull Requests (and How You Can Too) 📝💬

Pull requests aren’t just for catching bugs — they’re for leveling up your team. Here’s how to make the most of them (and avoid common PR pitfalls).

Your Code Isn’t a Masterpiece — It’s Just Design

Your Code Isn’t a Masterpiece — It’s Just Design

Some engineers treat their code like art — striving for perfect form, debating aesthetics, and nitpicking endlessly. But code is design, not art. Its value comes from function, not form. Here’s why adopting the right mindset helps your team ship better software — faster.