I heard something like: "The second system you design will be the most over engineered piece of shit ever" I don't know who said it but it has been very true f

I heard something like: "The second system you design will be the most over engineered piece of shit ever" I don't know who said it but it has been very true for me and my close friends who work in software development. I remember first starting software development and I started to read up on "how to do it right" in the Java/C# world back when XML was everywhere. I had first started to expand my skills after university by building my own blog (who didn't at that time?) but thought I should rebuild it according to "best practices". Hoooooly shit that was a poorly architected and designed piece of software. The example in the blog was of course not as poor of an example as my creation but I feel that many end up in this trap after they have some experience that they need to do everything "right" and they don't have the experience to evaluate if it is worth it. However I also think a good workplace have a healthy mix because those youngsters will also push the old guard to learn new things and introduce new technology. Just need a balance between using 0.1-alpha libraries and things that were released 10 years ago.