Gregory's Server
This is an important notion to me on a personal level.
Many of my projects, I started before i understood how hard they were *supposed* to be - and then, once I saw the rising difficulty ahead of me, I just... stopped trying.
This was wrong, but I tend to think I'm smart, but not *arrogantly* so - if a lot of smart people are telling me that something's going to be hard, who am I tell them otherwise?
I'm understanding now why arrogance and humility are *both* considered important traits.
@pixx I feel like the difficult thing to hone in on is not necessarily self-belief (although it is critically the first step) but the delivery of self-belief producing results along the way to your chosen destination.
As an example, I used to choose monolithic projects that were outside of my skill set which didn’t necessarily have iterative successes along the way, or alternatively I would not choose projects with a focus on learning rather than result.
Take for example I’ve been wanting to learn more assembler but I know I only really learn things when I have a material goal I want to achieve. I’ve just discovered that I can’t access the RTC on my Z80 retrobrew from MBASIC so I need to rewrite my moon phase clock in Z80 asm.
At the core of that is knowing (as you alluded to) how I learn, and how that is not the same as everyone else learns and critically not the same as most people teach.
@pixx I feel like the difficult thing to hone in on is not necessarily self-belief (although it is critically the first step) but the delivery of self-belief producing results along the way to your chosen destination.
As an example, I used to choose monolithic projects that were outside of my skill set which didn’t necessarily have iterative successes along the way, or alternatively I would not choose projects with a focus on learning rather than result.