4 ms·

I will admit, I forgot that description as I got deeper into the content. In terms of managing the struggle, though, at least in my experience, a lot of it com

I will admit, I forgot that description as I got deeper into the content. In terms of managing the struggle, though, at least in my experience, a lot of it comes from having broken models of effectiveness. The net result is having to use a lot of emotional energy attempting to discern what the optimal answers are in a deeply ambiguous sea of grey, with the added difficulty of especially ruthless hindsight. Again, maybe my expectations were grossly miscalibrated, but there wasn't much in terms of orienteering in that environment. What advice there was: the regular, time-boxed 'containers' of learning, struck me as deeply taxing on someone who struggled with context switching or executive function. Further the exhortation to seek out like-minded peers would be especially painful (non-?) work for someone with social anxiety. I guess what I wrestle with reconciling is the desire to unconditionally affirm and pastor those in the depths of their struggle, with the advocated actions that would often be inconceivably costly to those most in need of that affirmation and support. Maybe the impersonal written word is a sub-optimal medium for this mission?

svilen_dobrev 6y ago
i have been mentoring wanna-be programmers for a while. 15y old and 40y old. Men and Women. In big companies and in tiny companies. For few weeks, and for many months. And... most do make it. Some don't. Not very proportional on abilities/capabilities, AFAI see them. It seems to depend on internal flame.. and some humility. Internal eagerness to do exactly that thing, And be useful. That desire keeps one growing, trying, failing, rising again, finding ways, learning about self by looking from "aside" (controlled shizophrenia IS the state of programmers mind), asking others, helping others, and repeating.. Common advices are difficult, everyone's struggle is different. Hence these taste like usual mumbo-jumbo.. here are some: do not fight your daemons, harness them. Find out weaknesses, and walk around them. Far away if need be. Or straight across them under different angle. Observe and study everything about yourself. Not all weaknesses are equal, are most are not weaknesses per-se, it's the perception that gives them the name. Ah, and same thing about the strenghts - Sometimes it might be better to avoid to ride a strength as it may take you too far, too fast.. There are many many meanings of the word "better", in "better programmer".. i'd prefer the ones closer to "better person" than to "ultimate machine". And.. the ambition.. may not be the best tutor. Persistence.. might be better. It is important to find yourself a project/s of your own. Nothing too great, can be tiny or insignificant to others. Then don't give up until you do it. And.. Have Fun. If there's never fun, then this isn't your thing. Abstractly said, programming is the ultimate boredom, and i only manage to do it for 35+ years by searching new ways of finding fun. Nowadays it's mentoring people. What's next.. will see :)

svilen_dobrev 6y ago

i have been mentoring wanna-be programmers for a while. 15y old and 40y old. Men and Women. In big companies and in tiny companies. For few weeks, and for many months. And... most do make it. Some don't. Not very proportional on abilities/capabilities, AFAI see them. It seems to depend on internal flame.. and some humility. Internal eagerness to do exactly that thing, And be useful. That desire keeps one growing, trying, failing, rising again, finding ways, learning about self by looking from "aside" (controlled shizophrenia IS the state of programmers mind), asking others, helping others, and repeating.. Common advices are difficult, everyone's struggle is different. Hence these taste like usual mumbo-jumbo.. here are some: do not fight your daemons, harness them. Find out weaknesses, and walk around them. Far away if need be. Or straight across them under different angle. Observe and study everything about yourself. Not all weaknesses are equal, are most are not weaknesses per-se, it's the perception that gives them the name. Ah, and same thing about the strenghts - Sometimes it might be better to avoid to ride a strength as it may take you too far, too fast.. There are many many meanings of the word "better", in "better programmer".. i'd prefer the ones closer to "better person" than to "ultimate machine". And.. the ambition.. may not be the best tutor. Persistence.. might be better. It is important to find yourself a project/s of your own. Nothing too great, can be tiny or insignificant to others. Then don't give up until you do it. And.. Have Fun. If there's never fun, then this isn't your thing. Abstractly said, programming is the ultimate boredom, and i only manage to do it for 35+ years by searching new ways of finding fun. Nowadays it's mentoring people. What's next.. will see :)