3 ms·

Switched our team off Microsoft platforms entirely. All developers are on macOS now, targeting JVM on Linux. Refreshing to be able to participate in a real ec

Switched our team off Microsoft platforms entirely. All developers are on macOS now, targeting JVM on Linux. Refreshing to be able to participate in a real ecosystem, instead of having to write the .NET version/binding for every damn useful piece of OSS out there. Plus, working for an 80,000 employee company, IT can't screw up macOS as much as they did their Windows image, which does wonders for productivity. The last straw was a McAfee update on Windows which causes every executable launched to take 45 seconds the first time it launches. Last time I checked, IT still hadn't figured out how to fix it for real, after months, and resorted to exclusions to "fix" it. Think how many times a developer builds an executable and needs to launch it....yeah. I know, I need to quit, but they pay very, very well and it's a pretty low stress job that's really helping me hammer my mortgage. With proper tooling like I have now, it's a pretty good position that leaves a lot in the tank for learning and experimentation.

staofbur 9y ago
This is normal corporate IT on windows. The biggest battle I have is with operations teams who require that you don't have administrative privileges on windows dev machines. This cripples development teams instantly because you just can't do that. I tried to push the organisation I work with currently in that direction but they haven't quite got over the Stockholm syndrome of being a Microsoft certified partner yet or admit that a lot of infrastructure and platform investments were bad ones now. I'd take low stress and good pay over most things ;)
- hvidgaard 9y ago
  > The biggest battle I have is with operations teams who require that you don't have administrative privileges on windows dev machines. Fortunately I do not have this battle. But if I did, I would simply tell operations boss that unless my developers get admin access in their dev environment, they have to have staff dedicated to my team, ready 24/7/365 to serve them. Weekends, holidays, christmas - all the time, no exceptions.
p2t2p 9y ago
> IT can't screw up macOS as much as they did their Windows image Oh trust me they can. How about to hang while showing login screen because AD server doesn't respond? MacOS auto reboots in such occasion. How about screw your keychain with their scripts completely when you change you password? I need to re-login into iCloud every single time I change my password because of that. How about hang before even getting to login screen because AD doesn't respond? Broken file permissions and groups because of AD thing? Unexpected CPU spike to 100% because some IT thing does something in background? Constant notifications even OVER LOGIN SCREEN about "Your sleep time is too long" and so on. I'm now just afraid to install updates because it'll involve reboot and next reboot IT scripts will screw up something else and I'll need to spend half a day fixing it.

staofbur 9y ago

This is normal corporate IT on windows. The biggest battle I have is with operations teams who require that you don't have administrative privileges on windows dev machines. This cripples development teams instantly because you just can't do that. I tried to push the organisation I work with currently in that direction but they haven't quite got over the Stockholm syndrome of being a Microsoft certified partner yet or admit that a lot of infrastructure and platform investments were bad ones now. I'd take low stress and good pay over most things ;)

hvidgaard 9y ago
> The biggest battle I have is with operations teams who require that you don't have administrative privileges on windows dev machines. Fortunately I do not have this battle. But if I did, I would simply tell operations boss that unless my developers get admin access in their dev environment, they have to have staff dedicated to my team, ready 24/7/365 to serve them. Weekends, holidays, christmas - all the time, no exceptions.

p2t2p 9y ago

> IT can't screw up macOS as much as they did their Windows image Oh trust me they can. How about to hang while showing login screen because AD server doesn't respond? MacOS auto reboots in such occasion. How about screw your keychain with their scripts completely when you change you password? I need to re-login into iCloud every single time I change my password because of that. How about hang before even getting to login screen because AD doesn't respond? Broken file permissions and groups because of AD thing? Unexpected CPU spike to 100% because some IT thing does something in background? Constant notifications even OVER LOGIN SCREEN about "Your sleep time is too long" and so on. I'm now just afraid to install updates because it'll involve reboot and next reboot IT scripts will screw up something else and I'll need to spend half a day fixing it.