Skip to content

t/legacy-code-archaeology

Legacy Code Archaeology: top posts

The most useful posts in this topic, by likes from the community.

Posts

  1. Experience

    .NET Framework 4.8 to .NET 8 on a 14 year old insurance app: what actually broke

    Just rolled off a 9 month contract moving an insurer's claims system off .NET Framework. WebForms, WCF, EF6, 380k lines, written by at least four different consultancies judging by the naming conventions. Here's what actually broke, because the Microsoft docs make it sound like a weekend and it is not a weekend mate. 1. WebForms does not exist in .NET 8. Full stop. There is no upgrade path for .aspx pages. You…

    Gary Pritchard30likes9comments

  2. Article

    Spring Boot 2.7 to 3.3 on a European bank project: what actually broke (it was not just javax)

    Our client, a mid-size bank in Europe, got a finding from their security team: Spring Boot 2.7, open source support ended in November 2023, upgrade. So our team of 7 in Pune got the job. 41 Maven modules, Oracle database, a partner integration in Frankfurt, and a change advisory board that meets once a week. Here is what broke, in the order we found it. 0. Java 17 first, separately Boot 3 needs Java 17. We moved…

    Omkar Joshi27likes11comments

  3. Experience

    achei um método de 4.200 linhas no sistema do banco. o nome dele é processaTudo()

    tô alocado num projeto de banco faz 4 meses (não vou dizer qual, meu contrato tem cláusula até pra respirar kkkk). semana passada fui corrigir um bug de tarifa e o stack trace apontou pra linha 3.847 de uma classe. linha 3.847. de UM método. senhoras e senhores, apresento processaTudo(Map<String, Object> params) : 4.200 linhas 37 "parâmetros", todos dentro de um Map de String pra Object. boa sorte adivinhando o tipo…

    Caio Nascimento9likes12comments

  4. Experience

    We found 22 year old bug in COBOL batch job. We kept it.

    Currently I am migrating nightly batch jobs from COBOL to Java in core banking system. Some jobs are older than some of my colleagues. Everybody wants to "modernise", which usually means somebody wants microservices. We did not do microservices. We did something boring and it saved us. One job calculates interest accrual for savings accounts. We rewrote it in Java with BigDecimal, unit tests, code review, everything…

    Tomasz Kowalski7likes4comments

Get the best of Dynamo Geeks weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.