Code Saiyan

Sign in Subscribe

Software Development

The craft itself — architecture calls, technical tradeoffs, the decisions that seemed small until they weren't. This is the closest thing to a workshop floor on this blog: less opinion, more "here's exactly how we built it and what I'd change."

📚 Pitfalls & Anti-Patterns: A Glossary for Engineers, Managers, and Product People

📚 Pitfalls & Anti-Patterns: A Glossary for Engineers, Managers, and Product People

A friendly glossary of common traps, anti-patterns, and bad habits that creep into engineering, product, and management work—so you can spot them (and avoid them!) next time they show up.

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.

Make the Backlog Work for You, Not the Other Way Around 🪵

Make the Backlog Work for You, Not the Other Way Around 🪵

A backlog is not a to-do list, a feature dump, or a trash bin of ideas. It’s a communication tool. If it’s not reflecting user value and team focus, it’s working against you. Here’s how to fix that.

🧠 We Want Better Resources for Knowledge Sharing

🧠 We Want Better Resources for Knowledge Sharing

Documentation is one of the most valuable and neglected parts of any engineering org. If you're going to invest in it, make sure you're doing it right—without turning it into another pile of tech debt.

From Critique to Commit: What Graphic Design Taught Me About Writing Code 🎨🧑‍💻

From Critique to Commit: What Graphic Design Taught Me About Writing Code 🎨🧑‍💻

What do design and software engineering have in common? A lot more than you'd think. Here's how lessons from my graphic design career made me a better coder—starting with how to take critique, simplify solutions, and stop overworking your ideas.

What We Weren’t Doing: Takeaways from Agile Training

What We Weren’t Doing: Takeaways from Agile Training

Our agile training wasn’t mind-blowing—it was a mirror. We weren’t doing the basics: real planning, clear stories, realistic commitments. This is a reflection on the fundamentals we skipped and the lessons that still stick with me today.

✅ Start Simple: Why You Can Safely Make Assumptions When Building Web Applications

✅ Start Simple: Why You Can Safely Make Assumptions When Building Web Applications

Most web development isn’t complex—it just mirrors how we already live. Focus on conversations, things vs. events, and building value fast. Here’s why it’s safe (and smart) to make assumptions when building apps.