This idea reminds me of my early days as an IT Analyst in Brazil. We didn’t have automation or fancy pipelines, but the best projects happened when two or three of us sat side by side, arguing over every decision, and writing code for problem-solving. The difference now is the AI and scripts to handle the routine, but the human focus hasn’t changed much.
Wow Kacper this is such a brilliant piece. I’ve seen how context-switching in larger teams kills momentum, and your emphasis on pair programming and shared mental models feels like a practical antidote.
One angle I’d love to explore further is how you onboard a trio to align their mental models so quickly, especially when team members might come from different technical backgrounds. In my experience, even small teams can stumble if assumptions about the problem domain aren’t fully synced early on. What techniques have you seen work to get that shared context airtight from day one?
This idea reminds me of my early days as an IT Analyst in Brazil. We didn’t have automation or fancy pipelines, but the best projects happened when two or three of us sat side by side, arguing over every decision, and writing code for problem-solving. The difference now is the AI and scripts to handle the routine, but the human focus hasn’t changed much.
Wow Kacper this is such a brilliant piece. I’ve seen how context-switching in larger teams kills momentum, and your emphasis on pair programming and shared mental models feels like a practical antidote.
One angle I’d love to explore further is how you onboard a trio to align their mental models so quickly, especially when team members might come from different technical backgrounds. In my experience, even small teams can stumble if assumptions about the problem domain aren’t fully synced early on. What techniques have you seen work to get that shared context airtight from day one?
I think you've just given me an idea for a follow up article 😄 stay tuned!
Nice😂 Looking forward to it!