Alex Unger

The new Cluecumber report library version 3.12.0 for Cucumber json reporting is out. This release brings updated dependencies, bug fixes and fresh new features for rerun test scenarios and exception display. https://lnkd.in/evr2-nZR

10

𝗧𝗵𝗲 𝗯𝗲𝘀𝘁 𝗴𝗶𝗳𝘁 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗴𝗶𝘃𝗲 𝗮 𝘀𝗽𝗲𝗮𝗸𝗲𝗿 𝗶𝘀𝗻’𝘁 𝗮𝗽𝗽𝗹𝗮𝘂𝘀𝗲, 𝗶𝘁’𝘀 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸. After my sessions at the International JavaScript Conference Munich, I got the feedback summary this week. Both talks scored really well: 🟩 𝗖𝗮𝗰𝗵𝗶𝗻𝗴, 𝗣𝗮𝘆𝗹𝗼𝗮𝗱𝘀, 𝗮𝗻𝗱 𝗢𝘁𝗵𝗲𝗿 𝗗𝗮𝗿𝗸 𝗔𝗿𝘁𝘀: 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗶𝗻𝗴 𝗨𝗫 𝗶𝗻 𝗦𝘂𝗯𝗼𝗽𝘁𝗶𝗺𝗮𝗹 𝗖𝗼𝗻𝗱𝗶𝘁𝗶𝗼𝗻𝘀 • Quality: 4.67 / 5 • Knowledge: 5 / 5 • Comment: “A bit overloaded with information.” 🟦 𝗙𝗿𝗼𝗺 𝗙𝗿𝗮𝗴𝗶𝗹𝗲 𝘁𝗼 𝗙𝘂𝘁𝘂𝗿𝗲-𝗣𝗿𝗼𝗼𝗳: 𝗦𝗼𝗹𝘃𝗶𝗻𝗴 𝗪𝗲𝗯 𝗠𝗼𝗻𝗲𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 • Quality: 5 / 5 • Knowledge: 5 / 5 It’s always nice to see high numbers; it means the work, preparation, and energy paid off. But the most valuable part was that small comment: “A bit overloaded with information.” I actually love that. It’s true, I tend to pour a lot into my talks because I want people to walk away with something practical. The tradeoff is that sometimes it becomes dense. That single line says more to me than a perfect score ever could. It’s what helps me get better. Feedback like this is 𝘂𝗻𝗱𝗲𝗿𝗿𝗮𝘁𝗲𝗱. Most people don’t realize how little of it speakers actually get after a talk. You stand on stage, share your work, and often walk away without knowing what really landed and what didn’t. When someone takes 20 seconds to write one honest sentence, it gives you a mirror. It shapes your next talk, your style, your pacing, and your focus. So if you’ve ever attended a meetup, workshop, or conference talk, take that moment to leave feedback. Whether it’s praise, confusion, or critique, it all helps. And to everyone who came to my sessions in Munich, thank you. You showed up, listened, asked, challenged, and cared enough to respond. That’s what makes these communities worth being part of. #IJS #PublicSpeaking #Conferences #EngineeringCulture #Feedback #ContinuousImprovement #Learning #DeveloperCommunity

21

3 Kommentare

if you think #Rust is still a niche programming language only for hobbiest, you need to catch up on the news. Ubuntu is replacing the `sudo` implementation with a Rust version. You cannot go more mainstream and security critical than this!

31

1 Kommentar

“I ship code I don’t read”. This is not revolutionary. It has to become the norm with AI coding. 👩‍💻 Human in the loop to read code does not scale with AI generated code. 🤷🏽‍♀️ If AI is writing code, and reading code, does it even need to be human readable? ✅ Focus has to shift to ensuring correctness and completeness of code.

1

Essential SRE Articles: The Essential Knowledge You Need as an SRE by Marcel Koert feels less like a textbook and more like a trusted field guide for engineers working in the real world of Site Reliability Engineering. Written by a practicing SRE, this book speaks directly to the moments that matter most—between incidents, during on-call rotations, and in the quiet minutes after a production fire has been put out. Instead of idealized, Google-scale scenarios, Koert starts with the reality most SREs know well: legacy systems, partial migrations, political constraints, and monitoring that’s never quite perfect. The book focuses on what actually makes an SRE useful—error budgets, service levels, monitoring, capacity planning, disaster recovery, infrastructure as code, and modern reliability design patterns. What truly sets this book apart is its emphasis on human factors. Cognitive biases, communication failures, and decision-making under pressure are treated as first-class reliability concerns, not afterthoughts. The structure is intentionally practical, with short, focused chapters designed for quick reading during a busy day. With an entire section dedicated to AI and modern prompting techniques for SREs and DevOps engineers, this book feels current, honest, and deeply usable. A highly recommended read for anyone serious about building reliable systems—and becoming a more effective SRE. Book link: https://a.co/d/68qhzdf #SiteReliabilityEngineering #SRELife #DevOpsEngineering #TechBooks #ReliabilityEngineering

1

Everyone loves the idea of “move fast and build.” But here is the reality we see with many teams: → Features get shipped quickly, but without long-term planning. → Tech debt piles up quietly in the background. → Scaling becomes painful, costly, and sometimes impossible. At EnqCode, we often help clients untangle this. The most common hidden costs we find are: ・Re-engineering poorly designed modules just to handle growth. ・Fixing security oversights that should have been caught early. ・Migrating from a “quick fix” tech stack to one that can actually scale. Building fast isn’t wrong but building fast without direction is expensive. The smartest teams balance speed with scalability, and treat tech debt as a real cost, not an afterthought. #SoftwareDevelopment #Scalability #CustomSoftware #SaaSDevelopment #Technology #Build #TechDebt #DigitalTransformation #EnqCode

3