63 karma · joined August 25, 2017
Good developers can also hop from one job to another and make more and more money in the process.
Job security is a thing of the past, whether you went to school or not.
The "ideal" developer isn't some kind of monk who dedicates his entire life to one firm.
Making money doesn't mean your product is bad, useless or badly designed. It also doesn't necessarily mean you're the best salesman.
Sometimes experienced developers without a CS degree and without sales skills still get paid a lot because:
A) the requirement doesn't call for advanced computer science knowledge
B) the requirement does call for a significant amount of practical experience and business knowledge
C) it's a highly profitable industry and the specific work being done will generate the company profit and/or cut costs
It can be perfectly legitimate to perform jobs like this without having a CS degree or ever intending to get one.
It can be perfectly legitimate to work your way up the ladder of such jobs and jump from job to job in the process.
Some of us want to raise a family and/or be able to retire one day. Why should we put our careers on hold to pursue a degree?
I think I am interested in the fundamentals of this field, at least enough that I've been reading some of the books and papers in my spare time. If it was just a matter of interest and curiosity, I guess I'd just keep up the reading, which I can do for free anyway.
But I would only invest in a degree if I thought it would boost my earning potential in the Valley. Otherwise it seems better to just keep working full-time, maybe do some short courses here and there.
See this website: dollarstreet.org.
Looking at the photos of some of the poorest places, I suppose they're undesirable from my perspective now, but if I moved there and lived there long enough and adapted, I could see myself finding contentment with less.
For more info about this lifestyle, see this website: http://earlyretirementextreme.com
While I certainly believe in self-documenting code where possible, I think there's a place for comments, and also for well structured comments.
I wouldn't recommend going haywire and commenting on every HTML element, attribute, etc., any more than I'd recommend using any other language facility or tool like a sledgehammer.
But that's not to say structured commenting isn't a useful tool for the right situations. I have found the JSDocs in the code-base of Angular and other libraries to be invaluable, on occasions where it wasn't possible to fully convey the meaning in pure code.