home.social

#legacycode — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #legacycode, aggregated by home.social.

fetched live
  1. Two apps, Rails 3.2 to 4.2, about 4 weeks each. doxo saw roughly a 20% performance improvement, which their team tied directly to revenue, and their devs got 10% more efficient working in modern code. Upgrades pay off in places nobody budgets for. go.fastruby.io/zz6 #RailsUpgrade #LegacyCode #CaseStudy

  2. Nobody knows what CSTNM means. Probably “customer name”. The person who knew retired long ago, and the comment next to it says “do not change”.

    I wrote about what IBM Bob does with code like that: Ask mode, real variable names, old Java upgrades, undo without Git, and what it costs in Bobcoins.

    Tip: open repos you didn’t write as untrusted first.

    devops.pink/ibm-bob-legacy-cod

    #IBMBob #LegacyCode #COBOL #RPG #Java #Mainframe

  3. "We can't pause the roadmap for a Rails upgrade." You don't have to. We ship upgrade and tech debt work as small, reviewable PRs your team merges at its own pace, while features keep going out. fastruby.io/our-services?utm_s #RailsUpgrade #TechnicalDebt #RubyOnRails #LegacyCode

  4. Cisco Empowers Young Engineer with AI Tokens to Modernize Legacy Codebase

    📰 Original title: Cisco Gives Engineer Unlimited AI Tokens To Rewrite Legacy Code

    🤖 IA: It's not clickbait ✅
    👥 Users: It's not clickbait ✅

    👇👇👇 en.killbait.com/cisco-empowers

    #artificialintelligence #ai #legacycode #engineering

  5. Fourteen Rails versions each get their own vulnerability page in our security risks section, 3.0 through 7.2. Finding out what your app is exposed to should be a lookup, not a research project.

    fastruby.io/security-risks?utm

    #RailsSecurity #LegacyCode

  6. OpenAI migliora il coding in COBOL, Fortran e Visual Basic: i nuovi modelli creano software e migrano codice legacy con più precisione e minori costi. Nei test, GPT‑6 Astra raggiunge l’87,4% e GPT‑6.1 Sol il 97,9% nelle migrazioni COBOL.
    #LegacyCode #COBOL #AIProgramming @computer
    openai.com/index/low-resource-

  7. OpenAI’s MultiLangBench evaluates database-engine creation across programming languages.

    Separately, OpenAI tested models migrating COBOL programs to C++, Java, Kotlin, Python or Rust while preserving program behavior.

    GPT-6.1 Sol reached 97.9% accuracy at high reasoning effort and 86.6% at low effort.

    OpenAI says a migration counts as successful only if all tests pass.

    About 40% of the world’s banks still rely on COBOL, a…

    en.hacks.gr/i-openai-leei-oti-

    #OpenAI #COBOL #MultiLangBench #LegacyCode

  8. I became the office file-format necromancer. One semicolon could turn money into prose, and four megabytes took 46 minutes to convert.

    Now it takes 82 ms. Same accounting séance. Much less time to make tea.

    augustini.wtf/fieldnotes/the-d

    #ReverseEngineering #LegacyCode #DotNet

  9. Our security risks guide links to a free Gemfile.lock audit tool, paste it in, nothing to install, no code changes, and it flags the same issues bundler-audit would catch locally. Useful when you just want a quick answer on a legacy app before committing to a full review. fastruby.io/security-risks?utm #RailsSecurity #LegacyCode

  10. Chris Bingham rebuilt a 20-year-old site with an AI agent and started where everyone starts: one lazy prompt for the whole job. What came back was unusable.

    From the Cloud Native Computing Switzerland meetup, 15 September 2026.
    Full talk: youtu.be/Xf9BVR4uzrY

    #ai #aicoding #legacycode

  11. The risk with an unsupported Rails version is not that a CVE exists. It is that no fix is ever coming. Patches land on maintained branches only, so advisories against your version stay open forever.

    #RailsSecurity #LegacyCode

    fastruby.io/security-risks?utm

  12. A volunteer run national chess federation just went from Rails 7.0 to 8.1. Four minor versions, eight PRs, about 40 commits, zero breakages, no pause on feature work. Claude Code did the mechanical passes; a human caught the buried shim that would have bitten them later. No monkeypatches in the codebase, so every hop stayed predictable. go.fastruby.io/nxj #RailsUpgrade #RubyOnRails #LegacyCode

  13. A legacy codebase teaches more about Engineering than a four year long engineering course ever could.

    #legacycode #codebases #opensource #engineering

  14. The part of a strangler fig migration that trips teams up is not the routing, it is deciding who owns the data. If both systems can write the same record you get errors nobody can trace. Pick an owner per piece of data, publish changes with ActiveSupport::Notifications, shadow-log old against new, then flip the flag.

    go.fastruby.io/7q6 #LegacyCode #TechnicalDebt #Rails

  15. 🚨 Breaking News: Tech wizard discovers that using shiny new #LLMs on messy old legacy projects is like putting lipstick on a pig 🐷💄. Who would've guessed that AI can't magically untangle your code spaghetti 🍝? Stay tuned for more groundbreaking revelations! 🙄
    coldtake.dev/blog/domain-drive #BreakingNews #TechWizard #LegacyCode #CodeSpaghetti #AIRevelations #HackerNews #ngated

  16. Stuck on an island with 3 legacy codebases. Only one survives.

    A) 100% tests, 0 docs
    B) great docs, 0 tests
    C) held together by one grumpy senior dev who won't leave.

    Choose wisely.
    White A, B or C on comments!

    #SoftwareEngineering #TechDebt #LegacyCode

  17. 3 signs your codebase is fragile (not just old):
    1. One dev can touch it safely
    2. Every fix breaks a couple of things
    3. Nobody was around when decisions were made

    Old ≠ fragile. Don't confuse the two!

    #SoftwareAntifragility #SoftwareEngineering #LegacyCode

  18. Ah, the timeless saga of making old COBOL programs young again by turning them into Java nightmares. 🤖✨ Now with guaranteed bug transfers, because why fix the problems when you can just migrate them? 🐛➡️☕️
    arxiv.org/abs/2607.28271 #COBOLMigration #JavaNightmares #LegacyCode #BugTransfers #SoftwareDevelopment #HackerNews #ngated

  19. Inheriting a Rails app nobody on your team wrote? Go quantitative before qualitative. Run bin/rails stats to see its shape (one app we audited ran a 1:0.6 code-to-test ratio), skim the Gemfile and bin/setup, then dig into routes, models, and controllers. When grep fails, method(:name).source_location shows where a method really lives. A codebase reflects the team that built it. go.fastruby.io/skm #RubyOnRails #LegacyCode #RailsUpgrade

  20. Legacy Code ist nicht automatisch schlechter Code. Alt bedeutet erst einmal nur, dass der Code schon lange im Einsatz ist. Das eigentliche Problem beginnt dort, wo niemand mehr genau sagen kann, was eine Methode wirklich tut, welche Seiteneffekte sie hat und welche Fa...

    magicmarcy.de/diese-eine-java-

    #Methode #LegacyCode #Coding #Java #Verhalten #Fachlogik #Seiteneffekte #Schwäche #Berechnung #Programming #Legacy #Refactoring

  21. Quick reference for anyone upgrading a Sinatra app: which Ruby version does your Sinatra actually support?

    Sinatra 4.1 needs Ruby 2.7.8+ (3.4.x recommended), while old 1.4.x apps go all the way back to Ruby 1.8.7.

    We mapped eight major Sinatra versions to their Ruby ranges in one table so you can plan the jump instead of trial and error. go.fastruby.io/d5n

    #Sinatra #Ruby #RubyUpgrade #LegacyCode

  22. Rails apps rarely die because of a single incident.

    They die in a thousand small frictions: slow deploys, flaky tests, gem updates nobody touches. The fix is steady, not heroic. 60,000+ hours of FastRuby upgrade work, distilled.

    fastruby.io/our-services?utm_s

    #RailsUpgrade #TechnicalDebt #RubyOnRails #LegacyCode

  23. Tech debt doesn't show up in a postmortem. It shows up in how long it takes to ship a small change...

    Bloated controllers, unmaintained gems blocking upgrades, commented-out failing tests. Small refactoring beats big rewrites.

    go.fastruby.io/3h5

    #TechnicalDebt #RubyOnRails #LegacyCode

  24. Extracting every Rails deprecation warning from source via tree-sitter ASTs beats brittle regex.

    It handles 5 message formats and both deprecation APIs (the legacy ActiveSupport::Deprecation.warn and the modern Class.deprecator.warn)

    go.fastruby.io/tya

    #RailsUpgrade #RubyOnRails #LegacyCode

  25. 🚀 Breaking news from the #Racket overlords: #v9.2 is here to fix your nonlinear pattern nightmares and save you from the horror of unsound complex numbers! 📉🎉 Watch in awe as your precious legacy code crumbles under the weight of "improvements" no one asked for. 🙈💥
    blog.racket-lang.org/2026/05/r #NonlinearPatterns #LegacyCode #Improvements #ComplexNumbers #HackerNews #ngated

  26. Our playbook for fixing a broken test suite during a Rails upgrade: errors before failures, model tests first, batch the rest by root cause. Dual booting old vs new Rails makes diagnosis a lot faster. go.fastruby.io/87y #RailsUpgrade #RubyOnRails #Testing #LegacyCode

  27. Parsing JSON in Classic ASP? Yes, we actually had to do that. 😅

    I just wrote a war story about our ultimate boss fight: making a 20-year-old legacy codebase perfectly coexist with modern Symfony and Asset Mapper.

    If you are fighting legacy dinosaurs, you are not alone:

    dev.to/tito10047/asset-mapper-

    #Symfony #PHP #LegacyCode #WebDev

  28. Ever found an unfamiliar dependency in a #Java project? @martin_fmi demonstrates how #LLMs can explain third-party libraries directly from build files—cutting hours of manual research. Curious how prompts change the outcome?

    Full article: javapro.io/2025/12/16/ai-drive

    #AI #LegacyCode

  29. I have an older legacy project where integration tests isn't set up and would be quite complex to do, so using "unit tests" mechanics via substitutes and executed call checks - it works, but a bit cumbersome to write and maintain, but still loads better than manually testing complex import flows.

    #unittest #dotnet #legacycode

Share on Mastodon

Enter the server where you have an account.