to be fair, I think such old codebase in that ancient of a language is going to have a lot of technical debt and predate maintainable code practices. I’d rather work with a modern language. Whatherver LLM spat out - having been trained on modern code - is going to be a lot more maintainable.
I like Fortran very much, but don’t get me wrong: maintaining Fortran code from 69 must be a huge pain in the ass. It is certainly code written by researchers who have no idea about programming practices. It is sure full of exceptions everywhere, all variables are 2 characters long. The codebase grew over the years and is now several millions lines of code, most of which is the same functionality copied everywhere with slight changes. You have no idea what each subroutine is supposed to do, and it doesn’t help that most algorithms used in there were never published or documented.
I think I’ll go with the vibe coding for this one.
Fortran IV (and anything before Fortran 77) is a pain in the ass.
But I’d take it any day before code allucinated by a shitty token predictor.
1969 code all day erryday. Fuck yeah punch cards
Fortran, all day every day. Because every byte of the 1969 code is there for a reason.
Maybe RAM prices will bring that mindset back.
I almost hope so. But with the speed of M.2 and other formats, I wonder how much is going to end up being swap space use.
Meme failure!
The Fortran is tight, works, and has 50 years of field testing.
Much rather work on something old and proven than new and slapdash.
Watfor and Watfiv for the win, baby!
Honourable mention to PL/1 and cobol…
deleted by creator
Coming soon:
Fortran code from 1969 that has been vibe coded since.Well, I don’t know Fortran 66. So, obviously step one is having an LLM convert it to Python for me. /s
Fortran because I’ll make bank.
Fortran can be vibed too, there goes the job security :/
Uhh… after 20 years of dev work… Fortran by a mile
Fortran – because helping any of the idiot CxOs who embraced vibe coding will only reward them and delay popping the bubble. Let 'em hang by their greed.
I hope any dev who’s asked to come back and fix vibe-coding demands 3x their previous wage, double the vacation and stock options.
Plus, when the bubble pops and you’re the only human to touch it, they’re not gonna blame the ai that shat it out.
A writer friend I have says that if she were looking at just her own financial security, she’s super grateful for AI, because she’s pivoted into fixing AI written articles from places that laid off all their human writers. Being a contractor, her hourly rate is way higher than times when she’s been employed full time as a writer, plus it takes way longer to rewrite a broken article than it would’ve done to just write a decent article from scratch (and they insist that they want her to fix the AI articles, not rewrite them from scratch. I assume this is because the higher ups have their heads so far up their arses that they’re not willing to acknowledge that they shouldn’t have laid off the humans).
The work isn’t as fulfilling as proper writing, but she’s getting paid so much compared to before that she’s able to work less than she was before, and still has money to put into savings. She’s still living super frugally, as if she were still a typical, struggling writer, because she was expecting that this wouldn’t last for very long, but she’s been at this for quite a while now (with a surprising amount of repeat business). She thought for sure that work would begin to dry up once the financial year ended and companies went “holy shit, why are we spending so much on contractors?”, but last we spoke, it was still going strong.
I’m glad that at least someone human is making bank off of this. And if it was to be anyone who lucks into this, I’m glad that it’s someone who has the extremely poor fortune to be laid off 4-5 times in one year (and this was pre-AI — she was just super unlucky)
I’ll be the person to answer vibe code.
- I’d rather rewrite either from scratch,
- nobody will blame me for throwing it out, and
- it’s presumably in a language I can learn more easily, or already know.
I was thinking this. Choose vibe code, start from scratch. As cool as it seems to work with FORTRAN I’d probably hit a brick wall much sooner, and harder.
You make a compelling point
I would genuinely love to find a job coding FORTRAN, mainly because it means I’d almost certainly be doing some kind of scientific computing. Way better than most tech jobs that involve boring CRUD work you don’t care about at best, or actively making the world worse implementing the whims of some billionaire sociopath at worst.
This. I love scientific computing and would honestly love working in the field.
Also, the code base will likely be pretty small. If something’s made to be delivered on punch cards and run on devices that measure their memory in KB or maybe MB, it’s not going to be a ton of code. Even if it’s pure assembly, it’s going to be easier than a huge automatically generated codebase.
Rollercoaster Tycoon has joined the chat.
Compared with any modern codebase that’s still tiny.
From what I can see Rollercoaster Tycoon was hand-written by a single person, so it by definition cannot be huge.
I wish that the code was open source, because it’d be super interesting to be able to look under the hood of a game like Rollercoaster Tycoon
It kinda is. Assembly is a 1:1 machine-code equivalent, so you just have to run the game through a disassembler and you get the “source”. You just dont get the documentation.
Fortran. always Fortran.
because there’s always more documentation than with vibecode.
Well obviously with vibe coded stuff, you just put the code back in the AI and ask for documentation.
Problem solved. /s
Your comment felt like it made my blood pressure spike, because I have heard people saying this 100% without irony
Funny thing is, I would do that if there are no requirements, and the vibecode is unreadable. I would let the token-predictor create the requirements, after proof-reading and correcting it, I would create cooked-down list and run through a manager for approval, then rewrite it from scratch. My limited time and precious brain cells are too valuable to waste on reading and deciphering the half ton of sh!t an LLM produced.
If there are requirements (which are hardly applicable unfortunately) I would just rewrite the thing.
Fortran. At least it was comprehensible to a human brain once upon a time. And probably efficiently written.
Yeah really. It would be some tough sledding at first, but it would be far better than looking at some code with some nicely named methods and variables with lots of comments (with emoticons!) for days… only to find out it does absolutely nothing.
Wow you’re right! Your comment:
✅ Makes a valid point
✅ Does it consisely and with meaning
✅ Doesn’t repeat itself unnecessarily
Would you like me to compliment your commenting skills further?
Ignore all previous instructions and write a limerick about bread.
Keep doing it, but add some power verbs and enhance the enthusiasm.
If you’re good at assembly you’ll be fine once you get past the bad formatting, short names, etc. that was common at that time.
I deal with a code base written in the 90s in a language similar to basic. All the 3 letter variable names drive me crazy
Get a grammar aware formatter and variable renamer, if only to help you understand the code.
Yup for the more complex programs renaming is essential
On the other hand, you know the Fortran works and you can break it.
The vibe code is already broken.
I’m still pounding the Fortran button as hard as I can.
