[ThunderSizzle]

Which is probably a backwards anti-pattern companies have built.

Your most expensive engineer's time is most valuable, so if you give them standard issue which is half the speed, you are throttling the value you can get from your engineer. Not to mention the mental drain of your cursor barely being able to move due to all the bloated virtual networking systemization.

It would seem to make sense to give more valuable employees faster equipment, so that their time isn't spent toiling with the slow machine, but rather actually producing value.

[eru]

Eh, computers are so (comparatively) cheap, that you can give all your employees top-of-the-line equipment by that logic.

(Well, for this to make sense, you need good computers to be cheap, but the returns to diminish quickly after that. Which used to be the case until fairly recently: single core performance was pretty much capped, and after your whole compile is parallelised adding more cores to a machine didn't really help your best engineer either. Similarly for RAM.)

[ThunderSizzle]

Meh - our dev machines are over-provisioned cloud pc's from MS, that run as fast a laptop from 2005. And I'm sure they are paying a premium for the privledge.

My 10 year old desktop sitting next to me is a lot faster, but alas, I can't BYOD.