I’ve previously written about that I think having domain knowledge as a software developer is tremendously important, and really helps you be effective in your role. As I currently work with carbon emissions and carbon accounting at Climatiq, I figured I’d put together a little reading list of what to read in this space if you’re a software developer / software engineer looking to get a little…
Something that I think is often overlooked by many software developers is the value of domain knowledge, i.e. understanding the industry you’re in and the mindset of the end-users of your software1. Depending on how large systems you’re working with, you might have users of your software module, and those might have end-users. The distinction can get fairly blurry in large-enough systems, but…
I’ve never really been too keen on many of the US tech giants. I deleted my facebook back in 2019 (and shamefully re-created it again last year, to participate in a few groups), and I X’d Twitter back when it changed name.
I’m trying to rely less on US services & tech, and I’m using a few hours every Sunday to migrate. I’ve mentioned why I want to do this migration in the first part of this series.
I’m trying to rely less on US services & tech, and I’m using a few hours every Sunday to migrate. I’ve mentioned why I want to do this migration in the first part of this series.
I’ve written quite a bit about pull requests before - covering everything from how thoroughly you should review a pull request to strategies for avoiding being blocked by waiting for reviews and making your PR faster to review. This post builds on those, focusing specifically on what I do when reviewing PRs.
Caveat: While I consider myself a product-first engineer with solid product skills and an academic background partly founded in product design and UX, I have never worked as a full-time product manager. My experience only comes from “the other side of the table”, i.e. working with product managers as an engineer.
I recently came across an integration test that demonstrates what I believe is an antipattern. This particular test was consistently failing at the start with a “Unique constraint violation” in the database when calling the createUser function.