Some revolutions don’t arrive quietly. They show up as anomalies, glitches in a system everyone thought they understood. In software engineering today, AI-assisted development is one of those revolutions. It’s not merely a new tool; it’s a shift in how code can be produced, tested, and deployed—challenging assumptions that have guided the profession for decades.

Traditional software engineering emphasizes craft: elegant, human-readable code, rigorous code reviews, methodical testing, and structured processes. These practices have created careers, reputations, and entire companies. Respect for this paradigm is deserved. It’s a system built on decades of accumulated expertise.

But anomalies—the strange, disruptive results that cannot be explained within the old framework—have begun to accumulate. Autocomplete evolved to agentic coding. AI models began producing entire applications with minimal human touch. At first, these were dismissed as toys. Now, they’re creating tangible results that work. And the dissonance it generates is visceral for those who have lived and built within the old framework.

Tip: Treat every new tool or method as an anomaly first, not a threat. Observe, explore, and test before making assumptions about its capabilities.

Resistance to change is never purely intellectual. It’s emotional, grounded in identity. For many developers, coding isn’t just work—it’s a craft, a vocation, even an artistry. Watching AI take over parts of this craft triggers a grief response, even before rational evaluation begins.

Historical parallels help: Thomas Kuhn described paradigm shifts as periods where the core assumptions of a field are replaced wholesale. Max Planck observed that new paradigms often triumph not by convincing skeptics but by the fading of the old generation. In AI-assisted development, the pace is compressed: shifts that used to take decades may now unfold in months or years.

Understanding this emotional core allows for a different approach. Instead of battling defensiveness, recognize it. Respect the expertise that underpins skepticism. The defensive reactions—heated debates, philosophical objections, ad hominem critiques—aren’t mere obstinacy. They’re mechanisms for coping with a rapidly moving landscape.

Tip: Acknowledge your own discomfort when engaging with new systems. Awareness of emotional resistance allows for clearer evaluation and reduces reactive decision-making.

One of the most challenging aspects of paradigm shifts is incommensurability: two sides are not merely disagreeing—they are measuring success by different standards. Traditional engineering judges quality by elegance, maintainability, and adherence to established methodologies. AI-assisted coding judges quality by function, testability, and results. Comparing them directly is like comparing apples to quantum particles: the metrics don’t align.

Defense mechanisms emerge naturally:

Even objective studies can be misinterpreted. Early findings showing limited productivity gains often fail to capture concurrent, agentic workflows that deviate from sequential expectations. Evidence must be evaluated in context, not in isolation.

Tip: Measure new methods by their outcomes relative to the problems they solve, not by how closely they mimic old practices.

Kuhn describes a crisis as the stage where anomalies can no longer be absorbed by the old paradigm. In software, it manifests as urgency, heated debate, and disbelief. Developers see AI closing tickets, passing tests, and shipping software in ways previously thought impossible. Their instincts resist what they cannot yet rationalize.

Opportunity exists within this crisis. Some of the most respected engineers—those who adapt—embrace discomfort and experiment with the tools. They let go of entrenched assumptions, update their priors, and become beginners again in familiar domains. Adoption doesn’t require abandoning craftsmanship; it requires redefining metrics of success and understanding how new methods shift the landscape of possibility.

Tip: Treat paradigm crisis as a chance to expand perspective. Experiment actively, track results empirically, and document learning to accelerate adaptation.

AI-assisted development is here. It is functional, practical, and increasingly integral to production workflows. Grassroots adoption is driving its integration, not top-down mandates. Ignore the noise of online debates; focus on measurable results and real-world application.

Surviving—and thriving—means accepting that the rules of the game have changed:

The shift is real. The evidence is undeniable. And yet, the choice remains: move with it or remain anchored in the old paradigm. Those who engage with curiosity, rigor, and humility will find themselves not displaced, but empowered.

Tip: Focus on mastering new paradigms with the same intensity you applied to past crafts. Discomfort is not failure—it is the signal that transformation is underway.

Eppur si muove. And it moves for those willing to adapt.

What’s your next spark? A new platform engineering skill? A bold pitch? A team ready to rise? Share your ideas or challenges at Tiny Big Spark. Let’s build your pyramid—together.

That’s it!

Keep innovating and stay inspired!

If you think your colleagues and friends would find this content valuable, we’d love it if you shared our newsletter with them!

As the world becomes increasingly digital, this question will be on the minds of millions of people seeking new income streams in 2026.

The answer is—Absolutely!

Thank you for taking the time to read today’s email! Your support allows me to send out this newsletter for free every day. 

 What do you think for today’s episode? Please provide your feedback in the poll below.

Share the newsletter with your friends and colleagues if you find it valuable.

Disclaimer: The "Tiny Big Spark" newsletter is for informational and educational purposes only, not a substitute for professional advice, including financial, legal, medical, or technical. We strive for accuracy but make no guarantees about the completeness or reliability of the information provided. Any reliance on this information is at your own risk. The views expressed are those of the authors and do not reflect any organization's official position. This newsletter may link to external sites we don't control; we do not endorse their content. We are not liable for any losses or damages from using this information.