Tessera
Folgen

Modern Software Engineering

@modernswe.bsky.social

The Modern Software Engineering Channel ➡️ https://www.youtube.com/@ModernSoftwareEngineeringYT

429 Posts1261 Follower8 Folgt
Dave Farley@davefarley77.bsky.social · 4d ago

AI won’t replace software engineering, it changes the economics of writing code. But prompts aren’t enough. To safely guide AI agents, we need executable specifications. Discover why Acceptance Test-Driven Development (ATDD) is the future of AI coding. 📽️ youtu.be/EkH_uoybj8k

Bild
Emily Bache@emilybache.com · 2w ago

Collaborative coding in an ensemble or mob has been a cornerstone of my work, and when you add agentic AI it needs different interaction patterns. My latest video and blog explain some of the things I've found to work. youtu.be/ydAin2IWaQo & coding-is-like-cooking.info/2026/10/agen...

Agentic AI Coding BREAKS Mob Programming (Here's How to Fix It) - Coding Is Like Cooking

This article is available as a video on the Modern Software Engineering channel. As a technical coach, I find Mob Programming is really effective. Recently of course, we started using agentic AI, and ...

coding-is-like-cooking.info

Dave Farley@davefarley77.bsky.social · 2w ago

Mastering ATDD & BDD shows you how to define value clearly, collaborate more effectively, and build automated, executable specifications that drive development. This course is built for teams who want to start delivering with clarity and confidence. FIND OUT MORE 👇

Bild
Acorn DevOps@acorndevops.bsky.social · 3w ago

Now for a quote Jurassic Level Big Up to @modernswe.bsky.social for their YouTube note. Approval testing, too, is a healthy technique to monitor throughput, yet the note invites questions: 1) Can Approval Tests be synthesized with adequate *other* layer tests? 2) When does trunk time start?

Screenshot of a dark-mode community post from the YouTube channel Modern Software Engineering, posted 37 minutes ago, with the red-and-blue MSE logo. The text describes the fear of inheriting legacy code with no automated tests, where changing a single line risks breaking hidden dependencies or edge cases, so teams stop refactoring and systems decay. It then introduces Approval Testing. Instead of writing assertions upfront, an approval test runs the existing code, saves its actual output to a reference file, and fails on later runs if that output changes. You don't need to fully understand the code's internal logic to write one. A bulleted list of benefits follows: confirming that refactoring hasn't changed behaviour; building high test coverage quickly by pairing it with code coverage tools and sample inputs; protecting quirks or bugs that other systems quietly depend on; and validating complex outputs such as reports or graphical renders, where line-by-line assertions are impractical.The continuation of the post, in dark mode, promotes Dave Farley's free guide "How to Get the Best from Approval Testing." It says the guide covers how approval tests work step by step, their role in safe legacy refactoring, why to avoid them for brand-new features, and self-referential traps to watch for. A book emoji precedes a truncated download link to subscribepage.com. Below the text is a close-up photo, taken from below, of a fossilized Tyrannosaurus rex skull with its jaws open and long curved teeth. The skull is mounted in a bright museum hall with white columns and an arched ceiling, and metal brackets hold the bones together. The dinosaur serves as a visual joke about "legacy" code.
Dave Farley@davefarley77.bsky.social · 3w ago

"I bought this book for myself after watching Dave Farley's YouTube channel. I've now bought a second copy for the office library and I'm suggesting that everyone in my development team reads it." Why thank you! 😎 Grab your copy here 🔗 amzn.to/3DwdwT3

Bild