The online whiteboard of Kristofer Palmvik
What will happen when we blindly apply Big Agile + premature AI tooling to core health services and patient data? Financial services? Social media and the spread of misinformation? Government infrastructure? Military infrastructure? It’s 2025 and software engineering is the backbone of pretty much everything. But for all its prevalence and influence, most people don’t have the technical literacy to even grasp the basics.
That conversation is what matters. Jira (or Trello, Pivotal, sticky notes on a wall, pick any other etc) is only a good tool when it facilitates those conversations and makes sure that the team has them. If people use the tool to have the conversation thats what really matters. That is the best way your team is going to build shared context.
For us, reverse pull requests boosted code quality, knowledge transfer and therefore consistency. It raised topics for our daily tech-chats that resulted in new conventions being agreed and improved overall design in a way that was non-blocking.
Memorising docker commands is hard. Memorising aliases is slightly less hard. Keeping track of your containers across multiple terminal windows is near impossible. What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well). Lazydocker's goal is to make that dream a reality.
Traditional product teams often follow a linear flow: PM defines, designer mocks, engineers build. But that model breaks down when you're building AI-native products. We’re not designing screens for users to click—we’re building systems that interpret intent and act on it. That changes everything. To get it right, everyone needs to be involved early: product, design, frontend, backend, data. Discovery and delivery collapse into the same loop. Feedback is faster. Outcomes are less predictable. The system learns from use, so you need tight, collaborative cycles to learn with it.
Through experience, we discovered some unexpected long-term benefits of mob programming: reduces the amount of work to do, makes continuous improvement more effective, improves design discussions
Somewhere in the last few months, something fundamental shifted for me with autonomous AI coding agents. They’ve gone from a “hey this is pretty neat” curiosity to something I genuinely can’t imagine working without.
Most of us believe that over the longer term, speed is maximized by operating at a high, but not stupidly high, level of quality. The question is, what is “longer term”?
Sorting alphanumeric data can be tricky! Discover how to use custom collations in Postgres to achieve natural sorting and make your data handling a breeze.
The reason why we do this is that nobody wants to work on a Friday evening. Deploying on Fridays keeps us motivated to make sure our system ready to be deployed at all times, and that is important to us. Having a system that can be deployed anytime allows us to quickly push out new features as well as fixing incorrect behaviour when needed.
5028 links collected between and