How Code Bases Survive

All Clips are from the live stream of ThePrimeagen

Wanna Become a Backend Dev & Support me at the SAME TIME???

[AllWeAreBadKids]

Yeah the times I feel I grew and learned the most was on crappy projects

[leomac]

Dunno how Prime does it, but now I'm really looking forward to my next set of failures.

[NotherPleb]

I don't disagree, but people tend to misuse this point to argue it's fine to poorly design software like "it's gonna be rewritten anyways". The best code is not the one that's never deleted, it's the one easier to rewrite.

[nerdycatgamer]

its insane how many comments are missing the entire point.

all code bases start with your 90-99 percentile dev who builds 'the rails' (all the infrastructure and architecture for the codebase), and then they quit after X amount of time.

the remaining people keep tacking onto that codebase in the *exact same way* (no refactors, no intelligent design, just slapping code on top of the pile), until eventually it 'runs off the rails' after some Y amount of time and cannot work. this is not the point that you need a refactor, this is years after you needed a refactor, but your 90-99 percentile dev isn't around to be like 'alr we need a refactor'.

the LLMs haven't been trained on that 90-99 percentile dev, because LLMs are trained on the median. the LLM has learned from the devs who just 'tack onto the pile', so instead of getting that X+Y lifetime for your codebase, you're just getting at most Y, and that lost time is the exact amount of time you needed to take off and start making money.

[xff]

Everything sucks and eventually fails. Don't fight the laws of the universe. Embrace the suck and live with it.

[neks]

what does it mean a code that works? ofcourse when im finished making a project it works. how can it stop working by itself? does he mean that it cant be evolved furhter?

[noredine]

Does that mean hindsight feeds into foresight?

[felix_xb]

Whats the context for the part at 00:35 (LMM? whats that?)

[elieobeid]

code will work forever as long as it provides business value, it can live and be refactored. This opinion is wrong and the proof is that most of the banking sector uses cobol and lives even though it's crappy

[That_Guy_You_Know]

In your example of making code that works for X months: I assume you mean works while scaling users? Or do you mean works while you have N developers working on then project also? Or do you mean it simply just runs for 6 months?

Lost me on that one.