This isn't unusual, I went through a similar experience with C++ at some point. It's satisfying to tardwrangle the language, but ultimately it's satisfying for the wrong reasons, so unless you're programming for the sake of masturbation, you eventually tire of it after facing a roadblock one too many times.
many programmers love to make programs in esoteric languages such as brainfuck for a little bit of fun...
...and unfortunately, nobody really wants to use esolangs as their main language, because it gets tiring quick
But people are willing to use JS for even the backend via node. So at least one esolang is widely used.
you have arguably already succeeded
To follow up on @Creative Username 's suggestions, something I should mention is that change and progress usually happens as a response to some kind of perceived need. Nobody changes for no reason, so I think the thing to do is to continue exposing yourself to new ideas and concepts, but especially new problems. The easiest way to know you need to improve is to run into a problem you can't solve at your current skill level, but beyond that, staying curious and digging around in anything from others' code or design principles or even just discussions like this will passively bombard you with new concepts and ideas, and you should put the work in to try to at least look into all the stuff you don't know.
They both appear to have jumped into a big passion project that they couldn't handle and their ego will not allow them to abandon/shelf/rewrite (or accept criticism/advice). They also both take money to support the "development" of their games, so they have quite a strong incentive to never actually finish, or take time away from the project in order to improve their skills. The programming/game is a secondary concern.
Look into Exercism, where you can get more than automatic pass/fail grading, but real human input
They have neither the ability, drive or reason to improve. You need someone who will give you tough criticism and goals to go with.
Not necessarily "tough" criticism but otherwise yeah. Since I just mentioned Exercism earlier, as a mentor (which I've been a few times), you get instructions on being tactful and delivering constructive criticism. I consider these guidelines mostly common sense but there's a lot of uh ... let's say "neurodivergence" in coding.
I think that could run afoul of the "premature optimization is the root of all evil" principle. For me it would be writing something truly worth of those kinds of architectural considerations.
Try building Netflix’s microservices architecture with federation. What have you got? A few downloaded movies and one user? It’s not possible for one person to build anything worth "those kinds of architectural considerations." We’re talking about the results of decades of work, thousands of engineers, and business evolving to meet new uses that just so happen to fit the current logistics.
My books on this subject matter involve examples that fall well short of building a new Netflix
Sound like you’re prematurely ejac...optimizing to me.
I'm not entirely sure what that's supposed to mean here
He's making fun of your nationality.
programming a system as a bunch of uml diagrams before writing it in a language is only one of the million different ways you can develop programs
what if op wanted to program for fun? endless uml diagrams can't draw pretty pictures on the screen
see he doesn't like a good pipe he thinks you need a funny diagram with several boxes and lines between them instead of typing |