@johntcosta
Software Engineer focused on shipping value in the form of code that is easy to read, maintain, and extend.
Nothing here yet.
Nothing here yet.
Apr 28 · 6 min read · There's an assumption engineers pick up early. The way you create value is by shipping something into the product: a feature, a fix, an improvement to something users see every day. That's the roadmap, that's the sprint board, and that's where engine...
Join discussion
Apr 21 · 11 min read · You finish your code change, go through several rounds of self-review and testing, fix issues, and get CI passing. You have a polished piece of work that's ready to go. You put it up for review, and nothing happens. Maybe for several days. You ping t...
Join discussion
Apr 15 · 5 min read · My first contribution in this run was to Owncast, a self-hosted live streaming platform written in Go. I had never used it and I had never written Go. I found an issue, pointed Claude Code at it, and it implemented a fix. I spun up the app locally an...
Join discussion
Apr 12 · 3 min read · A few years ago, I was reviewing code from dozens of developers across our team. One pattern I saw constantly: a dev would need a new API endpoint, so they'd open an existing one, copy the whole thing, rename the route, swap out the model, adjust the...
Join discussion
