Michael Schmidt-Voigt

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

🚀 Today in Berlin at Agile meets Architecture: Kenny (Baas) Schwegler and Evelyn van Kelle are presenting: “Debiasing Your Software Design Decision-Making” 👇 https://lnkd.in/d6Zb_NuH Are your software design decisions driven by bias or by deliberate choice? Kenny and Evelyn invite you to move from a reactive, bias-driven approach to a deliberate, resilient, and more effective design process. This talk applies cutting-edge research from behavioural economics directly to software architecture and development, with or without AI. 🎯 What you’ll take away: - Move beyond awareness of biases - A practical five-step checklist to systematically ‘debias’ your design decisions - Tools to build better software and better decision-making habits across all your technical work. ✨ Plus: don’t miss the chance to continue the experience in person at the Collaborative Software Design Workshop in Amsterdam, led by Kenny and Gien Verschatse. 👇 https://lnkd.in/dvzA-ZiR

9

🎙️ New episode with Sebastian Gerhardt is live. In this episode of Build by People Leaders, I speak with Sebastian Gerhardt, founder of Flee, about improving developer experience in modern software organizations. One key idea: Developer productivity cannot be measured by output alone. We explore: • Why output-based metrics often fail engineering teams • How organizational structure and team culture shape performance • The role of psychological safety in high-performing teams • How feedback systems and survey-driven insights reveal hidden friction • Engineering leadership in remote and distributed environments For CTOs and engineering leaders, this conversation offers practical insights on identifying friction points, fostering open communication, and building resilient, high-performing teams. 🎧 Listen here: https://lnkd.in/dKV3ZtFW

3

CSS Advent Calendar - Day 9 – Container Queries Container Queries are the feature we missed for years. With them, components become truly independent – no longer oriented to the viewport, but to their own context. This fundamentally changes the architecture of frontends. Responsive design becomes more local, modular, and scalable. Container Queries are not just another feature. They are a turning point. #CSS-Advent-Calendar #CSS #Web-Development https://lnkd.in/e_dZU97d

1

1 Comment

☕ Is Java your cup of coding? We’re back with another Java meetup — this time pouring three freshly brewed talks from top beans (a.k.a. speakers). 🎤 Smithy in Java – a metamodel for your distributed system  Martin Schmied & Michal Janoušek will show how Smithy models can unify clients, servers, and docs — plus how to keep APIs discoverable and future-proof.  🎤 Developing K8s Operators, and Why to Do It in Java  Jakub Čecháček explains why Go isn’t the only option for building Kubernetes operators. You’ll learn about the Java Operator SDK, when it makes sense to use it, and why Java can be a great choice even when Go is not a barrier. 🎤 Structured Concurrency in Java 25 – a smarter way to load data  Jakub Vavrik explores how Project Loom and Java 25 make concurrency cleaner and safer with virtual threads, scoped tasks, and error handling that just works. 📅 October 16, 6 PM  📍 Sky office, AFI Butterfly, Karlín  Book your spot on Eventbrite https://lnkd.in/eHhjhp4W Come for the code ☕, stay for the community 🥮

58

2 Comments

“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

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 Comment

🎬 Throwback time! 🕰️ At our last Angular Vienna meetup, Adrian Romański walked us through why accessibility should never be an afterthought—and how it’s directly tied to long-term technical debt. In his talk "Accessibility Driven Development – Start with A11y, Stay Ahead of Tech Debt", Adrian shared the story of a developer and a tricky menu component. Through live refactoring, he showed how much effort it takes to fix accessibility issues later—and how much smoother things go when you build with A11y from day one. ▶️ Watch the full talk here: https://lnkd.in/dTtFHKFP Thanks again to Adrian for the awesome session—and to our amazing community for packing the room and showing up with great questions! 💛 #AngularVienna #Angular #Accessibility #A11y #TechDebt #Frontend #Community

3

⚡ Slow test suites drain focus — and they don’t have to. In this session, Sebastian Bergmann shows how smarter test design and targeted optimisations can dramatically speed up your PHPUnit runs. You’ll explore approaches that keep pipelines responsive, reduce waiting time, and bring testing back to being a productive part of your workflow instead of a bottleneck. IPC | 📍 Berlin | 📅 June 8 – 12, 2026 🎓 All about the session: https://lnkd.in/dwXYNqCu #IntPHPcon #PHP #PHPUnit #Testing #Performance #DevOps

9

3 Comments

🛠 Is software craftsmanship still relevant? This week on Modern Software Engineering, Emily Bache reflects on the last great idea from the software craftsmanship movement - and why it still matters today. ✅ Clean code vs. fast delivery ✅ Idealism vs. practicality ✅ Professionalism in a changing landscape If you care about writing better code and being a thoughtful developer, this one’s for you. 🎥 Watch now: https://lnkd.in/eWz2udEX #SoftwareEngineering

2

Your frontend feels slow — but you’re not sure why? 🚀 In his Frontend Performance Workshop, Peter Kröner shows you how to truly understand what’s happening under the hood of the browser — and how to fix performance issues the right way. With practical tweaks you can apply immediately! You’ll dive deep into: 🔺 How browsers parse, execute & render HTML, CSS & JS 🔺 Reading and understanding flame charts 🔺 Render-blocking CSS & JS pitfalls 🔺 JS engine internals & just-in-time compilation 📅 Monday, June 8th, 26 | Webinale Web Week |📍Berlin 🤓 All about the workshop: https://lnkd.in/dMFvYjsj #webinale #Frontend #WebPerformance #JavaScript #CSS #WebDevelopment

1

Wanna learn more about the defer block? 💡 💻 During this year’s Angular.love Spring Camp, GDE Enea Jahollari gave a talk showing @defer from a slightly different angle. In this talk, Enea presented real-world examples that demonstrate the need for the defer block in Angular. Watch if you want to learn: 🔹What are the @defer triggers 🔹How to break the defer block 🔹How to optimize it Watch iit here: https://buff.ly/Ye2U9pf #angular #deferblock #angularlove #frontend

87

🚀 Two days before WhatTheStack kicks off, I’m running a crash course in building apps that survive the real world. Real-World React: The Architectural Playbook for Performance, Resilience & Scalability is built around React and Next.js as our shared language, but it’s not exclusive. I’ve had Vue, Svelte, and Angular devs attend, and most of the concepts we’ll cover are framework-agnostic and apply to any modern frontend stack. We’ll dig into: - Architecture patterns that implicitly boost performance - The real story behind React reconciliation (and anti-patterns to avoid) - Resilience engineering for modern frontends - DORA metrics and delivery velocity at scale - Building post-deployment confidence so you can ship without fear This isn’t about pixel-perfect UIs, it’s about patterns, decisions, and trade-offs that keep apps fast, resilient, and scalable when they’re serving millions, not just running locally. 🎯 If you work in frontend and want to level up your architecture game, this is for you.

5

🥘 TypeScript can be a feast. Or a food fight. On today’s #GOTOpodcast, Stefan Baumgartner joins Peter Kröner to serve up lessons from the TypeScript Cookbook. Instead of cramming in every advanced feature, Stefan shows why the best devs keep it simple: 🍴 Use type annotations only where they count 🚫 Skip enums when cleaner alternatives work better 🏗️ Know when classes help—and when they just get in the way 🔍 Focus on what’s happening behind the scenes to make smarter choices 🎧 Listen in: https://lnkd.in/g_UDEnR

7

1 Comment

⚡️ Framework fatigue is real. But what if 2025 is the year you break free? At iJSCon Munich, Stephan Rauh shows how to move from framework frustration to frontend freedom — leveraging modern HTML + Tailwind CSS for lean, beautiful apps, while avoiding the common pitfalls of rolling your own UI framework. 👉 Practical insights, real-world lessons, and tips you can apply across Angular, React, and Vue. 🔗 https://lnkd.in/d3cfSM69 #iJSCon #JavaScript #Frontend #WebDev #Angular #React #Vue

12

1 Comment

I recently presented #Eventmodeling to a group of developers at my company. ❓ The question arose as to how to document changes to an already implemented slice. From Martin Dilger's videos and explanations, I learned that the best way to do this is to take a screenshot of the slice, copy it below, and then make the changes to the slice. This way, you can also restore the original state if you decide not to make the changes. 👉 Here's an example: You've modelled a simple input mask as a state-change slice and have already implemented it. After some time, the customer wants to add another field, which in turn changes the command and the associated event. 📸 With the #Eventmodeling tool in Miro, I would, as mentioned, take a screenshot, then change the status of the slice from "Done" to "Created." This visually indicates that something has changed and that this change still needs to be implemented. After implementation, you can delete the screenshot and change the state of the slice to “Done” again. 🤔 What other options are there for documenting changes to an existing model? Is this history important? The model can also be stored in Git, so you'd have the history there if you wanted to determine when something changed.

10

4 Comments

Great software doesn’t start with code - it starts with clarity. At Solwey, we know that successful custom software comes from aligning user needs, design thinking, and front-end development from day one. Too often, companies jump into development only to realize later that they’re building features no one asked for - or solving the wrong problem altogether. That’s why we emphasize deep user research, collaborative wireframing, and continuous feedback loops between designers and developers.  In one recent project, simple survey insights revealed a demand for features like gamification and stronger user connectivity - insights that changed the direction of the product entirely before any mockups were finalized. What we’ve learned? -Low-fidelity wireframes spark better conversations -High-fidelity mockups eliminate surprises -Constant testing turns assumptions into confidence -And transparency throughout keeps teams aligned and outcomes stronger When done right, the end product feels intuitive, purposeful, and genuinely valuable - not just to stakeholders, but to the people using it every day. Read how we bring that process to life: https://lnkd.in/gVGnUmTc

2

Running LLMs directly on mobile devices sounds appealing. But what actually works for React Native today? At the React Universe Meetup with Zalando in Berlin, Artur Morys - Magiera will walk through the practical realities of on-device LLM inference in React Native. The talk covers performance and efficiency, end-user constraints, and what developers need to consider to make this production-ready. If you’re exploring AI features on mobile and want a realistic view of the tradeoffs, this session is for you. https://lnkd.in/dYRMYhX8

10

1 Comment

𝗦𝗽𝗲𝗲𝗱 𝗶𝘀 𝗴𝗿𝗲𝗮𝘁. 𝗨𝗻𝘁𝗶𝗹 𝗶𝘁 𝗰𝗿𝗲𝗮𝘁𝗲𝘀 𝗰𝗵𝗮𝗼𝘀. No-code and automation tools promise something every company wants: move faster. And they work. But there’s a problem many teams discover too late. When automation is built too quickly, without structure, it doesn’t create efficiency. It creates operational chaos. Disconnected workflows. Hidden dependencies. Fragile systems no one fully understands. We call this The Automation Trap. In our latest article, we explore why speed alone isn’t enough — and why automation without operational thinking often creates more problems than it solves. Read the full article: click the link in first comment. #Automation #NoCode #Operations #Startups #Scaling #BlackDurian

2

1 Comment