A Cautionary Tale of Learning to Code
blog.freecodecamp.com
A Cautionary Tale of Learning to Code
1–10 of 135 posts
Re: A Cautionary Tale of Learning to Code
#2Re: A Cautionary Tale of Learning to Code
#3Re: A Cautionary Tale of Learning to Code
#4Re: A Cautionary Tale of Learning to Code
#5Re: A Cautionary Tale of Learning to Code
#6[deleted]
Re: A Cautionary Tale of Learning to Code
#7Re: A Cautionary Tale of Learning to Code
#8I personally think every programmer should know some C. Basic things like what the stack and the heap are.
Edit: Ok, probably not in the case of absolute beginners, but after a year or two...
Re: A Cautionary Tale of Learning to Code
#9But in some other ways, the author is too self-critical:
> I'd spent months sitting alone in libraries and cafes, blindly installing tools from the command line, debugging Linux driver problems, and banging my head over things as trivial as missing parenthesis.
All these things have value, and I doubt that this was time truly wasted. Although some people can get by for a while without it, becoming intimately familiar with the command line is extremely valuable. Also, although this is by no means a requirement for being an effective programmer, most good programmers I know use a traditional text editor such as emacs or vim.
Ultimately, I think the point is that expending time is an investment, and you should prioritise based on the expected future utility from your time investment. More often than not, this means finding the most important thing and putting almost all of your energy into it.
Re: A Cautionary Tale of Learning to Code
#10Great article.