|
|
|
|
|
|
by n00kie
5368 days ago
|
|
|
Depends. If it is your product/startup then be careful: We had a split between founders (business vs technical) about outsourcing vs hiring more people, but I finally gave up. So we outsourced 2 non-trivial components, I interviewed both teams (that was my condition and they were really good!) and of course they shipped. The problem was that we had to throw both outsourced components out and eventually expand our team. Why? 1) Minor tweaks: code was hard/impossible to extend - no long term thinking and why should your outsourced team really care? They follow the specs!
2) Pivot
3) Expensive
4) No know-how
5) Hidden costs -> communication
6) After some time the code quality dropped dramatically If you need something YESTERDAY and have the resources to do that... then why not? Just be mentally ready to throw that code away next month. In retrospect we should have used outsourced teams only for mockups/experimental front-end prototypes and not for the actual product. |
|
|