@StillGamingTM
What it used to mean: Code is tangled up in such a way that 1 change can break stuff everywhere - global variable hell, everything happening everywhere ad hoc without stuff being sorted into isolated modules What people think it means today: An isolated module that is not split into a bunch of separate files and/or code that isn’t split out at the top level into folders containing e.g. types, components, services (even when one particular component in the simple app only relates to one particular service relating to a handful of related types all chucked together, but somehow it’s considered “organised” since, well, the types are all in one place and that looks pretty and feels tidy therefore it must be the one and only right way even for a very tiny application performing only very basic functionality. I saw it in a massive enterprise app and therefore it must be the only way to organise code, even for tiny pet projects! It’s like having a cabinet for cups and a cabinet for plates and a cabinet for pots despite owning only three of each)
@adamkeasey655
What keyboard are you using?
@mementomori7160
I remember one of my early programs. You gave it a number 'n' and it searched for 'n' first prime numbers. I don't know how but I didn't know about things like "break" or "continue", but I knew "goto". Imagine this nightmare, I came back to it after a few months and I had no idea wtf was happening there.
@Diamond_Hanz
So what's spaghetti code again?
@nuotatorre8741
You made a very intresting video and even if I didn't understand much I still want to ask you something. Most of the time in the gameing space whenever a game isn't exatly well optimized and has somewhat frequnet bug and glitches, the most common thing it is sad to criticize it is "Oh XYZ game has spaghetti code, that is why it sucks". Even if I find than this accuse has some merit most of the time, it always seems to me like it's an unbrella word used by peopole to explain evrything wrong with a game without takeing in to consideration other factors. So is it true? Is spaghetti code a good aswer to explain evrything wrong with a game, or could there be other factors at play?
@paweld.9542
where are examples ?!
@MikkyIGuess
source spaghetti
@DonaldFranciszekTusk
Fajny opis napisałeś. W mojej głowie pojawiło się więc pytanie -- czy uważasz, że zdolności do pisania prozy idą w parze ze zdolnościami do pisania kodu? Pozdrawiam.
@sandipansarkar9211
nice and easy explanation
@Yarkanlaki
I am new at company most left overs are spaghetti codes
@Scudmaster11
Im a monolithic writer and i dont really care... modular is overrated.. along with so many (moduals) being just afew lines of code (not great).. bottom up isnt good.. stop using it... stop being afraid of deep nesting... never nesting is disterbing and annoying to use / debug
@TonySenpaii
Omg you are descripting my new job right now its a nighmare......
@mikolaj_lewandowski
I'm waiting for english subtitles my countryman :)
@LMGunslinger