Oh. No. I’m sorry, unrelated to the ai debate, but I have to correct this. Software architecture is intensely not raw logic sequences like you learn in uni. Everything before compilation is cooperative abstract modeling that does not necessarily impose any change at all in the binary. You are essentially teaching laymen that all programming languages for the same plattform are a creative choice, that extensibility, robustness, scaling or maintenance are just completely imagined fields of research. I’m sorry but that statement is complete nonsense misinformation. The binary itself, while it’s a stretch; sure, in a way it can be considered only logic. From a certain angle. But that viewpoint is actively unhelpful for understanding what code is. The product is always so much more than the machine code. Consider writing raw arm instructions vs the obfuscated js that our engines churns through that decides most of our executing logic. All that is architecture and affects output only through the lens of the machine code. You have to enter the "code“ any time anything breaks, or is updated, if even a single thing is not as expected, or if you wanted to iterate on the program, or collaborate, you have to move into abstract land and then the architecture matters. The term spaghetti code does not mean that the logic is messy. The compiler wil usually remove most such mistakes. Instead the whole architecture, the “blueprint” the “workbench” is the magic of code, even if it is often obscure for the user is much more important for their experience than the raw logic.
Oh. No. I’m sorry, unrelated to the ai debate, but I have to correct this. Software architecture is intensely not raw logic sequences like you learn in uni. Everything before compilation is cooperative abstract modeling that does not necessarily impose any change at all in the binary. You are essentially teaching laymen that all programming languages for the same plattform are a creative choice, that extensibility, robustness, scaling or maintenance are just completely imagined fields of research. I’m sorry but that statement is complete nonsense misinformation. The binary itself, while it’s a stretch; sure, in a way it can be considered only logic. From a certain angle. But that viewpoint is actively unhelpful for understanding what code is. The product is always so much more than the machine code. Consider writing raw arm instructions vs the obfuscated js that our engines churns through that decides most of our executing logic. All that is architecture and affects output only through the lens of the machine code. You have to enter the "code“ any time anything breaks, or is updated, if even a single thing is not as expected, or if you wanted to iterate on the program, or collaborate, you have to move into abstract land and then the architecture matters. The term spaghetti code does not mean that the logic is messy. The compiler wil usually remove most such mistakes. Instead the whole architecture, the “blueprint” the “workbench” is the magic of code, even if it is often obscure for the user is much more important for their experience than the raw logic.