Tag

#Software Engineering

Software engineering is what programming becomes when the code has to survive contact with users, time, and other engineers, and these posts are about that transition. I write about architecture and the trade-offs it encodes, testing as a discipline rather than a metric, code review as a site of mentorship and politics, and the organizational patterns that let teams ship without burning out. The pieces here cover the unglamorous core of the profession, estimation, incident response, technical debt, on-call, the work that does not demo well but determines whether a system stays standing. Software engineering is not just writing software. It is operating it, maintaining it, and deciding, often under pressure, what to build next and what to leave alone.