2 ms·
I have been thinking this for years.... though I would consider myself an "early coder" according to the article. This stuck out to me as being just the beginn
by r0mbas1c 11y ago
I have been thinking this for years.... though I would consider myself an "early coder" according to the article.
This stuck out to me as being just the beginnings of the quintessential issue:
A beginner’s hurdle is training their brain to grasp the concrete problem of using syntax to create computation and then understanding that the syntax is just a proxy for how computation works. The early coder is past this, but now has to work up the abstraction stack to convert ideas and fuzzy descriptions into concrete solutions. It’s this traversing of abstraction and concrete implementation that I believe takes someone past the early stage and into the junior programmer world.
But why stop at just "beginner" "early" and "advanced". All of the books I have on programming are either truly "beginner" or blankly labeled as a programming guide, when in actuality it is quite "advanced"...nothing in between.
If, as the article states, 4 is the magic number of languages to learn up front, perhaps there should be a 4th level of programming guides....one for the journeyman who knows the syntax, can articulate the complex algorithmic issues that need to be addressed, but isn't quite at that "mastery" or "advanced" level.
- veddox 11y agoI think that's the stage I'm at right now (or getting there). But what is the divide between "junior" and "senior/advanced" programmers? And what would help somebody (me) push across that boundary?
- chadzawistowski 11y agoPlease don't use code tags for quotations! It doesn't wrap lines and forces readers to scroll in order to read the whole quote. Code tags are okay if you manually line-wrap, or you can precede quotes with a > and everyone should recognize it for a quote.