2,359 karma · joined May 26, 2013
I think there are two separate problems here, though - one in which a particular individual is being assessed for his or her aptitude, and one where dozens or hundreds of applicants for a particular position must be evaluated on the basis of limited information, often from a pool of even more candidates.
A degree by itself is not a terribly reliable proxy for capability or potential, but better proxies are harder to scale and apply to many more people. Companies like degrees because they're an easy, lazy way to (at least in the minds of HR people) establish a competency baseline, and if it's true that most companies would rather have false negatives than false positives, it's easy to see why a degree would be "required" in a lot of cases. Hopefully that will change in the future.
From a technical perspective, I guess I'm impressed by the fact that he was able to marshal together the resources, time, and support necessary to make this happen. He's done similar stunts without killing anyone, so I'm somewhat impressed by his driving skills (although there's also the advanced safety technologies in his car, as well as the intrinsic chance you'll find yourself in a situation that could result in an accident). His endurance is also admirable - it must have been very difficult racing the clock for hours on end while maintaining extreme concentration. But then, there are also people who drive drunk, drive while distracted, or drive dangerously badly-maintained vehicles regularly, and nothing happens to them, so I guess that makes the 'reckless driving' aspect slightly less impressive.
The article makes it clear that he plans ahead, relies upon support, and tries to stick to straight stretches of highway. Good for him, and if he wants to risk his life doing 130 down a deserted highway at 2 in the morning so be it. But honestly, from the article, it looks like he has a habit of weaving through traffic at unsafe speeds, and as someone who's nearly been killed by insane drivers trying similar stuff...well, honestly, I'm not impressed.
If someone happens to find their job challenging, meaningful, and enjoyable, learns a lot, enjoys the company of their coworkers, and achieves their personal goals while working for a company or starting a business, why would the fact that other people are benefitting from their work put a damper on their enjoyment?
Or, like other commenters have mentioned, a job or self-employment might provide the income and opportunities to enrich one's life by living in an interesting place, getting to meet interesting people, supporting a certain lifestyle, enabling new experiences, and increasing someone's standard of living overall.
Don't get me wrong - I don't think that it's a bad thing, either, for someone to derive enjoyment from the mere fact that they aren't making someone else richer. And if that's what the author values, more power to him or her. But I really think it's sort of silly that the author is so puzzled that not everyone else thinks the same way.
If we're talking about sending people to Mars to live for long periods of time, and worrying about whether in doing so we're consigning them to miserable deaths, it seems like spending the money to work out the bugs in a non life-and-death situation might be a prudent idea. We've sent people to orbit the moon, we've landed people on the moon and robots on Mars, but we've never had people spending time on another world without relying entirely upon supplies they brought with them.
You can see the effect of years of exposure to soot on the faces of people who live in rural China (and, I daresay, anyone who lives in similar circumstances). These people are not living particularly environmentally clean lives right now (although, to be fair, they probably do consume far fewer manufactured goods than their city-dwelling brethren).
Something of interest is the prevalence of solar water heaters, both in urban and rural areas. They are surprisingly common, much better than heating water using fire or electricity, and affordable even to those outside the cities.
Presumably Chinese industrial espionage hackers would want to do more with their stolen schematics than let them sit untouched on a server somewhere.
I graduated college with a degree in electrical engineering not really knowing anything about what I wanted to do for a living or where I wanted to be in five or ten years. So I sort of drifted into a master's program, again in the same field, hoping to figure out what I was doing before I was forced to confront the job market or academia proper.
I didn't realize until the second half of my first year at that graduate program that I enjoyed the CS courses I was taking as electives far more than the normal engineering courses. So I ended up taking my second year and throwing all my effort into taking as many CS classes (which were cross-listed departmentally) as I could: operating systems, databases, compilers, etc. I made some stupid mistakes choosing some classes that turned out to be neither interesting nor relevant, and skipping on classes that would have been extremely useful or informative.
When I graduated, I took a position at a startup in the area, doing work that fell between the interface of EE and CS. I realized that I wasn't too fond of the work or the company (for various reasons), and so I spent months teaching myself the practical and theoretical stuff I had missed out at school, whether out of inexperience, disinterest, or sheer decision-making ineptitude. Some of this stuff was useful for my position at the time, other topics were completely exploratory in nature. And when I was ready, I started sending out my resume and interviewing for positions. I did get a new job, and I'm a software engineer at a well-regarded mid-size tech company in Silicon Valley right now.
Some thoughts regarding your position:
- CS is one of the fields with the lowest barrier to self-teaching. You don't need expensive lab equipment or fieldwork - just software, much of which is freely available, an ordinary computer, and enough motivation to actually utilize both.
- You don't need a 4 year degree. In the US a lot of schools won't even allow you to enter their bachelors programs if you already have one. A BS would be a waste of your time.
- The MS degree isn't a prerequisite. Build something substantial, and people will take notice. If you don't have anything you can show them, the degree can sometimes be useful. I'm not proud of this and it's actually really shitty, but the name of the school on your resume may sometimes make the difference between people taking a look at it and throwing it out (at least from my experience).
- If you do go back for formal schooling know what classes you should take, in order to acquire knowledge you need to have. You mention data structures and algorithms in a comment earlier; there are classes which focus on those; there are also classes that focus on discrete math, statistics, and other foundational topics. You should build an OS and a compiler while you're there. I always thought this was a thought-provoking read: http://matt.might.net/articles/what-cs-majors-should-know/
- A lot of MS programs are coursework programs; they've been charitably described as financially lucrative to their host institutions. Mine almost certainly would have qualified (both the EE and CS programs). This is not necessarily poison, but it does mean that if you attend, you should make the most out of the classes you take.
- If you are interested in working at certain companies, see if you can get someone to give you an internal referral once you're ready to begin the job application and interview process. A lot of companies (again, this is a controversial topic) seem to give more weight to internal referrals than unsolicited submissions. Contact with most of the companies I was looking at started either when a recruiter reached out, or when I asked someone I knew to put in a word. If you feel that people are loath to consider you due to your late start/lack of formal credentials this may be a way to offset that.
Finally, the fact that you are considering this move because of passion, interest, and demonstrated competence bodes really well for you. Best of luck!
Twitter probably seemed like a fake problem at its inception (post 140 characters to a personal blog from your phone), and yet it's been adopted and used daily by many, many people outside the Valley. Google's founders weren't thinking about ads when they first built their search engine, but apparently the ads they serve are considered lucrative enough by their customers to turn the company huge. (Of course there are the data privacy issues, but on a more cynical note someone's needs are being served.)
On the other hand, Better Place seemed like a useful idea. EVs presumably aren't more widely adopted because of range anxiety and charge times, so why not create a business model and technology to swap out batteries and make recharging as painless as filling up at a gas station? But Better Place is dead now and Tesla is building out its fast charger network and selling more and more cars.
It seems like there are at least two threads of thought going on in the comments in general. One of them is, "does C have any role in any domain, and if so what is that domain?". I think that it does; software development is much wider than kernels, userland applications, and compilers, and there are fields where C and/or C++ are the right tools as things currently stand. I don't think anyone would argue that either language exists as a global optimum in any problem space, but from an engineering (rather than a theoretical purism) standpoint sometimes there are few practical alternatives. Maybe these domains are small, maybe they're unexciting, but they do exist.
The other is, "what is the point of learning C?". Maybe they want a deeper understanding of manual memory management, the concept of stack and heap storage, pointer manipulation, etc. Learning more about C to play with these concepts isn't a terrible idea, although it's not the only way to learn about these things. If nothing else, learning C and trying to implement your own parsers or data structures might be a good way to better understand why writing correct code in C that accounts for buffer overflows and string issues is so difficult, and what challenges higher-level languages face in order to overcome these flaws.