What's the EXACT Technical Gap That Separates AI SUCCESS From AI FAILURE? | @stevesmithtech.bsky.social & @davefarley77.bsky.social
π½οΈ Available NOW
Watch HERE β‘οΈ youtu.be/ekRMQ5qUMlo
@davefarley77.bsky.social
Software Engineer, Consultant & Author. The Modern Software Engineering Channel: https://www.youtube.com/@ModernSoftwareEngineeringYT Support Me On Patreon: https://bit.ly/ContinuousDeliveryPatreon
What's the EXACT Technical Gap That Separates AI SUCCESS From AI FAILURE? | @stevesmithtech.bsky.social & @davefarley77.bsky.social
π½οΈ Available NOW
Watch HERE β‘οΈ youtu.be/ekRMQ5qUMlo
Vendors are desperately slapping AI labels onto their tools to keep the hype cycle going, but AI is absolutely not the end of DevOps.
06.03.2026 11:47 β π 10 π 6 π¬ 3 π 0
The Simplest Way to Make Your Architecture Testable and Reproducible (Works Every Time) | @davefarley77.bsky.social
π½οΈ AVAILABLE NOW
Watch HERE β‘οΈ youtu.be/uHatwKrYY_c
If you care about continuous delivery and evolutionary software architecture, you should care deeply about deterministic system design. Determinism is the prerequisite for trust in software engineering.
Find out my thoughts in my latest video for @modernswe.bsky.social β‘οΈ youtu.be/uHatwKrYY_c
With Manuel Pais on Flow by Design for CI/CD, he takes a look at how to optimize your delivery processes and team interactions to actually achieve these transformative business outcomes.
You can register for the free webinar and secure your spot here: courses.cd.training/courses/flow...
However, to reap these massive business benefits, you have to design your workflows, teams, and pipelines deliberately. You cannot simply install a tool and expect "Flow."
7/8
5. The bottom line is that these organizations simply make more money. The State of DevOps report found that organizations practicing CD saw a 50% higher market cap growth over a three-year period.
6/8
4. By moving quickly, businesses can rapidly experiment and learn in the field. It allows you to leverage "economies of speed" to close the gap between what you think customers want and what they actually need.
5/8
3. CD provides better control and a lower-risk way of working. When I worked at LMAX, we designed our CD pipelines to automatically ensure every successful release candidate was regulatory compliant from day one.
4/8
2. Job satisfaction is the number one predictor of high performance. When Microsoft adopted CD practices on their Bing team, engineers reported their work-life balance satisfaction jumped from 38% to 75%.
3/8
It's because Continuous Delivery delivers five distinct business advantages:
1. Teams practicing CD spend 44% more of their effort actually creating value rather than just fixing bugs.
2/8
Does your development process attract innovators, or drive them away? We know that Continuous Delivery is the approach used by some of the most successful companies in the world. But why do they care so much about how their software is released?
1/8
The Simplest Way to Make Your Architecture Testable and Reproducible (Works Every Time) | @davefarley77.bsky.social
TOMORROW NIGHT @ 7PM (UK)
Subscribe & turn on notifications π so you NEVER miss an upload! β‘οΈ youtube.com/@ModernSoftw...
Gain a clearer understanding of modern software architecture and design.
Spend an hour with industry expert @davefarley77.bsky.social in this Free Tutorial as he explains the essential tools of software engineering and how to apply them in practice.
π
Welcome to the Engineering Room Dan Abel! π£
The nuances of engineering leadership and the evolution of high-performing teams.
π£οΈ LISTEN NOW
Apple - apple.co/43s2e0h
Spotify - spoti.fi/3VqZVIV
Amazon - amzn.to/43nkkRl
Audible - bit.ly/TERaudible
If youβre not treating software development as an scientific discipline, with experiments, feedback loops, and measurable outcomes, then youβre not a software engineerβ¦
26.02.2026 12:28 β π 15 π 3 π¬ 1 π 0
Itβs Time We Go Beyond The Test Pyramid (& Do This Instead) |
@emilybache.com
π½οΈ AVAILABLE NOW
Watch HERE β‘οΈ youtu.be/IBvYFRSw4do
Itβs Time We Go Beyond The Test Pyramid (& Do This Instead) | @emilybache.com
π
TOMORROW NIGHT @ 7PM (UK)
Subscribe & turn on notifications π so you NEVER miss an upload! β‘οΈ youtube.com/@ModernSoftw...
If you want to dive deeper into how to actually apply these ideas in the real world, I have a free webinar on how to design to manage complexity and learn software architecture.
You can register here β‘οΈ courses.cd.training/courses/desi...
9/9
Ultimately, architecture is just the shared understanding of the system that we all subscribe to. It is the tool we use to manage complexity.
8/9
4. A brilliant concept from George Fairbanks: write code in a way that makes the architecture obvious. If the code you work in closely represents the intended architecture, the shared mental model of the entire team stays up to date.
7/9
3. Good architecture isn't about massive rulebooks. It's about establishing a short list of solid constraints that keep everyone aligned, paired with the freedom and principles to creatively solve problems within those bounds.
6/9
2. When developers get frustrated by an architecture, it's almost always because they don't get to see behind the curtain. If a developer hits a problem and doesn't understand the context of why a constraint exists, they will simply find an "inventive" way to circumvent it.
5/9
1. You need to understand your place in the bigger picture. You might not be able to affect the entire machinery of a massive system, but you need to completely own and understand your specific "cog," as well as the immediate consumers and producers you interact with.
4/9
But how much does a developer actually need to know, especially in a massive system built by hundreds of people? You can't have everyone involved in every single decision.
Here are the core takeaways on what developers must grasp to do their jobs well π
3/9
Exactly where does code design stop and architecture begin? The truth is, there is no hard line. It is a continuum.
2/9
Should software developers care about software architecture? If your answer is "no," we are back in the bad old days of the "Ivory Tower Architect" handing down rigid edicts to developers who are told exactly what to do.
1/9
β Approval Tests vs Acceptance Tests: What's the Difference? β
One Big Question with @kentbeck.com & @emilybache.com | AVAILABLE NOW π½οΈ
Watch HERE β‘οΈ youtu.be/n5vzuQAToZE
Modern software leadership is about moving from a culture of permission to a culture of evidence.
If leaders are still making technical decisions based on their 'gut' rather than creating the feedback loops that allow the team to experiment, theyβre becoming the bottleneck.
How to Make the Best of AI Programming Assistants | @davefarley77.bsky.social
π½οΈ AVAILABLE NOW
Watch HERE β‘οΈ youtu.be/XavrebMKH2A