Live data from Hacker News

What I learned from spending 3 months applying to jobs after a coding bootcamp

medium.freecodecamp.com

361–370 of 398 posts

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#361
post #95

Earlier quoted context omitted.

London COL is very similar to SF/NY I believe.

Thanks to trains you can commute into London fairly easily from somewhere more affordable. And it isn't driving so you can work or read as well.

Not really, anywhere that's convenient to London has basically the same prices as London. If you do end up saving money it's because you're taking one of those awkward 90minute+ journeys.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#362

Earlier quoted context omitted.

In a tiny town in the middle of nowhere middle america, where the cost of living is 90% the national average, we can't keep college grads starting at $75k with an assured 10% bonus. This is a town where all marble 4,000 square foot McMansions start at $240k. bestplaces.net puts this as a comparable salary to around $280K in San Fran.

Maybe, but $280K in SF pays off the student loans a hell of a lot faster than $83K in the middle of nowhere.

Yep. Fixed costs.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#363
post #285

Holy shit. Is this some kind of a joke? > Otherwise, companies automatically categorize us into junior developer roles or tag us as “not enough experience.” ??? What do you think you are after a TWELVE WEEK coding seminar (no matter how intense it was)? It looks frightening to me that he doesn't even know what "junior developer" really means. How ignorant can someone be to NOT think to be a junior dev right after "gr…

Hey, there. I also went to Hack Reactor. It's not a joke.My first job out of the program was Groupon and the algorithm-heavy style of the interview wasn't a problem. The hardest thing for me while there was CSS (because they supported some old versions of IE).

I'm not saying that I was stronger on the data structures and algorithm side than top students who spent four years staying up coding during their nights and weekends but I was definitely ahead of most fresh grads I encountered. I don't know how that is, given what a typical CS curriculum (at least what I saw later on Open Courseware) but my guess is that a lot of CS grads don't actually practice what they're learning enough so that it sticks.

One thing it appears a lot of people on this thread are missing is that it's not a school for complete beginners. There are prep courses for people looking to enter the school. I had been programming simple things for my blog for years before I went. About 1/3 of my class already had CS degrees before entering.

The other factor is that intensity really does matter. The reason focusing on duration of 12 (well actually 13 weeks) is wrong isn't because nearly 1000 hours of instruction and work are packed into those 12 weeks. It's even more wrong because working at double the intensity leads to more than double the progress. I saw the same phenomenon with language learners when I was living in Taiwan. It's very common for someone who did a full four year degree in Chinese to speak poorly compared to someone else who did a much shorter, more intensive study at a top immersion program like ICLP.

Anyway, the degree of animosity here is a little surprising, even considering the cognitive biases that might come from having spent a fortune on a university credential. Large numbers of my peers from Hack Reactor went on to do well at YC companies and/or large companies like Google. One I remember well did both (was an early engineering hire at a YC company that got acquired by Google). I still consider the tuition I paid to HR one of the better investments I've ever made (and one that I easily recouped within the year.

Thank you Marcus and thank you, Shawn. You guys were fantastic instructors and project mentors!

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#364
post #209

Earlier quoted context omitted.

To be fair, for 99% of web development being able to select elements based on their CSS class is seriously way more useful than being able to explain and apply "engineering crap". Pretty much until you get to the point where you need to scale infrastructure you won't use any of your CS degree when working on most web applications.

Also to be fair, learning how to select elements by CSS class is so trivial that it doesn't effectively separate levels of developers. Whether you choose the basic JavaScript version or one from a popular framework, it should take less than a minute to look up if you don't already know it. I imagine that seasoned developers (and possibly recent CS grads, depending on school) are much, much less likely to waste time w…

CSS is not only selecting elements (like JS is not only "defining functions"). Creating complex CSS layout can be hard the same way complex JavaScript system is.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#365
post #285

Holy shit. Is this some kind of a joke? > Otherwise, companies automatically categorize us into junior developer roles or tag us as “not enough experience.” ??? What do you think you are after a TWELVE WEEK coding seminar (no matter how intense it was)? It looks frightening to me that he doesn't even know what "junior developer" really means. How ignorant can someone be to NOT think to be a junior dev right after "gr…

They gave him shitty work that nobody wanted to do, and you are surprised that guy had no motivation for do it?

> work that wasn't too complicated

"complicated" is subjective. There are many talents and somebody could be better in for example JavaScript (and not HTML/CSS).

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#366

Earlier quoted context omitted.

I mean, call it what you will, but a lot of these people are getting offers, man. Good ones. Which is more than I can say for myself with my comp sci degree and two years experience. Although my location is likely to blame for that.

More than I can say for my BS CS plus 17 years. As I have had 7 different jobs for 12 different employers (due to mergers/acquisitions, by the most generous count), and have needed to run the entire interview gauntlet all 7 times, my primary career goal is no longer to earn more money. It is to never have to do another effing software-industry interview, ever again. But damn. For $120k/year, in the region where I now…

>"my primary career goal is no longer to earn more money. It is to never have to do another effing software-industry interview, ever again.:

I feel exactly the same way, even though the existence of those interviews is probably the main reason I was able to get into kinds of companies I did.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#367

Earlier quoted context omitted.

In a tiny town in the middle of nowhere middle america, where the cost of living is 90% the national average, we can't keep college grads starting at $75k with an assured 10% bonus. This is a town where all marble 4,000 square foot McMansions start at $240k. bestplaces.net puts this as a comparable salary to around $280K in San Fran.

Maybe, but $280K in SF pays off the student loans a hell of a lot faster than $83K in the middle of nowhere.

$83K in the middle of nowhere is for entry level positions. $280K in San Fran are rock stars well into the 99% of salaries. You're comparing a starting first year fresh out of school who can easily afford a McMansion on a large acreage with a seasoned developer who's in the top 1% of their colleagues who can now just afford a nice condo.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#368
post #6

Are people in America seriously getting offers of $120k with no degree, no experience, and not even a side-project? That is mind-blowing. In London, probably the biggest/richest market outside of USA, that sort of salary is beyond what most experienced developers get, even some very good ones. I must be missing something here (some sort of bubble?) because I can't see how businesses can be profitable paying those sor…

I'm in London too, $120K job in today's London market (£100K) only exists in some banks, hedge fund and HFT companies, and you'll definitely need 10year+ experience to get those jobs.

I think the salary gap between US and UK programmers in the last decade has definitely increased.

One reason is exchange rate, only a few years ago GBP/USD is 1.5x, now it's 1.2x.

Another reason is that tech sector boomed in the US, big companies like google and Facebook are doing really well, there are also more successful small companies, fuelled by VC money. together they drive programmer salary up.

However, the UK economy is totally dominated by finance. And the banks are not doing particularly good after 2007.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#369
post #285

Holy shit. Is this some kind of a joke? > Otherwise, companies automatically categorize us into junior developer roles or tag us as “not enough experience.” ??? What do you think you are after a TWELVE WEEK coding seminar (no matter how intense it was)? It looks frightening to me that he doesn't even know what "junior developer" really means. How ignorant can someone be to NOT think to be a junior dev right after "gr…

One of the odd things about our industry is that we don't distinguish between technicians (who build and maintain things) and engineers (who analyze and design things). We tend to call everyone engineers, and muddy the distinction between building and analysis.

If we did make the distinction, the place of these bootcamps would be much clearer. They train technicians. Specifically software technicians. Their graduates can build things and fix problems using current technology, but they don't have the deep theory and sophisticated understanding of the field that lets them solve really hard problems (at least until they considerably augment their skills.)

The job that most closely fits those is usually called Software Engineer, as distinguished from Senior Software Engineer or Staff Software Engineer. Did the writer really land a job at the Senior level on the strength of ten weeks of instruction and three months of personal study? Sounds weird.

The only situation where I'd hire someone like that into such a position is if they brought a LOT more to the table, meaning probably domain experience. If someone spent ten years as a petroleum engineer and I am hiring a software developer to work on software for the oil industry, then yes, I might be willing to hire them at Senior despite a dodgy background in software.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#370
post #285

Holy shit. Is this some kind of a joke? > Otherwise, companies automatically categorize us into junior developer roles or tag us as “not enough experience.” ??? What do you think you are after a TWELVE WEEK coding seminar (no matter how intense it was)? It looks frightening to me that he doesn't even know what "junior developer" really means. How ignorant can someone be to NOT think to be a junior dev right after "gr…

Sometimes its about demonstrated skill. We all know about the FizzBuzz debacle - how most folks we interview can't write a simple loop and test? Well that guy was actually educated and demonstrated skills way up the bell curve.

There is "some kind of joke" going on, but it isn't that guy. Its the rest of the industry that turns out script-mungers and form-fillers and calls them 'software engineers'.

Post reply on HN