Discussion on: Please explain why I need software architecture

[Thien DX]

By following standard pattern/architecture, you're sacrificing short-term dev time for the long-term.
Usually you create more classes or code to solve what seems to be simple at first. For junior, trick/hacked solutions always look better if they don't see the long-term benefit.
If design pattern is used efficiently, future you or your teammate can easily understand the code / identify issue, from a higher level rather than go through the code details.

[Pacharapol Withayasakpunt]

Actually, I'd look for benefit of

• Make sense of my own code.
• The code can grow
• Well-tested for edge cases (and common cases)
• Handling the code more than a few months, where I have forgotten some of the internals