In Mac vs Windows I'm Mac for $reasons. That said my personal daily driver is desktop (not laptop) Linux. I've used primarily Macs at work for several decades; that said, my work focuses on systems running primarily Linux these days, and occasionally BSD or in the distant past VMS (once in a while some embedded stuff). I run Linux in a VM on my personal laptop so that I can run KDE desktop apps in the native Mac windowing environment (X forwarding).
Working for a threat mitigation company, I built KDE actual with Brew on my company-issued Macbook. Admittedly that was masochism. We didn't use Brew for anything; we didn't do any development at all on our laptops. Fast forward. I transferred to the threat intel team; we did some work in VMs on our laptops, still no Brew. We got bought.
New overlords wanted to swap spit / infect themselves with that threaty DNA so loaned me to their prod team. They did all their development in Brew, and deployed to cloudy Linux. They said "use Brew, be like us" and I said no way I am doing that, because my laptop touches bad shit; everything needs to be isolated; loan me a different laptop. But no can do. So I used the devops runbook (and submitted edits!) to build the deployment environment in VMs on my laptop. Prod didn't take kindly to this and threw me back. Left shortly thereafter for $reasons.
But not before I made a runbook for the threat team. Some months later heard through the grapevine that the threat team had been tasked with red teaming the actual deployed system which prod was responsible for and that the pwnage was epic.
The moral is obvious: your security team shouldn't be the only team eating dog food.
Working for a threat mitigation company, I built KDE actual with Brew on my company-issued Macbook. Admittedly that was masochism. We didn't use Brew for anything; we didn't do any development at all on our laptops. Fast forward. I transferred to the threat intel team; we did some work in VMs on our laptops, still no Brew. We got bought.
New overlords wanted to swap spit / infect themselves with that threaty DNA so loaned me to their prod team. They did all their development in Brew, and deployed to cloudy Linux. They said "use Brew, be like us" and I said no way I am doing that, because my laptop touches bad shit; everything needs to be isolated; loan me a different laptop. But no can do. So I used the devops runbook (and submitted edits!) to build the deployment environment in VMs on my laptop. Prod didn't take kindly to this and threw me back. Left shortly thereafter for $reasons.
But not before I made a runbook for the threat team. Some months later heard through the grapevine that the threat team had been tasked with red teaming the actual deployed system which prod was responsible for and that the pwnage was epic.
The moral is obvious: your security team shouldn't be the only team eating dog food.