I worked on 15 year old code base for about two years. The initial 10 years was by the first guy, next couple of years second guy and i was third person to ever touch the code. Pretty unusual project i think. First guy was worried about memory and used global variables for everything, and second guy tried to refactor things and was a bit of an architecture astronaut and did things for "future extendability" leaving tons of dead code. Everything was so tightly coupled that you couldn't isolate or identify source of bugs. This was grand example of spagetti code. This was great learning experience with all of the anti examples. Global variables with multiple reads and multiple writes were common things. I feel bit anxious just thinking about the project. I just couldn't make anything work without a full exhaustive debug session. It took me months to do anything. Now i use rust and i couldn't be happier
I started working in my current codebase in 1998. Its origins dates to sometime in the 80s. Not gonna lie, it feels pretty familiar and comfortable by now. Granted, the frontend has changed a number of times over the decades, but all the logic is in the database so the frontend is more a matter of configuration than programming (creating the actual frontend framework and tooling isn't my department).
@@82TheKnocKY some of my company's web page functionalities are stored as jsons in a database. I looked at it and said "there's no way this is right, lol". But then you think again and you're like "oh, you can add functionality to the page (say, buttons with stuff in them) by just coding in simple SQL", and now I don't know what to think
In the defense world, it’s not unusual to stay on a single product line for 10, 20, even 30 years. Many programs take 10 years to first release and then they last 20 years or more. There’s pros and cons.
Oh, ADA, I hardly knew ye. More seriously, yeah. Been there. It's why all of my hobbies involve creating tangible things in relatively short amounts of time.
I’m a year into working with a decades old codebase. I also feel like a “member of the team”, but I figure in another year I’ll be almost indispensable and they won’t be able to fire me.
This was scarily familiar. I currently work in IT, maintaining a 35 year old software that is still actively developed. The database part of it consists of more than 700 tables and over 11,000 columns, all well documented (and none of these are a result of automated table/column generation; everything has a purpose and was created by a developer at some point). I have no idea how many rows but we must be up in the billions by now. I have no idea what will happen when the old devs retire. Creating a replacement software is next to impossible. It just does so many things.
@@MindBlowerWTF I have never used such a complex software. Quite frankly, I believe most software is way more convoluted then they need to be. Why? Because simple is hard. It is easier to keep tacking stuff as you need it than to figure out a small but expressive set of operations. You generally only have a much better idea how to abstract things when you have a bunch of repetition everywhere. Is his software well made? I have no idea. But that's why I am asking. Take vim for example. It has no business being as big as it is. Or python, which is another monster. But of course everything takes time. Perhaps it just doesn't make sense to spend time to pay off technical debt and make the project leaner. Or it just doesn't suit short term goals. Also, why the condescending attitude?
0:20 When I got into my first job, I took over some codebase. Most of the things my predecessor did seemed stupid, and I still think, they were stupid, but some really weren't that stupid.
I faced a codebase with 20 years of history in C++ and the codebase keeps changing for new features and new platform … One my of colleagues wrote majority of the code, when I faced some issue due to historical reason that he exactly know why and what needs to be changed. 😅
I imagine that it's basically all custom bit encodings and data transformations to display wierd custom sensors to some display. But might as wel be some crappy hacked together medical platform.
Keywords: medical software. So large testing and acceptance process. Making a single line changes is a business process unto itself, ADDING lines an enterprise. Your laughing , every line he wrote was a monumental task of rigor and your laughing, your laughing!
Hahaha! I've been working on that kind of project myself. I think it was legacy from the start (DOA, lol). The codebase is large and even the traversing is pretty time-consuming. Those guys made their own CMS engine which I believe is an achievement on its own. The extensibility probably was a point but it's implementation is poor. Since some management have changed we're more open to transit to some solid and tested and documented platform.
3:20 Writing code with AI is probably around as good as letting an intern program, who just copy pastes stackoverflow without knowing what that code does. Oh, I hate when people just copy paste code. I like to copy paste code, but at least I do some basic things like doing an auto formatting, rename the variable names to make more sense, change everything to fit my coding style, maybe introduce intermediate variables to make it more understandable if too much is done in one calculation (or remove intermediate variables if every small step has a variable), and remove all comments.
Heck, lots of people I work with have spent most of their career in the same code base. That's what happens when you work on a production program with loooong legs.
Actually your ipad's mic stopped earlier than it should have. I had to shut it off cause it was messing with the camera and my view of your scrumptious bare ass.
Hundreds of lines of code? Keywords: medical software. So large testing and acceptance process, mothership levels of bureaucracy. Making a single line changes is a business process unto itself, ADDING a line? That's an enterprise. Are you laughing? Every line he wrote was a monumental task of rigor and your laughing, your laughing!
A huge let down I'd say I thought this is going to be great article cuz you reacted to it but you baited me into watching this video that had almost nothing to learn 😂
It's a pretty crappy practice to not write explanation of a hacky thing your code does. We should ideally avoid comments unless it's a public API (such as library, web API) but if you know your code is doing something weird, you must write an explanation to avoid wasting the other devs time (which could be you if you visit it after a few months away from it!)
I worked on 15 year old code base for about two years. The initial 10 years was by the first guy, next couple of years second guy and i was third person to ever touch the code. Pretty unusual project i think. First guy was worried about memory and used global variables for everything, and second guy tried to refactor things and was a bit of an architecture astronaut and did things for "future extendability" leaving tons of dead code. Everything was so tightly coupled that you couldn't isolate or identify source of bugs. This was grand example of spagetti code. This was great learning experience with all of the anti examples. Global variables with multiple reads and multiple writes were common things. I feel bit anxious just thinking about the project. I just couldn't make anything work without a full exhaustive debug session. It took me months to do anything. Now i use rust and i couldn't be happier
I started working in my current codebase in 1998. Its origins dates to sometime in the 80s. Not gonna lie, it feels pretty familiar and comfortable by now. Granted, the frontend has changed a number of times over the decades, but all the logic is in the database so the frontend is more a matter of configuration than programming (creating the actual frontend framework and tooling isn't my department).
Please tell me the logic isn't actually in the database in the form of stored sql procedures.
@@82TheKnocKYPL/SQL all the way, baby.
@@82TheKnocKY Of course it is. It's how InfoSec taught everyone to do it for security's sake!
@@82TheKnocKY That's gotta be the only way to improve on JDSL.
No wait, that'd actually make JDSL run faster I think.
@@82TheKnocKY some of my company's web page functionalities are stored as jsons in a database. I looked at it and said "there's no way this is right, lol". But then you think again and you're like "oh, you can add functionality to the page (say, buttons with stuff in them) by just coding in simple SQL", and now I don't know what to think
Man Spends ENTIRE Life In A Crappy Code Base and now young dev will rewrite everything in RUST ???
classic
i feel scammed by clicking on this video
I feel the same for every video.
What are you talking about?? You always learn something from primeagen
@@Gohealtthe name
@@GohealtIf you aren’t learning, then you’re laughing… =]
Hella funny… 😊
I feel scammed by reading your comment
He was also the maintainer of right pad
O'rly? Seriously?
I'm not sure if you're joking or not, but the controversy was with left pad, not right pad.
@@flynn3649 that’s the joke
@@rarogcmex yes, absolutely serious
In the defense world, it’s not unusual to stay on a single product line for 10, 20, even 30 years. Many programs take 10 years to first release and then they last 20 years or more. There’s pros and cons.
Oh, ADA, I hardly knew ye.
More seriously, yeah. Been there. It's why all of my hobbies involve creating tangible things in relatively short amounts of time.
My life:
#DO NOT MODIFY THIS CODE
....200 lines later
# I *TOLD* YOU NOT TO MODIFY THIS! WELL DONE, YOUR WARNINGS ARE PROPHECIES
My favorite is the comment:
The same but a tick mark for how many times it's been tried
the war & peace of wingdings is my new favorite metaphor
I’m a year into working with a decades old codebase. I also feel like a “member of the team”, but I figure in another year I’ll be almost indispensable and they won’t be able to fire me.
"The War and Peace of wingdings" sounds bloody horrifying... Like I'd rather face off against John Wick. At least that'd be over quickly.
Death by John Wick much nicer than death by The War and Peace of Wingdings
"adult salmon cat mix"
ah yes, the blended up cats I feed my salmons for lunch
I've just been sitting here wondering wtf a salmon-cat is...
"There are making Human animal hybrids!"
When you find stupid code and it was yourself 1 year ago T_T
This was scarily familiar. I currently work in IT, maintaining a 35 year old software that is still actively developed.
The database part of it consists of more than 700 tables and over 11,000 columns, all well documented (and none of these are a result of automated table/column generation; everything has a purpose and was created by a developer at some point). I have no idea how many rows but we must be up in the billions by now.
I have no idea what will happen when the old devs retire. Creating a replacement software is next to impossible. It just does so many things.
Damn, why is it so big?
@@alan5506 what, you are going to release another product that does one small thing? No, you add it as a feature - do this 10000x times.
@@MindBlowerWTF I have never used such a complex software.
Quite frankly, I believe most software is way more convoluted then they need to be. Why? Because simple is hard. It is easier to keep tacking stuff as you need it than to figure out a small but expressive set of operations. You generally only have a much better idea how to abstract things when you have a bunch of repetition everywhere.
Is his software well made? I have no idea. But that's why I am asking.
Take vim for example. It has no business being as big as it is. Or python, which is another monster.
But of course everything takes time. Perhaps it just doesn't make sense to spend time to pay off technical debt and make the project leaner. Or it just doesn't suit short term goals.
Also, why the condescending attitude?
The old devs needs to write as much documentation as possible before they retire and needs to be a priority.
0:20 When I got into my first job, I took over some codebase.
Most of the things my predecessor did seemed stupid, and I still think, they were stupid, but some really weren't that stupid.
I faced a codebase with 20 years of history in C++ and the codebase keeps changing for new features and new platform … One my of colleagues wrote majority of the code, when I faced some issue due to historical reason that he exactly know why and what needs to be changed. 😅
3:21 I've seen it, and holy moly. It's like you could see the gears turning... if they ever did.
35 yrs, hundreds of lines of code. Did he work 1 day a week?
most of the code was deleted
That's like 5 minute a week man
In bad enough codebase riddled with indirect references even changing one line can be a gamble.
I imagine that it's basically all custom bit encodings and data transformations to display wierd custom sensors to some display.
But might as wel be some crappy hacked together medical platform.
Keywords: medical software.
So large testing and acceptance process.
Making a single line changes is a business process unto itself, ADDING lines an enterprise.
Your laughing , every line he wrote was a monumental task of rigor and your laughing, your laughing!
Hahaha! I've been working on that kind of project myself. I think it was legacy from the start (DOA, lol). The codebase is large and even the traversing is pretty time-consuming.
Those guys made their own CMS engine which I believe is an achievement on its own. The extensibility probably was a point but it's implementation is poor.
Since some management have changed we're more open to transit to some solid and tested and documented platform.
3:20 Writing code with AI is probably around as good as letting an intern program, who just copy pastes stackoverflow without knowing what that code does.
Oh, I hate when people just copy paste code. I like to copy paste code, but at least I do some basic things like doing an auto formatting, rename the variable names to make more sense, change everything to fit my coding style, maybe introduce intermediate variables to make it more understandable if too much is done in one calculation (or remove intermediate variables if every small step has a variable), and remove all comments.
oof that hurt.
5 years at my company and I almost understand most of the code-base of our million lines of garbage code.
Just a million? Let the dick waving contest begin!
Nah, just kidding. But big projects are a special kind of thing.
the only way to get a short video (less then 40min) from The Prime
Why dumpster diving is bad? How else would you find new revolitionary js libraries on npm?
Heck, lots of people I work with have spent most of their career in the same code base. That's what happens when you work on a production program with loooong legs.
wtf I always shower with you on and I just assumed my iPad died. you left my zoomer brain without stimulus for a whole 4 minutes. baitagen
Actually your ipad's mic stopped earlier than it should have.
I had to shut it off cause it was messing with the camera and my view of your scrumptious bare ass.
Hundreds of lines of code?
Keywords: medical software.
So large testing and acceptance process, mothership levels of bureaucracy.
Making a single line changes is a business process unto itself, ADDING a line? That's an enterprise.
Are you laughing? Every line he wrote was a monumental task of rigor and your laughing, your laughing!
Junior devs without projects are getting hired ?
I first assumed this was about Bill Gates in the shitty Windows code
3:12 The head of IT @ cisco said the same thing in interview with David Bombal cpl weeks ago. 5x more tech jobs.
I'm not sure if I feel better or worse after this
Since we are all equally apt? Yeah?
I know how much senior developers having worked in two languages over some 12 years believe that to be true.
Your comment seems to be missing context XD.
Unfortunately, I dont read minds so you sound like an idiot.
sounds like a horror movie.. surviving a horror movie
I dont understand the last sentence, is prime saying writing code with AI is a good thing?
Im a complete noob in coding, but i love this channel XD.
Sounds like the creator of Dwarf Fortress
A huge let down I'd say I thought this is going to be great article cuz you reacted to it but you baited me into watching this video that had almost nothing to learn 😂
It was under 4 minutes long. Get over it lol
@@AggressivesnowmaN fair point 😅🤣
@@TechBuddy_ cheers haha
here is your learning -> Don't just write hundreds of line code in your 35 year career, otherwise you will be eating "adult salmon cat mix" :)
@@amitdhaterwal8395 I only eat chicken
COBOL works well... Whys should i switch :)
Rust is woke! Camel? That’s a cigarette brand!
It's a pretty crappy practice to not write explanation of a hacky thing your code does.
We should ideally avoid comments unless it's a public API (such as library, web API) but if you know your code is doing something weird, you must write an explanation to avoid wasting the other devs time (which could be you if you visit it after a few months away from it!)
Linux is now over 30 years old.
Probably not even using automake.
So you're saying that he didn't jump companies every week bc the new job had a PS4 in the recreation room? CAP
typo in the first sentence lol
I rewrited it and didnt make the stupid thing🤣🤣🤣
If you find out why a stupid thing is there: write a comment.
This is satire….
right?
Hilarious!
Love from Syria ❤❤❤❤❤
Are you Syrious.
@@changoviejo9575 Syrious Black
@@MayyasNakhli Syrious Lee?
Nah programmer will get hold of ai and will teach it how to deal with silly mistakes, THEN ai wiml replace programmer
🤣😂🥲🙂😐🫤😢😭
hi
omfglmfao
Is this clickbait?
No views
beuaitufl
really bored
First
Fist