4 ms·
"According to Rose, “there is a temptation that you want to throw as many developers as possible at a problem.” As Digg was built on top of PHP, the company wou
by mgkimsal 15y ago
"According to Rose, “there is a temptation that you want to throw as many developers as possible at a problem.” As Digg was built on top of PHP, the company would hire too many developers that specialized in this language. Then, however, Rose noted, “you end up with lots of PHP developers, but at some point, PHP isn’t a problem anymore and you are stuck with all of those developers.” At that point, said Rose, you end up having to hire a lot of developers that can do other things and don’t know what to do with the old developers."
-------------------------------
OK - so don't hire employees, but contract with contractors. Seems a pretty simple problem, yet few companies I talk to want to go down that route.
"We're looking for someone who's in it for the long haul" or "we value loyalty" are some reasons I've heard from companies that won't consider contractors.
In some situations, that's probably fine. In many other cases - fast tech-driven startup-type stuff - contracting probably makes more sense for precisely this reason. The company's needs can change quickly, and having a lot of staff that don't know X but only Y is a competitive problem.
"But smart people can learn X too!" Well, yes, to a point, but probably not as well as the people at your competition may already know it. And who says all those smart people really want to learn X? If you're really switching from Y to X, some Y devs may resent that, because Y can handle the workload too. They may not put all the effort in to learning X, because they see it as a fad, or a dangerous pivot that is doomed to failure, etc.
"Smart people can learn new tech X too!" is condescendingly treating devs as interchangeable parts while damning with some praise ("but they're smart!")
"If your developers are either incapable of pivoting to a new language or flat out refuse to, then they are terrible developers."
You've just done 3 years of Rails development, fighting all those version bugs, pulling all the late nighters, getting every rock solid and scaling out to the moon. Yay! Launched, everything's great, and you're rocking it. Then your board of directors signs a deal with MS for Bing tie-in, and MS invests some money in your company, but you have to pivot to ASP.NET/C#. In 3 months.
Do you refuse? YOU TERRIBLE DEVELOPER!
What's that? You'd rather keep doing Rails, so much so that you'll quit your job and move somewhere else to get a chance to keep working on Rails projects? That describes most of the Rails devs I know, and I wouldn't say they're "terribly developers" at all. Well, a couple aren't great... :)
- petervandijck 15y ago"for fast tech-driven startup-type stuff - contracting probably makes more sense". On the contrary, actually.
- vkatluri 15y agoWould you care to explain or elaborate?
- deleted 15y ago[deleted]
- dextorious 15y agoYou want to keep the expertise on your product IN-THE-COMPANY, not outside. You want to be able to build a company engineering culture, to be able to adapt. You want people which have a stake in the actual outcome of the company. You don't want your programmers only be a contract away from working for your competitor. Also: you don't want all the contracting engineering, communicating and legal overhead.
- slindstr 15y agoI agree with all of your points, but I'm wondering about the case where it's a solo technical founder that has to do EVERYTHING - marketing, development, customer relations, billing, etc. In that case do you think it makes sense to outsource non-core functionality just so he/she can accelerate development in order to get a more complete product out there (beyond MVP)?
- viscanti 15y agoThere's different stages of a company. In the beginning, when flexibility is more important, contractors might make sense. Even then, I think you're better off finding flexible developers to work with long-term, but if a contractor is the best you can do at that stage, it's probably not a deal breaker. MVP+ stage requires a lot of iterative development. Ideally, you'd want to keep the people who are helping with that, because they'd know WHY things are done the way they are. They'll be aware of the failed experiments and previous iterations. You don't want future employees making the same mistakes. The goal of the MVP+ stage is to learn as much as possible about your market and product. Letting that product learning walk out because they were contractors is probably a mistake.