The bottleneck in software engineering has shifted from typing to understanding. As AI handles implementation, engineers who thrive will be those who recognise patterns, curate guardrails, and connect technical decisions to business outcomes.
AI is making the knowledge side of consulting cheaper by the day. Teams still avoid the legacy system. The gap is not expertise. It is the structural courage to act on what everyone already knows.
AI has removed the junior work that used to build software engineers. Seven other industries faced the same disruption and didn't agree on an answer.
The fastest way to learn agentic development is to stop studying it: move in, extract repeatable patterns into skills, and reflect to compound.
Technical debt used to justify meetings, trade-offs, and dedicated sprints. AI has changed that. Cleanup is now fast, cheap, and continuous. Teams that stop debating and start fixing unlock faster delivery and better outcomes.
Agile was supposed to free us from bureaucracy. Many teams just rebuilt it with better branding. Now, AI-driven development is forcing the uncomfortable question: Were we ever truly agile, or just managing slow feedback loops?
LLMs are built for conversation, not incantations. The value isn't in your opening message, it's in the back-and-forth: clarifying, correcting, refining. Iteration is cheap. The conversation is the work.
A company should have a vision, but a product should also have one. A product vision may sound like something large corporates work on. It may sound like a waste of time. However, a good product vision helps your team make the right choices while building your product.
Listen to this new Pulse podcast episode on technical debt where Jonas and Andreas discuss managed vs unmanaged debt, legacy code, code rot and give some tips on how to work with technical debt in any given circumstances.
Teams of all experience levels can improve their way of working, but only if they take a moment to retrospect.
Do you deploy every day? Your team probably should. Here's why.
It’s pretty evident that a startup in 2024 faces unique challenges that just haven’t existed in other years. Every entrepreneur knows that they
Every time I work on code with someone I haven’t worked with before, I end up having the same conversation. It usually starts when
I saw an interesting heuristic regarding habits recently but I couldn’t find the source anymore. Bear with me while I paraphrase a bit. If
I started a greenfield project this week. I knew it was coming after one of our product managers told me about it during lunch a
