Either we were coworkers, or every company that uses JAMF ends up with that saying. In fact, we made a slack response that would post a gif of Jeremy Jamm from Parks and Recs saying "You just got JAMFed" whenever anyone mentioned JAMF.
> I worked at a company that used the phrase "getting jamf'd" as a verb to describe when the management system broke things on your macbook.
It's just a management framework - Do developers who use windows say "getting sccm'd" or "getting Intuned" when SCCM/Intune does management actions on their devices?
> I got Jamf'd pretty hard this morning and now my build is broken...
If the IT department is pushing stuff out through the management framework on the devices that is "breaking builds" - they are doing device management wrong.
And if the IT department is pushing out Config Profiles which break things people use every day, thats more a people problem than technology/Jamf problem. (as in the IT dept are morons)
I think part of the problem is that many IT departments have a culture which focuses on the needs of less-technical users. They often don't have a good appreciation of the more demanding needs of technical teams. Non-technical users need a lot of handholding – an approach which can be irritating to the technically advanced. A locked-down UI which doesn't let you change any settings may be the right approach for non-technical users, developers can find it infuriating that you won't let them try to solve their problem themselves, and instead force them to talk to a helpdesk who don't understand it either and want to follow some script ("Have you tried rebooting?"), before they let you talk to someone who actually understands what is going on
Maybe software like Jamf isn't inherently a problem, but it can encourage IT departments with that kind of culture to do more things to irritate developers (like automatically run buggy scripts on developer laptops without any notice or easy visibility into what those scripts are and what they do), which without that kind of management software available to them, they would have been less likely to try to do. Developers are more likely to have configured their environment in custom ways which will cause IT's buggy script to play up and cause problems
I used to work for Oracle, and while I was there Oracle had a whole separate IT department just for the engineering/R&D org, while the main IT department serviced the rest of the business (sales/support/finance/legal/HR/etc). I don't know whether Oracle still uses that setup, but (if the company is large enough to sustain it) that could be an approach to avoid some of this
> It's just a management framework - Do developers who use windows say "getting sccm'd" or "getting Intuned" when SCCM/Intune does management actions on their devices?
Ubisoft Massive does have the phrase "got GPO'd" if that helps.
It happened to us with Fleetsmith too, it was great then overnight everything stopped working, which incidentally was because apple acquired them. I like Jamf'd better though, it's going into the lexicon!
E.g., "I'll be able to test that code change in a bit, I got Jamf'd pretty hard this morning and now my build is broken..."