I have had some comparable experiences when living in the UK back in 1998. It was probably one of the most remarkable times in my live and I still think about it with a lot of fondness.
What should we do to handle the constantly changing domain and technical requirements? Patrick Kua talks about some interesting aspects on the architectural level.
In my view a very good (technical) start to using Docker.
Martin talks about various algorithms for lock-free data processing. Worth watching, as always 🙂
Here is another interesting presentation from Martin given at the Code Mesh Conference 2015 in London.
A very entertaining, yet serious talk about what kinds of “projects” there are and why you need different people for them.
A good talk on EDA (event-driven architecture).
Here is a rather interesting video from Martin Kleppmann where he talks about dealing with concurrent changes to data. While the title may sound theoretical to some, it is a topic that probably every developer has come across. And here is also the link to the paper with the algorithm presented. If you are interested in an implementation, check this Github project.
In the closing statement of my post Architects Should Code I said that for me code and architecture are just two ways to look at the same thing. It seems that I am not alone in that perception 🙂 and can very much recommend the video linked in below. I found its start a bit boring, but am very happy, in hindsight, to have not switched away.
Here is yet another interesting video. The title is chosen badly, though, as the content is not really about the future but the history of programming. But on the other hand you need to understand the past, if you want to avoid repeating its failures.