The Future of Programming Systems - four thoughts
Last week I gave a 20 minute mini talk at M&I Partners in Zeist about the Future of Programming Systems, and how the work of architects and engineering teams will grow closer together in the future. I'm completely obsessed by this topic so I'm excited! Here is that talk expressed in a blog post, slightly modified based on some feedback and new thoughts.
Ok! Thank you for inviting me and sorry for not keeping to the original format as requested. I proposed this idea instead and it was accepted, so in part Matthijs (the organizer) is to blame and I hope it is OK with all of you as well ;)
When cycling here, I realized I needed to make a last minute change and added "Systems" to the title. I believe that limiting ourselves to the activities of the programmer is too narrow, and we should have solutions that involve everyone who is in the lifecycle of software. So it's about the System and that includes the designers, architects, users, database administrators, operators, and yes, also developers.
Your request was to talk about one of the classic texts of the software engineering / software architecture field. Now I didn't pick a classic, and I didn't pick a book. Instead I picked this semi-random blog post I found on Hacker News a couple of years ago.
