6 ms·
The ability (and willingness) to dive into legacy codebases and make sense of them paid my bills for a good 15 years after graduating with a CS degree. It was
by theshrike79 5y ago
The ability (and willingness) to dive into legacy codebases and make sense of them paid my bills for a good 15 years after graduating with a CS degree.
It was fixing bugs and adding new features to existing code, usually stuff that was 5-10 years old at the least. If I didn't understand something I needed to wait for That Guy to show up. The one who did the first version some time in the last millennium.
Latest versions of anything was a pipe dream. Java version was at least 1-2 major versions behind the time. Business logic was PL/SQL and Perl scripts old enough to have a driver's license.
Also: print-debugging all the way. There were exactly zero ways to attach any kind of modern debugger to a 20 year old pile of code that had organically grown to what it was at the time.
I think I was 16-17 years into my career before I started a greenfield project from scratch, one I could decide the full tech stack from top to bottom.
- aprdm 5y agoOne of the systems I work with just re-hired the original developer now that he retired. The software is around 20 years old and the guy is working for fun. It's actually quite interesting to see haha, the system is the core of a large company and hasn't changed that much since he left a decade ago. He sort of picked up from where he left.
- armchairhacker 5y ago> Business logic was PL/SQL Funny that you said that because i sometimes hear “store your database logic / invariants in the database!” I guess it depends what kind of logic.
- theshrike79 5y agoIn this case it was decoding binary responses from devices directly off the wire. Completely bonkers setup. If the PL/SQL parser failed, there goes that message. Oh, well. Try again next day when the message arrives or dial the device and ask it to send it again. I suggested after a while if we could store the raw message in a queue table and parse it from there. But no, everyone was too scared to change the system and we stuck to the old ways.
- dboreham 5y agoThe prevalence of people who like to generate "write-only" code bases keeps this business model alive and well.
- 908B64B197 5y ago> Also: print-debugging all the way. There were exactly zero ways to attach any kind of modern debugger That's just laziness from the original developer. To me, no debugger support means it's time for a re-write.
- fsckboy 5y ago> That's just laziness from the original developer. To me, no debugger support means it's time for a re-write. when do you plan to get started on the linux kernel? that Linus is a lazy pri*k, he'll never get to it! *printk https://www.kernel.org/doc/html/latest/core-api/printk-basics.html https://www.kernel.org/doc/html/latest/core-api/printk-basic...
- 908B64B197 5y agoThere's also KDB and KGDB (he eventually conceded that having a debugger in the main tree was for the best). https://www.kernel.org/doc/html/v4.16/dev-tools/kgdb.html https://www.kernel.org/doc/html/v4.16/dev-tools/kgdb.html
- theshrike79 5y agoYes, please tell me the argumentation you would use to completely rewrite a 10 year old perfectly working stack, which is actively used to read tens of millions of devices of varying age daily. A piece of software that has around 50 coders on it actively keeping it running and adding new features and supported devices. (It took around 5 years and a team of 20 with millions of funding to "rewrite it" eventually and even they had to drop support for all but the latest devices. The old system is still chugging away, reading the old devices) Also I would like to know how you would attach a debugger to a stack that contained, among others, ASM/C-code running on an embedded device on the other side of the world, some MFC/C code on a gateway windows computer, perl scripts running god knows where and a PL/SQL bundle on an Oracle server in another country and some Java logic on a different server. This is the life legacy coders live. Of course, if you have a modern stack you can just click "debug" on your IDE and it'll automatically attach to a remote process and let you step through the code. We don't have that :)
- dehrmann 5y ago> Java version was at least 1-2 major versions behind the time A lot of shops are 9 versions behind right now.
- theshrike79 5y agoYea, this was in the ye olden days where Java major version were big news. Now they have a major version upgrade every time someone coughs at the office :D
- approxim8ion 5y agoFor Java, definitely. Lots of places are still on Java8.