Is't spagetti code a design pattern? One can make use of design patterns, clean code and separation of concerns and still get working spaghetti code without al

Is't spagetti code a design pattern? One can make use of design patterns, clean code and separation of concerns and still get working spaghetti code without all the hacky stuff. Much less effort if use C. Engineered C case studies as goto solutions! https://blog.feabhas.com/2017/02/abusing-c-switch-statement-beauty-eye-beholder/ https://blog.feabhas.com/2017/02/abusing-c-switch-statement-... https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html Just have to impliment the program as if it was an OS. aka mix/match abstraction levels! Mix/match assembler / language macros / foreign language calls to other language libraries Use C20 ability to assign case statement(s) to a thread (mixed with remote procedure calling and/or function stacks across multiple threads) Mix & match unicode/non-unicode, hex, ascii, etc. where text is code that can be run. Mix and match C# language extensions in which same thing can be implimented different ways (e.g. strings, vectors, templating)