top | item 34734214

(no title)

robertcope | 3 years ago

I 100% think this is the long term play. Once we figure out how to really have "remote only" companies, the "remote" part won't be "remote in the USA" but "remote in some cheap part of the world". We tried this with outsourcing but it failed because we didn't have the "remote" part down... now we do...

discuss

order

rswail|3 years ago

As someone that has dealt with local (Australia) and remote (Slovakia, Mumbai, Phillipines, Thailand) outsourcing, the problem is not the individual workers, or even language, time zones etc.

The problem is more about the company/organization that is doing the outsourcing than the outsourced work itself. You have to have a clear definition of what you are trying to outsource. Is it "just coding"? Is it "some design, but not analysis"? Is it "do everything below a certain level of management" (the worst)?

If you don't know what you want other than "cheap" then you won't get either of the other two qualities of "good" or "quick".

Developers aren't fungible, neither are designers, or analysts or architects. About the only people that are fungible and easily replaceable are project managers (sorry, buzzword compliant "product owners" and "SAFe scaled Agile practitioners").

berkeleyjunk|3 years ago

Yes. Agree. The only thing preventing this going all the way is the friction in timezones and difficulty in co-ordination (i.e. still requires someone local to the remote people to manage their work).

scarface74|3 years ago

Well for my line of work (app dev/cloud consulting) there is lot of face time, video conferencing with clients, travel to client sites, etc.

But also many of our contracts have data governance requirements where you have to be US based and other government contracts require you to be a US citizen.