Kennst du das? Du musst Code pflegen, den du nie selbst geschrieben hast – und der längst „tot“ oder vergessen ist? 
Dead-, Legacy- oder sogar Zombie-Code machen das Leben schwer. Wie erkennst du, was noch lebt? Und wie wirst du die „Leichen“ los? 
@hansolo_ spricht auf der #BaselOne25 genau darüber und zeigt Tools gegen Code-Müll: We hate code – The !joy of maintaining dead code am 16. Oktober.
Tickets & Programm: https://baselone.org/#programm
#Development #Analyses
Vibe code is legacy code · “Code that nobody understands is tech debt.” https://ilo.im/165uaf
_____
#Programming #Coding #VibeCoding #AI #Maintainability #TechDebt #LegacyCode #WebDev #Frontend #Backend
Just posted: Can Claude help with legacy code? Let's try to use it and see what value it adds and what limitations it hits.
#Blog #Video #AI #Design #Legacycode #Video #Video https://mozaicworks.com/blog/can-claude-help-with-legacy-code
https://mozaicworks.com/blog/can-claude-help-with-legacy-code?fsp_sid=194
TECHNICAL DEBT is like a ROTTING ROOF
On rainy days, it's too wet to fix it.
On sunny days, there's no leak… so you ignore it.
Then one day, boom, ceiling caves in, buckets everywhere, and you're duct taping production at 2am.
That's technical debt.
Not just messy code. Not just bad practices.
It's what you chose not to fix when you could have.
The missing tests.
The config you hardcoded "just for now".
The abstraction you skipped because "it works".
The one extra iteration after the ticket was marked as "done".
And now it's slowing you down.
It's holding your future hostage.
You're spending engineering cycles bailing water, not shipping value.
We love to say we're "building", but half the time we're just… leak managers.
You can't scale rot.
So next time the sun's out, fix the roof.
Because when the rain hits, it's too late.
Think #Java's just #LegacyCode & boilerplate? Wrong decade. @vipinaiswarya maps how Java quietly shaped Python, #JavaScript, Go, even Node.js. From garbage collection to WORA & threading – it's everywhere. You just didn’t see it.
Read: https://javapro.io/2025/06/24/javas-impact-in-technology-spectrum/
I really liked watching this talk: "Code Mending in the AI age - Ray Myers | Craft Conference 2024"
Verheddert im Dschungel der #Java-Standards? Auf der #JCON2025 spricht Merlin Bögershausen darüber, wie du mit #MigrationEngineering & #OpenRewrite dein Projekt neu ausrichtest.
Hol dir vor der Session schon Input aus seinem #JAVAPRO Artikel: https://javapro.io/de/ueberwinde-20-jahre-mit-migration-engineering/
Legacy Systems = tightly coupled architectures hard to scale, change & maintain.
National Grid tackled this with 4 paradigms:
#DomainDrivenDesign
#TeamTopologies
#EventDrivenArchitecture
#ChangeDataCapture
Details in the #InfoQ article ⇨ https://bit.ly/44UplDs
Migrating from .NET Framework to modern .NET? In the latest Breakpoint Show, we chat with Tomas Herceg about what developers need to know before moving legacy code to today’s standards. Don’t miss this expert-packed episode!
https://www.breakpoint.show/podcast/episode-039-dont-call-my-net-baby-ugly/
Acabamos de publicar una traducción al español con algunas mejoras y actualizaciones de nuestro post sobre mutation testing "Relevant mutants":
Mutantes relevantes https://codesai.com/posts/2025/04/mutantes-relevantes
The earliest versions of the first C compiler known to exist
Coding is easier than ever. That’s why no one actually codes anymore.
Once, compiling took 30 minutes. Now, downloading dependencies does.
I started with a text editor, every line deliberate, every recompile an ordeal. My code was built to last. No frameworks, few dependencies, a simple bash script to build & deploy.
Now? I compile in milliseconds… only to wait hours for linters, CI/CD, IaC, PR rituals & YAML sacrifices. I am no longer an engineer. I am a high priest in a temple of abstraction.
Performance? A joke. Code once ran fast because it had to. Today, it’s an obese stack of best-practice boilerplate. Innovation? No, just rebranded complexity.
Legacy? We create it faster than ever. The lifespan of a framework is measured in months. But don’t worry, we’ll rebrand it & call it progress.
New post:
Sprouting or wrapping?
https://codesai.com/posts/2025/03/sprouting-or-wrapping
Republishing an old @codesai 's post on Dev community:
Relevant mutants
https://dev.to/trikitrok/relevant-mutants-3d67
Fix technical debt before it breaks your project! 
Join Borna Matijanić at the Dutch PHP Conference. 
https://phpconference.nl/session/technical-debt-autopsy-real-world-lessons-from-rescuing-challenging-projects/
Need to upgrade @Rails? Don’t know how long it will take? Get a #Ruby and #Rails code audit with an action plan to upgrade Rails.
Get estimates by our team of experts (based on 30,000+ dev/hours of Ruby/Rails upgrades) and secure the budget to upgrade this quarter! 
https://go.fastruby.io/r26 #TechDebt #LegacyCode #RubyOnRails
Looking forward to be speaking at Microservices Meetup Munich next week. Join if you like to learn about Domain-Driven Transformation.
Thanks, David Leitner, Christian Deger, Benjamin Brachert for organization and Markus Fröhlich from TESTIFI GmbH for the venue!
https://www.meetup.com/de-DE/microservices-meetup-munich/events/305829796/
"Our iOS Code is Too Complex for Unit Tests" is a Lie 
https://qualitycoding.org/legacy-code-rescue-thousand-line-view-controller/ #LegacyCode
Can a 1,000-Line iOS Controller Be Tamed? This Legacy Code Rescue Shows How 
https://qualitycoding.org/legacy-code-rescue-thousand-line-view-controller/ #LegacyCode
