I think I only respect things that truly seem not learnable or understandable. Anything that I can learn, I lose some respect for, because I can just use my brain and it'll be mine.
But today I told myself that's a dangerous attitude to have, because it completely devalues the fact to do a job well, which is a skill in itself.
But another part is the security courses I did at my university. When you're performing rowhammer, meltdown and all those type of things, then a lot of other forms of programming feel a lot easier. There's a ton of stuff in programming that I have a lot of respect for but CRUD apps isn't one of them. Concurrency, compilers, algorithms, AI at the PhD level or security (not a comprehensive list), those things are actually tough.
With that said, thanks for stating so clearly that you think I'm overconfident. I hope to find out ASAP if this is true.
How would I find it out?
Another reason is that I'm a digital creator at heart, not a programmer. Ultimately, I don't care about programming, I care about putting whatever is in my mind into the real world (despite that I did my best to learn CS as I did find it a valuable form of knowledge). And I find programming to be the most effective way to do that. I think creating CRUD apps is quite close to digital creation.
It's less of a headache (compared to other types of programming) and more visual (if you're full-stack or frontend).
Focusing on this and working "value creation" in to it will come across a lot better than anything that could be interpreted as "CRUD apps are easy and I'm looking to bludge for a while before I bail to something challenging again".
I thought I was a really good programmer leaving university.
Now I know I was useless the first 3 years. I only became someone I would consider hiring now after 5-7 years.
He came back from that a little, not much, but a little.
I wonder how you were useless and why you couldn't see that beforehand. Because I would like to be capable of diagnosing whether I'd be useless for the first 3 years.
As in: what am I not seeing?
1. It's not about writing code that works. That's the bare minimum. The real game is writing readable and maintainable code.
2. I had no clue that the most important thing isn't writing the code, but to work well as a team.
Also, I was just plain inexperienced. I had written a fair amount of code, but nothing like what you learn from doing in 40h/week, year after year. Raw talent is good, but it can't beat raw talent + experience.
A few problems you should be working on:
> nobody cares that I fast-tracked
> in terms of crystalized intelligence
> But my portfolio is rather terrible
> compared to what I'm capable of [*hint: Unless you did something that you can't show publicly, what you are capable of is nothing if what you did in terms of production is nothing]
I think you are over-confident when it comes to your skills.