Finally Good Architecture Documentation
Pragmatic architecture documentation with arc42, AsciiDoc and draw.io: Proven methods for sustainable software development and efficient team communication.
Pragmatic architecture documentation with arc42, AsciiDoc and draw.io: Proven methods for sustainable software development and efficient team communication.
Atlassian's Head of Product on cloud anxiety and tool overconfiguration. Interview with Matt Schvimmer at Team '24.
Establishing a software architecture for a project sounds like a decision for eternity. Why it isn't – and shouldn't be.
Hi, What if…? I must have read this sentence hundreds of times in the last few days regarding the CrowdStrike outage. Everywhere, people are looking for someone to blame. And that is wrong! We are witnessing the classic blame game. It is more important to find someone to blame than to solve the problem. This only fosters fear. An employee of Tom Watson, the founder of IBM, once made a mistake that cost the company ten million dollars. When the man was called into Watson’s office, he was sure he would be fired. To his surprise, his boss said: “Fire you? Not after I just invested ten million dollars in your education.” ~ The Winners Laws by Bodo Schäfer (translated from German edition)
Hi, HashMap? How can HashMap be a topic for the newsletter? Hold on! The topic came to mind because I was in an interview for a client yesterday and spent quite a long time discussing the HashMap. The experience was a bit of déjà-vu. 2-3 years ago, I was heavily involved in recruiting. During that time, I conducted over 150 technical interviews. And from that period, I learned a lot about our industry. First and foremost, we lack seniority and fail to sufficiently develop young developers.