4 ms·
The they will not hire you for writing spaghetti code. You can't win! :)
by asimuvPR 11y ago
The they will not hire you for writing spaghetti code. You can't win! :)
- nardi 11y agoI assume you're using the phrase "spaghetti code" to mean "hard to understand code." This is not what spaghetti code means.
- asimuvPR 11y agoDon't be shy then, what does spaghetti code mean exactly?
- Ericson2314 11y agotoo many gotos, originally http://www.u.arizona.edu/~rubinson/copyright_violations/Go_To_Considered_Harmful.html http://www.u.arizona.edu/~rubinson/copyright_violations/Go_T.... More broadly code lacking structure, hard to compose, or improperly not composed of smaller components.
- Retric 11y agoA tangled controle structure. Think lots of jump/goto statements or multiple recursion through multiple functions a>b>c>a>c>b... The idea was mapping flow looked like a tangled mess.
- drdeca 11y agoEdit: I forgot to check if there were other responses already. Oops! Never mind. Also, in addition to being late, I was also wrong (or, at best, partially wrong) Doesn't it usually at least connotate having large amounts of code, often repetitive code? Especially code that should be split into smaller functions? I thought that was the case, but I would not be surprised that it is also used more broadly
- Retric 11y agoIt's generally the other end, where there is 'not enough' code. Early systems needed to be like this because there was very little memory for your code and people would often do things use calculated jumps based on some register value. Not to mention the joys of self modifying code. This all sounds cool until someone actually hands you "Mel's" code: http://www.pbm.com/~lindahl/mel.html http://www.pbm.com/~lindahl/mel.html PS: Beginners or Evil people, would also get into horrid messes by trying to get something that sort of works into something that almost worked.