Hi, I’m a senior developer and team lead working mostly on the backend with some frontend mixed in.
I’ll be honest: college prepared me for some things, but a lot of what I know now I learned after, on the job, through trial and error, and the occasional codebase that made me want to close my laptop and never open it again. There were concepts I wish someone had introduced me to earlier — not in a textbook way, but in a real, practical, this-will-actually-matter-to-you way.
That’s what this blog is. A series of introductions to the ideas, patterns, and practices that have shaped how I think about software — things I’ve picked up over the years from experience, from great teammates, and from books like John Ousterhout’s A Philosophy of Software Design, which genuinely changed how I write code. I want to do something similar here, but from my own perspective.
The format is simple: each post introduces one concept. Meet Software Design. Meet Complexity. Meet Abstraction. Some concepts will get a follow-up that goes deeper into practice — how to actually apply the idea in the code you write every day. The goal isn’t to be exhaustive — there are textbooks for that. The goal is to give you a foothold, an honest introduction to ideas that took me longer than they should have to discover.
If you’re earlier in your career and still figuring things out, I think you’ll find something useful here.
Top comments (0)