Hacker News Reader

Comment by up_and_up | Hacker News Reader

> And for mentorship, don't hire people that need extensive mentoring.

So then forget interns and/or jr's devs?

I have found code reviews via pull requests to be a good mentoring tool.

I've been thinking about this issue lately. Jr developers, interns, fresh grads, etc all have some alluring properties: they are cheap(er), have few(er) bad habits, and are more open to being coached into their roles.

Netflix, on the other hand, hires no folks like this.

http://www.businessinsider.com/interns-banned-at-netflix-quo...

My current company is comprised almost exclusively of newer engineers. It has put me in a strange position as someone with > 10 years experience in my field when that long ago, most were in high school.

EDIT: fixed split infinitive and spelling

I think the reality is that only large-ish companies have the slack time necessary to devote to mentoring. Companies have to get to a certain size first.

At a startup, you are running full tilt 24/7 by necessity.

Startups are not (usually) engineering firms with super high quality requirements. My first job (still in college) was at a startup. I was the only developer under the CIO. It was a java webapp and both of us barely knew Java when we started. It worked pretty well, we had minimal serious quality issues compared to most companies I've worked at, we had zero unit tests and a shoe-string budget. That company is still going strong and has made millions off the project I started practically on my own over 10 years ago.

It can be argued that startups require a broad range of skills in a wide array of technologies, and you don't get that with inexperienced people.

In a mid-sized organization you can work on a java webapp - as in your example - and possibly only on a part of that java webapp. In early stages of a startup, you're likely to have to know your way around the webapp's frontend, backend, mobile app/mobile web adaptation, handle SEO, plan for scaling, be a part DBA, handle server administration DevOps style, and do all kinds of internal business process automation unrelated to that product you're building. You'd need to be a jack of all trades at beginning - since there's noone around who's specializing in that other stuff - or spend half of your time becoming a jack of all trades.

I installed the servers in the rack at the data center, configured the load balancers, installed and configured the database with a hot backup and wrote 90%+ of the application code when we went live. You don't need people with all that much experience.

Well, mentorship was mentioned as being hard to do remotely. So, don't hire remote interns or remote junior devs. That seems like reasonably good sense to me.

But of course "remote" is a reciprocal relationship. If the senior dev is remote and the junior dev is local, it doesn't matter, the senior dev still can't mentor the junior.

Reply on news.ycombinator.com