alt Hacker NewsThis seems like a complete opposite of what you'd expect. Why hire a team of mediocre overseas workers to prompt Claude (your characterization), then have to talk to them only at weird times of day, and have a 12 hour turnaround on anything? Instead you could have one or two local devs from your social circle, swing by their desk at 9am and they have the feature that Claude built merged by lunch?
Replies
Because in any decent sized organisation, the speed at which code is written has never been the bottleneck (even if management thinks that it is.)
Internal turf wars, endless meetings to get “alignment” and pivoting on management’s latest whims are what slows feature delivery.
>Instead you could have one or two local devs from your social circle, swing by their desk at 9am and they have the feature that Claude built merged by lunch?
Because the amount of skill it takes to do that is not commensurate with a salary high enough to afford living in SF.
> swing by their desk at 9am and they have the feature that Claude built merged by lunch?
At the scale where hiring overseas workers make sense, there are atleast one PM, QA people, Ops - likely teams, not just one person per, involved. No one is releasing a feature to prod by lunch.
The workflow you propose is a very good representation of SMBs and they are behaving as you have proposed - hire one or two local devs from Austin, call them over Slack and release to prod by lunch.
So yes, this is happening, just wanted to point out that the "overseas workers" workflow is at a different scale of operations.