lizzy مثلية الله ☭ 
lizzy@social.vlhl.dev
12
1
2
@lizzy I think that term already exists?
1
0
1
lizzy مثلية الله ☭
lizzy@social.vlhl.dev
0
0
0
lizzy مثلية الله ☭
lizzy@social.vlhl.dev
1
0
0
1
0
1
lizzy مثلية الله ☭
lizzy@social.vlhl.dev
0
0
0
Show content
0
0
0
lizzy مثلية الله ☭
lizzy@social.vlhl.dev
0
1
0
@lizzy It's priced in https://en.wikipedia.org/wiki/Spaghetti_code#Lasagna_code
0
0
1
Matthieu Urvoy
birozularutti@piaille.fr@lizzy I do love lasagnas, but here are a few tips to turn that into spaghetti lasagnas: https://youtu.be/WrfOiv1QO70?si=eRp8Oa8sRen91G74
- use polymorphism as much as possible
- use state variables as abundantly as possible, and make sure their representation is both ambiguous and redundant
- hide all calls to standard libraries into custom functions
- be more efficient and never lose time finding proper variable/functions names
- make objects unusable by construction, let the user codebase adjust their internal state at a later point until it may - or may not - become usable
- now you're lost. Introduce a new wrapper layer to hide the mess.
- repeat
0
0
1
@lizzy also, famously: https://www.johndcook.com/blog/2009/07/27/baklav-code/
0
0
1
@lizzy I increasingly feel like spaghetti and lasagna code are two ends of a spectrum and there is a small window in between where code is actually readable and efficient
0
0
1
Alexandre Oliva
lxo@snac.lx.oliva.nom.brit sucks that both refer to delicious food, though
it distracts from bringing the technical difficulties to mind
this reminded me of the conversation between shrek and donkey about layers: onions have layers, but so do cakes 🙂
0
0
1