Featured
When Coding Becomes Cheap, Experience Becomes Rational Again
For decades, software teams faced a trade-off: build the best experience, or build something affordable. Native applications offered quality and performance, but they were expensive. So the industry optimized for economics. The web and cross-platform frameworks were good enough, and good enough won. That constraint is now shifting. With AI-assisted development, implementation is becoming cheap. Machines can generate working software quickly. What they cannot generate is clarity. Intent, structure, domain models, and behavior are now the real bottlenecks.
The Philosophy of Self-Driving Enterprise Software – Rethinking How We Build Software
Enterprise systems should support people, not the other way around. Technology should extend human capability, not consume it. For too long, software has demanded that people conform to rigid structures, turning productivity tools into digital bureaucracy. AI-supported systems can reverse this. By operating on context rather than sequence, and relevance rather than rigid workflows, they reduce cognitive load and return time, focus, and agency to the people doing the work. This is not just about efficiency. It is about respecting human judgment, preserving meaning, and building systems that adapt to real work rather than forcing work to adapt to systems
Articles
Elephant butt, Software Development and Estimation
Okay, here's an interesting question: what does an elephant butt, software development and estimation have in common? At first thought not really much, but then again they actually have a lot in…
Smart Clients Versus Web Clients - What's the Answer?
For a long period of time every ISV jumped on the browser bandwagon, meaning creating web versions of their existing fat clients. This transition was driven by Google's everything web mantra, together…
Is HTML5/JS really the Silver Bullet for Mobile Applications?
HTML5 and JavaScript seems to be getting a lot of attention and being pushed as the next great set of technologies for write-once-deploy-many for mobile devices. If that crystallizes it would be great…
Native Tooling versus Non-native Tooling
Recently I've been following some interesting discussions on the subject whether to develop native apps for mobile or using cross platform technologies. Let me elaborate what I mean by native apps. A…
Choosing the right tools
Over the course of the last couple of years, I've been working on a lot of different projects where we initially had to make some technology decisions on what development ecosystem to use. By…
The Future of Software Development
It's becoming more and more clear that monolithic applications are going the way of the Dodo. With the general adoption of smart-phones, tablets computers and social network portals users starts…
Essence of being a successful Development Manager?
The above question was sent to me the other day from a former colleague and friend. He was preparing a presentation for heads of product management and product development, and not being an…
Wizards in software are mostly uninspiring solutions to bad design
Here’s a thought maybe even a provoking one, as everyone seems to have reached at the conclusion that wizards in software are good. The general and agreed upon argument goes; that a wizard shields the…
Methodologies, Better Software and Requirements
Methodologies Methodologies are like patterns, best practices, recipes or how-to’s. They describe how to get from A to B. But none of them claims that it’ll lead to better software, whatever better…