I strongly disagree with this. You can read all the books you want, but when it comes to making a decision about a set of tradeoffs, there is no substitute for the experience of having made a similar decision in production before and having seen what works well and what doesn't. So many of the nuances of real-world production systems get lost in books and articles that it's hard to know when it's appropriate to apply that knowledge.
That said, I concede that "experience" doesn't necessarily have to be your own—you can learn from the experiences of your co-workers, friends at other companies, or random people on HN, you just have to take everything with a grain of salt.
> Hacking sucks. Just hacking at stuff for years on end leads to you being an expert beginner.
Solo tinkering is a poor substitute for the experience of building production systems with a team, but it's a great way to stretch the breadth of your experience. I have learned lots of different programming languages, platforms, and concepts in this way that have all made me a better programmer all around, even if nothing tangible came out of any of it.
What I feel matters more than books, experience, and everything else, is simply being plugged in to an environment where you can socialize with the folks who've received the most outstanding training, and by osmosis, having the neural network between your ears attuned to their biases and areas of focus.
Higher education does a good job at this. So does working for a big company.
Glad to see I’m not the only one who winces at this. As bad as intellectual snobbery is, reverse/anti-intellectual snobbery is worse: “we don’t take to all yer fancy book learnin’ in these here parts!” It often seems to be lost that the difference isn’t between somebody with a four-year-degree and somebody with 10 years of experience, but between somebody with a four-year-degree AND ten years of experience and somebody with ten (or even fourteen) years of experience and no degree at all. With machine learning finally coming into its own, software development is getting to be more mathematical, and what you learn in college actually is pretty useful.
It sounds like you went to college and I think that's great, I hope you learned a lot and got a lot of value out of it, but try not to disparage the people who decided not to stick around and are working in the same jobs as you because they were smart/pragmatic enough to see the college experience for what it was.
Personally I thought college was a huge waste of time and money. We live in the day and age of the internet and yet we're paying tens of thousands of dollars to learn things that we can teach ourselves for free and the only reason we do it is because we're too afraid not to. Doesn't that sound ludicrous to you? It did to me, and that's why I saved hundreds of thousands of dollars on my student loans by switching to drop out. And before you hit me with the "It was all about the experience" argument, I'd agree, you paid for a very expensive life experience.
I'm now happily employed as a lead software developer making great money. If I need to brush up on my data structures and algorithms for an interview you know what I do? I go online. If I ever want to delve into machine learning you know what I'd do? I'd go online. Need to brush up on some math? You guessed it.
Strictly speaking I think you made a bad investment by going to college, does that make me an "anti-intellectual snob"? And as a follow up, does it make you "wince" when you see how much you paid to learn what I learned for free?
Also, this is exactly what I'm talking about. Huge chip on your shoulder about something that has nothing to do with you. You are so mad about someone else thinking their college experience was worth it.
Don't disparage people who felt like their education was worth it.
You have no idea about other people's life experiences and how they came to the conclusions they have come to.
So maybe accept that some people got a lot out of college and your experience is not universal.
Second I don’t know where you’re getting tuition plus room and board for 30K unless you had some sort of scholarship (which, not to drag race into it, seems to be increasingly difficult to get if you’re a white male).
Third I made it a point not to disparage you, I specifically said that I think it’s great if you feel like you got a lot of value out of your college experience. I don’t think anybody should disparage anybody, that’s the point. I’m not “anti-intellectual” because I made the financial decision to opt out of college.
Theory matters, classic example here[1], and if pointing out that people are making well understood mistakes because they haven't studied it is disparaging, so be it.
[1]: https://github.com/promises-aplus/promises-spec/issues/94
I don't think college is bad, I think debt is bad and for the vast majority of people entering software development the key is to get things done in a timely and efficient manor, I think it's pretty safe to say you'll never get the opportunity to apply category theory during your daily standup meetings with your scrum team as your managers are trying to meet deadlines for their clients, it's the unfortunate world we live in, if everything was free and nobody had to work hell stay in college your whole life. I wish I had that luxury.
Theory tends to bite when something breaks, though.
Performance problems are often explained through computational complexity, or concurrency theory. Strange values can be due to numerical error. If you see something weird in Javascript transformed by Babel, or really any compiler, you might be dealing with graph theory. If there are problems in a databsae, you're dealing with relational theory.
And yes, you can often Google the problem, but you're definitely doing better if you're the person whose answer everyone is searching for.
> That's certainly impressive, though 99% of developers aren't in the business of making high level language design decisions like that.
I think they do, though, because they get an incomplete spec and have to fill in the blanks.
"Agile languages" can be characterized as having concrete types: strings, ints, floats, lists, maps, sets. And the 99% of developers are using these languages and creating data structures using those types, and sharing those data structures, often via JSON.
This results in what I call "data pasta" being shipped back and forth between systems. And those ad hoc structures are effectively codified when they become APIs or are saved in NoSQL systems.
Does a CS degree help with this? I'm mostly aware of the problem because I've done it and then tried to clean it up in systems I work on. So the theory helps, but you need some practical guidance.
What the dichotomy of CS degree or self-taught misses is that the CS degree is aimed at learning the math, and while the math can guide best practices, you don't actually study best practices.
> I don't think college is bad, I think debt is bad
Yeah, I graudated in '03, so debt hadn't blown up. Even if we stop shoveling money into universities, not working for four years is still a massive opportunity cost, and a partially completed degree is worthless, exposing students to a tremendous risk.
And so it makes a lot of sense for people to do bootcamps to get their start in the industry, and regardless of whether you're self-taught or not, it seems like you could benefit from some formal training before you take on a senior role.
My degree had some courses on software engineering, but they were focused on requirements documents and UML diagrams and other high level stuff, which I wasn't going to see for year to come.
So maybe a software engineering course for people with industry experience could go over best practices and justify them through the math.
I find it very unlikely I would have learned the things I know had it not been for university.
Besides, I don't live in the US (thank god) so I was actually paid by the state to study.
Oh no my social media comment was read as "smarmy" by some internet drone. Yawn
I went to a bottom-ranked state school and loved it.
Money well spent.
I actually considered taking my newfound web development knowledge (this was in the mid-late 2000s coming out of the Web 2.0 craze) and starting my own website business, but the advisor at the community college recommended I go ahead and get the four-year degree, which I absolutely realize was a good decision.
I'd go as far as to say it's a bad sign if you can draw direct linkages between what you learned in university and what you do day-to-day in your job. That's not really the intent of a degree in comp sci.
Aside from single-row pulls (and even still), should someone that doesn't understand basic big-O be allowed to write any code that accesses a database?
You're right: Nobody cares you don't have a degree. It's not impressive, it is just normal. What I have a problem with is the huge chip on people's shoulders about "not having a degree" and insisting on dissing anyone who chose to go a different route.
I have a CS degree, I went to school on a scholarship, did not have these massive loans and "wasted years" everyone keeps harping on about. I volunteered my time, I was on the programming team, I did internships, I got amazing insights and advice from my professors. I went to school at night and worked during the day.
I consider my CS degree the best decision I ever made. I found the training and education I received extremely valuable. However, not all degrees are created equal. I went to a really great school. Probably would have had a different experience if I went to whatever crappy state school was nearby.
I also don't think it is necessary to have a degree to be a great programmer. What I DO think is necessary is study and honing your craft. Experience for software development is worth much less than people give it credit for.
Hacking sucks. Just hacking at stuff for years on end leads to you being an expert beginner. Do you have 10 years of experience? Or have you done the same thing for 10 years. This applies to everything: You can get twice as far in half the time if you don't have to figure everything out for yourself, and listen to and learn from experts.
What I look for in a developer: READS BOOKS. ( Audio books count )
That's the only thing. I'm sorry, if you are not reading and studying to keep up, you are getting left behind. There are so many brilliant people writing amazing books on a huge array of subjects. If I could get every one of my developers to read ONE book in on software design[0] a year, I would die happy and the entire industry would be 10 years ahead.
They don't even have to be technical books. I just want to see intellectual curiosity and a commitment to self improvement.
- 0: In the vein of Clean Architecture, The Pragmatic Programmer, The Mythical Man Month, Designing Data-Intensive Applications, The Google SRE book, etc.