Archive
Why Software Development Is Not Assembly-Line Work
Tell Me Why My Design Will Fail
The Hidden Economics of Development Approaches - Framework driven vs Domain driven
The Duplication Paradox: How to Master Maintenance and Expedite Knowledge Transfer
How to Apply Object Orientation to Non-Entities: Implementing the Interaction in Your Business Model
Steve Jobs’ Lesson for Software Architecture: Experience First, Technology Second
From Continuous Inspection Back to Continuous Integration: Amplify Your Development Teams
The Hidden Costs of Treating Software Development as Assembly-Line Work
Why Enterprises Should Rethink JavaScript Frameworks — and Look at GWT Again
Why GWT Remains the Most Coherent UI Framework for a Java Backend
The Difficulty of Designing IT Architecture: Lessons from the Boat Joke
Keep Tech Debt Below 10% Is Easy — Here’s How
From Low-Code to Full-Code: Task-Oriented vs. Thought-Oriented Teams in Software Development
Object-Oriented Development in Practice: Modeling System Responsibilities
The Toyota Way and Software Development
Quality in Software Engineering: It's Not What You Think - Part 8: Ignoring the Boat
Seeing the Boat – Part 7: Unlocking the Hidden Power of Domain Knowledge
When Functional Pipelines Meet Domain Objects - Part 6: An Example
Enterprise Frameworks vs. Enterprise Software - Part 5: The Semantic Shift and Its Impact
Overcoming Resistance – Part 4: Recognizing the Japanese Boat in a Dutch World
Coping vs. Improving in Software Engineering - Part 3: The Path to the Japanese Boat
The Intertwinement of Science and Engineering in Software Development - Part 2: Discovering the Japanese Boat
Why Development Speed Defines Software Quality - Part 1: Lessons from a Rowing Team

