3 ms·
Don’t forget: Hiring remote contractors to “speed up” things. Dev will slow to 50% and meetings will double as you attempt unsuccessfully to teach them how
by liquidpele 3y ago
Don’t forget: Hiring remote contractors to “speed up” things. Dev will slow to 50% and meetings will double as you attempt unsuccessfully to teach them how to code.
- WanderPanda 3y agoMore general hazard: Treating engineers as fungible resources
- ricardobayes 3y agoAbsolutely. If you have a software company, literally 100% of your company valuation goes home after 6PM. If a key engineer leaves, you lose a _lot_ more than 2-300k. In opportunity cost, you lose tens of millions, possibly.
- gochi 3y agoAnytime a leader sees new hires or contractors as a "speed boost" is when it all goes to the dump. The sooner we get past this idea, and start viewing new hires/contractors as "speed bumps" the better. Bringing anyone new into the fold should always be a slow process!
- tstrimple 3y agoDepends on the scope of the change and the objectives of the company. This is more true in larger organizations than startups, but not all technical problems you’re working on are directly linked to your value prop. I’ve seen good results in many cases where some systems are handed off to be managed by contractors so the FTE devs can focus their attention on improving the product which actually makes them money. What I haven’t seen work is (which is what I think you’re describing more specifically) bringing on new hires or contractors to a project in flight in an attempt to deliver it more quickly. That’s where we get into Mythical Man Month territory.