Interesting. What makes work provided computers better suited for coding?
Me, I don't recall using company hardware for anything even remotely personal in many years. It's stupid because they are loaded with all kinds of spyware.
Me, I don't recall using company hardware for anything even remotely personal in many years. It's stupid because they are loaded with all kinds of spyware.
Some particular quirk of autocompletion could become almost pure muscle memory, and if it's suddenly missing, you notice.
I am skeptical that nix or home manager would solve these problems. So I just have a specific setup at work, that is typically more advanced and automated than my home system. My leet code interviews suffer because of this. Just makes me realize that coding interviews using an environment that does not mimic the workplace is just excluding senior developers (read: old people) who don’t have the time or patience to jump through these hoops for 15minutes of placating a recently hired college grad
However, it seems that it does not cover all of my needs: https://github.com/twpayne/chezmoi/discussions/1510#discussi...
Maybe I should use Ansible for system-wide configuration and chezmoi for dotfiles in $HOME.
When you get a personal computer you do not need to set up all the things you need to do your work immediately, so you will do the setup of things as you need them.
thus if you get a new personal computer it might not be fully setup yet.
If you are of the age that you have kids you may not have time to do any sorts of personal projects, if so and you have an old personal computer it may not be up to date with what is needed for the coding project because you have not been doing a lot of stuff.
If you have kids or other problems your personal computer may end up broken or unusable and you might not have the money at the moment or the reason to buy a new one.
They already have working software development environments. It's a process that can be time-consuming and is done once in a blue moon (basically when you need to reimage the machine). In the meantime, all changes to your software dev environment are gradual, and your work-provided computer ends up being configured like a software development pet instead of cattle.
Moreso if your company adopted/enforces internal development tools.
Ask yourself this: how many times have you went through a complete OS reinstall and subsequently had to setup a working software dev environment? Is this something you have automated? Most people do not.
I expect there is a similar, but worse, problem growing with CoPilot and friends.
I guess this is because in college and my first few dev jobs used Macs. A nice side effect is my wife hasn’t had any tech support complaints since we switched, it has been great.
I’d still never use company hardware for personal stuff. I don’t even login to Spotify on the company laptop.
She doesn’t seem to have issues with macOS at all though, aside from the one time I had her using a VPN and it expired which is totally on me and disabling it was nonobvious.
Some people only know how to code within the environment managed by their corporation. This is increasingly the case with folks that have only worked at Kubernetes shops.