Frameworks and platforms promise to raise productivity by removing technical complexity. But it’s the technical aspects that interest developers, much more than domain aspects. This leads to a dynamics where peak productivity with a given technology is never reached, because developers already look for the next framework or platform.
The slides from our talk at BATBern, focused on « event-driven architectures ».
A collection of articles about software engineering that influenced me.
A description of the 6 core responsibilities in any team, as well as the actual repartition across members for common team structures.
This books presents stories that explain how memory works. It made me realize that each person has an individual memory, not only in terms of content, but also how it operates.
In the book Drive, Daniel Pink argues that people are motivated when they find purpose, mastery, and autonomy in their work. I liked this perspective.
It's easy to get going with new software technologies. But a deep understanding of their strength and weaknesses takes a lot longer-even decades.
Stephen Denning characterizes agile management with thee laws: the law of the customer, the law of the small teams, and the law of the network. I mostly agree.
The book Stuff Matters will make you look at the materials around you differently-more curious and more appreciative. A nice read.
It's time to rethink the development process with teams that are accountable for quality.