Self-directed learning and exploration. I find that a lot of people are unwilling or at the very least not used to actually trying to find answers on their own, writing experiments or just doing things that aren't directly assigned in detail. This isn't to say, "don't ask for help," so much as one should at least try to understand and find answers on their own as an initial effort. Set aside an amount of time to dig in, google, look at results, read documentation, etc. After some effort has been made, then ask as needed.
It can go the other way too... which are those that won't ask for help after exausting days of effort on what may/should be a simple answer.
Aside from this, but similar and related is the understanding of what you're using. The tools, system and projects. Too many times I'll see devs re-create something that's already in the box, or easily put into the box. This includes adding massive libraries to a given project (how many date-time libraries do you need). Take the time to look at the build scripts, docker files, and project dependencies list. More so, if you're using a UI component library, spend the hour or so familiarizing yourself with the example pages demonstrating the library so you at least know what's there.
I agree with what you said. I fall into this trap from time to time. The most recent one occurred in yesterday. I was supposed to follow some tutorials to set up development in Windows using Visual Studio and a bunch of libraries (SDL2, gml, imgui, etc.). My first setup took about an hour and the sample project seemed to work when running in Debugger, but failed to start when clicked directly in File Explorer. I got so frustrated that I almost gave up. I did manage to muster some strength to start over, and fortunately this time it worked.
Situations like that reminded me how impatience I was, have been and am. What struck me most, is that back in the 70s and 80s, microcomputer developers (such as Romero, Carmack and others) usually did not have access to any tutorial or even books (unless one is lucky to live close to a university or a large public library). The best thing they had are the manuals and specifications, and they were free to shoot in their feet and figure out what might it be. Many people actually dropped out, but some of them persisted and managed to come out as the pioneers of the time.
At the age of 40+, I'm a bit ashamed that I'm not as persistent as them, when they were at their 20s and 30s back then. I'm thinking about getting some trainings or therapy sessions regarding my impatience.
>> At the age of 40+, I'm a bit ashamed that I'm not as persistent as them, when they were at their 20s and 30s back then.
Don't be and be careful what you wish for.
From my perspective their behavior is borderline unhealthy and almost like a type of OCD but by sheer luck directed towards stuff that pays good. Especially Carmac and Romero are bad role models - their life is really good story to tell (both books reads very well) but not to live.
Thanks. I'm mostly concerned by my lack of persistence. I did read both of the books, and yeah, I don't want to live their childhoods, although my own childhood is not particularly interesting and inspiring.
It can go the other way too... which are those that won't ask for help after exausting days of effort on what may/should be a simple answer.
Aside from this, but similar and related is the understanding of what you're using. The tools, system and projects. Too many times I'll see devs re-create something that's already in the box, or easily put into the box. This includes adding massive libraries to a given project (how many date-time libraries do you need). Take the time to look at the build scripts, docker files, and project dependencies list. More so, if you're using a UI component library, spend the hour or so familiarizing yourself with the example pages demonstrating the library so you at least know what's there.