[true_religion]

So, we're engineers---very much not the average person.

Speaking from the point of view of someone who spent 8 years in school learning computer science, then the next 15+ practicing it:

I cannot create an RTS game engine in C. Not in a million years.

It's all good and well to be encouraging, but this is literally our field. If we can't identify our own short comings accurately (after for some people is decades of experience), then we are probably less capable than we think instead of more.

[isbadawi]

I don't understand why you wouldn't be able to, especially given "a million years" to learn whatever you need to learn. Why does it feel inaccessible to you?

[true_religion]

I'm not good at implementing algorithms that directly relate to mathematical equations. I learned this from 1 year banging away at computational photography while in university and 2 years banging away at automated trading systems at one of my first jobs.

Given enough time I can copy other peoples implementations, but its extremely mechanistic to the point where you can't say that I actually 'wrote' it or learned anything. And it would be questionable if all the functionality would fit together as a succinctly as the posters.

I hope you don't think that is goal post moving, but if I do something mathematical in order to get it correct I have to sacrifice everything else: speed of production, efficiency of the end-product, readability of the code, etc. Compared to my output in logic problems or HCI, you'd think two entirely different people were involved and one was significantly smarter.

It's a failing (of the sort where asked "What is your biggest weakness?" at an interview, I can always answer immediately this), but it's what allows me to be impressed with work like an entire RTS game engine in C in just 3 years as a passion project.