The Object-oriented Version of "Spaghetti Code" is "Lasagna Code" ?!

Key Takeaways

hey everyone um so I got some I I posted this quote uh yesterday no actually couple of days ago and I got some really interesting responses and um 140 characters is just too short to reply to this so um I decided to do a quick video reply also I'm trying out this new this new screencasting tool um so yeah so the quote was the object-oriented version of spaghetti code is of course lasagna code because you're ending up with too many layers and layers of abstraction that is and so yeah I got some really cool responses here from from ABI or I I hope I pronounced your name correctly ABI U he was saying or if you're in the microservices world ravioli code everything in its own pocket just thought that was hilarious that that's a great quote I'm I'm gonna make that another quote on uh that that I'm going to post and then uh assign you as as the author mention as the author as the author and we're going to see what happens um yeah now I want spaghetti I hope you're proud of yourself yes Tain that's I had spaghetti the last two days and I wonder if it has anything to do with that tweet so definitely had the same effect on me H all right and so Tobias writes uh how to avoid this is something wrong with the single responsibility principle and uh I think that's a pretty good question right because um well the the way I would interpret this is that the um uh too much of a good thing is a bad thing or you know it all depends on the the dose and I think it's with it is like that with any of these tools right like a tool or um a principle like the single responsibility principle it can be a really good thing for structuring your code and and writing better or more maintainable more readable code but you can also take it to an extreme and then you end up with something horrible right and whether that's called like lasagna code or or whatever um you know a giant like ball of twine code um you could totally take the single responsibility principle to an extreme I think where you basically you know you end up in this um your program is going to look like all of these joke examples for overly complicated Java programs right where you have like abstract Factory factories and all of these crazy design patterns applied in a way that just takes them you know into absurd territory and just absolutely makes them makes the result in code ridiculous and so I think like my interpretation here is that the quote is exactly about that I mean first of all like I think it's a bit of a joke but uh it it goes to show that you know too much of a good thing is a bad thing so if we if we go and just take you know object Orient orientation or the single respons a single responsibility Principle as like the only Hammer we have and we try to apply like to any nail we can find then I think we're going to end up with something horrible like lasagna code and um the way to avoid this is I think to know about many of these tools and to build up this kind of experience or feeling for when to apply a certain tool right in what situation um you want to apply one one of your many Tools in your toolbox so I think that will be that will be my strategy to avoid uh overlying one of these principles or one of these um these methodologies and you know it's the same with everything it's the same with like agile you know we probably all heard or worked at places where that was just taking that was being taken to you know too far you can be too agile and you can kind of you know you can spend all you know hours every week in Retros and all of these like meta things that don't actually help get the work uh help get the work done and so it's the same thing with these these the sign patterns and stuff so okay so a bit of a rambly answer there but I hope this helps you out and um I'm just going to post that to Twitter now see what happens