Entwicklungspraxis
November 23, 2024
Interview: How Atlassian Responds to Cloud Concerns and Over-Configuration of Tools
Atlassian's Head of Product on cloud anxiety and tool overconfiguration. Interview with Matt Schvimmer at Team '24.
Marcus HeldEntwicklungspraxis
June 25, 2024
HashMap
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.
Entwicklungspraxis
May 22, 2024
Agile
Hi, Dave Thomas never tires of mentioning that “agile” is an adjective - and not a noun. It is not capitalized. The legendary document we have been referencing for nearly a quarter of a century is not called “The Agile Manifesto.” It is called the “Manifesto for Agile Software Development” . 👈 Agile is not something that can be bought. The manifesto describes how to develop software in an agile (as an adjective!) manner. It does not describe a product.
Entwicklungspraxis
May 3, 2024
GitOps, SRE, DevOps - A Look Back and into the Future
Hi, Ten years ago, most companies were still dealing with manually managed infrastructures. Today, many medium-sized businesses still find themselves in the same situation. But that comes at a cost - and I’m feeling it right now. The Ghosts of Differences It’s astonishing how often we chase ghosts simply because our environments differ. This ranges from obvious things like available CPU or RAM to subtler issues like different kernel versions or configuration disparities in applications. It gets especially tricky with external application servers, where configuration files are spread throughout the system and can easily drift apart.
Entwicklungspraxis
April 24, 2024
Scrum Is Not Agile
Hi, In one of my client projects, we reflect on our working methods. Like most mid-sized projects out there, Scrum is used here too. But we have a few problems: - Sprint goals are never met - Not a sprint goes by without a new task coming in from the side - Estimations are regularly far from reality - Collaboration with other external parties is partially not integrated - … I can certainly think of more examples