Code reusability: from classes to containers

What is the right code granularity? I have previously written about reusing functionality [1] in the micro service context and found then that the old aim to optimise code footprint is a metric in need of a good overhaul. Ever since I'm happy that the idea is getting traction: Classes, libraries, applications OOP reuses code … Continue reading Code reusability: from classes to containers

Scalability through client-driven workflows

This post discusses a way to increase a service architecture's scalability by removing any communication paths between services and instead burdening clients with that communication. Bureaucracy in real life is a trade-off between ease of work for the applicant vs. ease of work for officers  In "Les 12 travaux d'Astérix" [1], Asterix and Obelix are … Continue reading Scalability through client-driven workflows

Of Babylonian kings or why technical users in user stories are OK

Every time a technical system impersonates a human in a user story, God drowns a kitten in an agile waterfall.-- Unknown User stories are supposed to advocate the user's view on a system's behaviour. Whatever technical systems which interface with "our" system think or do does not interest us. But why then is it so … Continue reading Of Babylonian kings or why technical users in user stories are OK

The art of copy & paste in programming

Code structures help fit code into your head Every programming course starts with showing a "hello world", moves on to computations, I/O, control structures, data structures and code structures. The necessity for data and code structures doesn't become obvious until one has written a larger programme. Until then (and often even then) it feels like … Continue reading The art of copy & paste in programming