Hello, and why I'm writing this down

I'm Murshid, a software engineer and architect. I spend most of my time at the seam between the two: deciding where the boundaries go, naming the trade-offs out loud, and making sure the systems I build stay legible as they grow past the point where any one person holds the whole thing in their head.

This site is where the projects live, but I wanted a place for the thinking behind them too, the parts that don't fit in a README or a pull request description.

What I'll write about

Nothing groundbreaking, mostly notes from the work itself:

• Decisions I made on a system and whether they held up
• Trade-offs I named out loud before writing code, and the ones I didn't
• Small tools I build to remove friction I keep running into
• Things I got wrong, and what I'd do differently

Why bother

Writing a decision down is a cheap way to test whether it actually makes sense. If I can't explain it clearly here, I probably don't understand it as well as I think I do.

More soon. Thanks for reading.