3 ms·
Best practice is to write, test, build etc. locally using a version control system and deploy a tested bundle to the remote computer when ready. Editing code d
by globular-toast 5y ago
Best practice is to write, test, build etc. locally using a version control system and deploy a tested bundle to the remote computer when ready.
Editing code directly on a remote server is something I used to do in the 90s before git and other tools made good practices much easier.
- ArcMex 5y agoOh, I love your response. Thank you. My workflow was as follows - Remote into server and develop from there - Git to different location, could even be same server - Occasionally pull on local machine for redundant backup This allowed me to - Segregate builds for my testing and the business's UAT - Allowed me to always have a stable build locally that I could look at from home Before, I did develop on my local machine and push to a server. Some part of me still thinks that's the proper way to do it. But I am always seeing what works best for the current situation and developing directly on my server served me well once upon a time.
- datalopers 5y agoBest practice changes rapidly, local dev environments have proven to be an endless pain in the ass. Apple M1 silicon is the final nail. The next 10 years of “best practices” will return to dumb clients and dynamically provisioned dev environments. It’s simply so much easier.
- TameAntelope 5y agoAs someone who has responsibility over how shitty the local development experience is for my org, I recently saw GitHub Workspaces and am curious if that could be a viable option.
- bluehatbrit 5y agoI've been using GH Codespaces for a side project when on the go for a while now. When I'm travelling or recently when moving house I've been able to use my terrible but light weight laptop with vscode + gh codespaces. It's been a complete dream! When running the same project locally on the laptop it's slow and makes development a real pain but codespaces has given the laptop a new lease of life. I'm not sure if the price lines up well enough for a daily-drive for a company, but if I were managing dev environments for an org these days I'd probably jump to something similar. Perhaps something like a decent size EC2 on AWS where devs can tear it down and spin it up again to start from scratch within a couple minutes. Throw away dev environments feels like a game changer having used it for the past 6 months on-the-go.
- globular-toast 5y agoIt sounds like the exact same thing but with added latency. I hate latency. It baffles me why anyone would choose an incompatible architecture only to run dumb clients on it. You might as well just save your money and run the dumb clients on 20 year old hardware. Or you could spend less money on a laptop that is actually compatible with whatever platform you are deploying to and enjoy low-latency local development.
- datalopers 5y agoI’d try VSCode with Remote SSH. Maybe it’s because I’m 10ms from my datacenter but I experience no lag and things have always felt just as speedy while on random public wifi.