The Course Says Your Team Is Doing It Wrong
You come back from a two day course on service design full of energy. One slide is still in your head. Each service should own its own data, and ser…
Latest Programming news from Tech News
You come back from a two day course on service design full of energy. One slide is still in your head. Each service should own its own data, and ser…
The decision is announced as good news. Your skills are in demand, so from next month you will spend half your time on the payments team and half on…
An engineering team can have experienced developers, a clear backlog, and regular sprint meetings while still struggling to ship. Sometimes the miss…
Part of the "How to bring order to a project" series — the people track. It comes after infrastructure and architecture not because it matters less,…
You explained it clearly. They still did not get it. Your instinct in that moment is to say it again, slightly louder, with the same words. That alm…
We see it on our professional feeds every single day : an election result announced, a campus lead appointed, or a post thanking mentors for a new t…
You can be the smartest person in the room and still get passed over. Not because the work was bad. Because no one understood it. Here's what took m…
AI made writing software cheap. That is the obvious story. More code, more prototypes, more pull requests, more “I built this in one afternoon” mome…
This is the first of a 3-part series on human-agent teamwork. In part one (this article), we'll cover "single-player" mode, in which team members ru…
We’ve all been there: a senior developer confidently expounds on their expertise, yet the codebase seems to have a mind of its own. Sometimes, it's…
thesis going alone is faster in the short run, but working with people is what produces durable, well-tested decisions. the hard part is admitting t…
Your team's code review process was designed for a world where a developer wrote every line. In that world, a PR with 200 lines meant 200 lines of h…
Every engineering team has two codebases. The first is the one in your repository — versioned, reviewed, deployed. The second lives in your engineer…