TL;DR: I am a Senior Software Engineer. I am confident in C# and JavaScript, but my English needs a refactor. I’m starting this blog to improve my writing, clarify my thinking, and prepare for the next stage of my career.
The Problem As engineers, we are trained that "bikeshedding" (focusing on trivial details) is the enemy of productivity. We optimize for shipping code.
But as I move further into my career, I’ve realized that code is the easy part. The hard part is:
Convincing a team why we should build X instead of Y.
Writing an RFC that doesn't get stuck in comment hell.
Mentoring junior engineers without solving the problem for them.
These aren't coding problems; they are communication problems.
The Solution I admire engineers like Tanya Reilly who use writing as a tool for thinking. I want to do the same.
I’m calling this The Bikeshed because this is my workshop. It’s a place to tinker with ideas, argue about the "trivial" details of engineering culture, and practice the skill of articulation.
What to expect I am treating this site like a sandbox. You will find:
Short musings on engineering headaches.
Retrospectives on technical decisions.
Practice reps as I try to find my voice.
If you are here, thanks for the code review.
Disclaimer: I am using LLMs (Gemini) to help me learn how to write better. If something sounds robotic, blame the bot. If something sounds insightful, I’ll take the credit.