Re:The Metaprogrammer
by falcolas on Wednesday September 07, 2016 @10:19AM
(#12443575)
> as you gain experience you realise how unimportant your local terminal is.
If I may be blunt, bullshit. Working on a remote server, especially one not on your local lan, is a lag filled pain in the ass.
Even if you decide to work on a local editor and upload to the cloud, your write-test cycle will be slower, and the best editors will require quite a few CPU cycles themselves to provide (their version of) intellisense, syntax highlighting, and documentation.
And this doesn't even cover ensuring that the computer is capable of handling remote conferencing - a resource drain to end all resource drains on laptops.
I'd go one step further and say that as I gained experience, I realized the value of the productivity gains from low latency and the freedom offered by working locally (I even keep local copies of documentation websites, so I never have to worry about them being down).
> Not that many coders 'often' travel on the job, as a proportion. Most are office-bound.
Internet can still go out in an office. So can power. People travel, work from home, and sometimes work from a conference. Why limit your employees for the sake of saving 1% of a software developer's salary (less, actually, when you consider amortization)?
If I may be blunt, bullshit. Working on a remote server, especially one not on your local lan, is a lag filled pain in the ass.
Even if you decide to work on a local editor and upload to the cloud, your write-test cycle will be slower, and the best editors will require quite a few CPU cycles themselves to provide (their version of) intellisense, syntax highlighting, and documentation.
And this doesn't even cover ensuring that the computer is capable of handling remote conferencing - a resource drain to end all resource drains on laptops.
I'd go one step further and say that as I gained experience, I realized the value of the productivity gains from low latency and the freedom offered by working locally (I even keep local copies of documentation websites, so I never have to worry about them being down).
> Not that many coders 'often' travel on the job, as a proportion. Most are office-bound.
Internet can still go out in an office. So can power. People travel, work from home, and sometimes work from a conference. Why limit your employees for the sake of saving 1% of a software developer's salary (less, actually, when you consider amortization)?