"Remote development is fundamentally changing how software is written. It is only a matter of time before local development becomes a thing of the past."
> It is only a matter of time before local development becomes a thing of the past.
Hahaha. Good luck with that!
Remote development was a reasonable, real thing 30-40 years ago, when faster remote computers still made up for the large network latency in between.
Today, when development machines are mostly as fast as any other computer on a workload that usually matters for development (single threaded workloads), we are already getting frustrated with the "devops unification" speed of docker-based development setups, and now introduce network latency and fragility into the picture, and you'll get hordes of developers signing up for it.
To be honest, there will be hordes of them, but there will also be hordes of those running away from this. If you are one of those who gets demotivated with 15s develop-test cycles, it's clear what camp you'll be in.
Sadly, consultants (like the OP author) will try to pitch this to C-level executives who don't understand the focus of a developer "in the zone", and we might end up with this being a requirement for some gigs.
2 comments
[ 15.7 ms ] story [ 606 ms ] threadhttps://www.withcoherence.com/post/its-time-to-forget-what-y...
Hahaha. Good luck with that!
Remote development was a reasonable, real thing 30-40 years ago, when faster remote computers still made up for the large network latency in between.
Today, when development machines are mostly as fast as any other computer on a workload that usually matters for development (single threaded workloads), we are already getting frustrated with the "devops unification" speed of docker-based development setups, and now introduce network latency and fragility into the picture, and you'll get hordes of developers signing up for it.
To be honest, there will be hordes of them, but there will also be hordes of those running away from this. If you are one of those who gets demotivated with 15s develop-test cycles, it's clear what camp you'll be in.
Sadly, consultants (like the OP author) will try to pitch this to C-level executives who don't understand the focus of a developer "in the zone", and we might end up with this being a requirement for some gigs.
But majority of them? No waaay!