3 ms·
It took me by surprise too, but now when I give a training, I make sure I include how to: - read a stack trace - find things in the doc - use the debugger M
by BiteCode_dev 7y ago
It took me by surprise too, but now when I give a training, I make sure I include how to:
- read a stack trace
- find things in the doc
- use the debugger
Most people, professional devs, signing up for my __advanced__, yes, specifically requested to be advanced, Python trainings, don't know how to do this.
Again, I try to be extremely nice about this, because nobody likes to feel inadequate and I'd rather have people learning happily this and improve their life and work.
It takes a lot of courage, if you are 40 and being in the field for 2 decades to admit you need to go back to this.
But it's not what I was expecting from the industry.
Hey, it makes me feel useful :)
- ci5er 7y agoGiven that Python belches stack traces anytime you look at it funny, I can't understand how that could be...
- jschwartzi 7y agoHey man, I * scrolls back 6 pages * love a good stack trace.
- enedil 7y agoGood that there is a stack recursion limit in Python.
- tomrod 7y agoI see you too forgot a comma once in a Java program.
- KptMarchewa 7y agoTemplate compilation errors in C++ were at least 300kb last time I've tried to use that language.
- jschwartzi 7y agoI've gotten my fair share of those from use of Boost.
- blaser-waffle 7y agoMy guess would be that a lot of coding is autodidactic, aka there is a lot of self-learning, trial and error, etc. This means you learn a lot of bad habits, or develop gaps that a formal training course would avoid. So when you get to something that is complicated and has the potential for deep strategies and shortcuts for efficiency (e.g debugging), it's no surprise that experienced coders might want a refresher. Impostor Syndrome may be a thing there, too.