<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/software-developers-should-avoid-traumatic-changes-l6mworll1" -->

---
title: Software developers should avoid traumatic changes
description: Breaking changes in software ecosystems can cause lasting community trauma, categorized as 'strong' (code stops working) or 'weak' (code becomes unidiomatic)....
canonical: https://daily.dev/posts/software-developers-should-avoid-traumatic-changes-l6mworll1
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Software developers should avoid traumatic changes | daily.dev
og:description: Breaking changes in software ecosystems can cause lasting community trauma, categorized as 'strong' (code stops working) or 'weak' (code becomes unidiomatic)....
og:url: https://daily.dev/posts/software-developers-should-avoid-traumatic-changes-l6mworll1
og:image: https://api.daily.dev/og/posts/L6mwoRlL1.png
og:image:alt: Software developers should avoid traumatic changes
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Software developers should avoid traumatic changes

**[Drew DeVault](https://daily.dev/sources/drewdevault)** · 4 min read · 0 upvotes · 0 comments

## Summary

Breaking changes in software ecosystems can cause lasting community trauma, categorized as 'strong' (code stops working) or 'weak' (code becomes unidiomatic). Python 3's migration exemplifies strong trauma, while asyncio's introduction represents weak trauma by rendering large portions of the ecosystem idiomatically obsolete without actually breaking anything. The slow rot caused by weak traumatic changes is harder to spot but equally damaging over time. The post urges language and framework designers to think carefully before introducing such changes, citing Go generics as a potential future example.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://drewdevault.com/2019/11/26/Avoid-traumatic-changes.html>

## Similar posts on daily.dev

- [Redesign without fear](https://daily.dev/posts/redesign-without-fear-4bs4ays3m) · ploeh blog · 6 upvotes · 1 comments
- [From Framework Fatigue to Ecosystem Fatigue](https://daily.dev/posts/from-framework-fatigue-to-ecosystem-fatigue-p73sopzuv) · Nanomicon · 1 upvotes · 0 comments
- [I Thought Working Code Was Good Enough. I Was Wrong.](https://daily.dev/posts/i-thought-working-code-was-good-enough-i-was-wrong--sht2vtiff) · Medium · 0 upvotes · 0 comments

---

Tags: [#golang](https://daily.dev/tags/golang), [#python](https://daily.dev/tags/python)

[View this post on daily.dev](https://daily.dev/posts/software-developers-should-avoid-traumatic-changes-l6mworll1)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Software developers should avoid traumatic changes","url":"https://daily.dev/posts/software-developers-should-avoid-traumatic-changes-l6mworll1","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/software-developers-should-avoid-traumatic-changes-l6mworll1"},"datePublished":"2026-03-31T12:28:55.574Z","dateModified":"2026-07-02T02:13:42.413Z","description":"Breaking changes in software ecosystems can cause lasting community trauma, categorized as 'strong' (code stops working) or 'weak' (code becomes unidiomatic)....","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","isAccessibleForFree":true,"articleSection":"Drew DeVault","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Drew DeVault","logo":"https://media.daily.dev/image/upload/s--BGhGBu0U--/f_auto,q_auto/v1774960025/logos/drewdevault?_a=BAMAMiWQ0","url":"https://daily.dev/sources/drewdevault"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/software-developers-should-avoid-traumatic-changes-l6mworll1","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"golang,python","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Drew DeVault","item":"https://daily.dev/sources/drewdevault"},{"@type":"ListItem","position":3,"name":"Software developers should avoid traumatic changes"}]}
```

