![]() Any drop off of interest from the already slim subset of people who care about our IT product hits our respect as peers in an engineering organization, and the dynamicity of our team can only be assisted by showing better representation of the customer population as a whole. When we do that, our service delivery will get feedback from the widest customer base possible because our members will be that much more approachable. ![]() I want us all to realize we should grow people that aren’t like the archetypes we can be perceived as having benefitted from in our careers. At most interviews I can still fake a ‘culture fit’ for pampered people havens because I’m male-identifying and cis and have worked in places with unconscionable practices, with really bad personalities that provided cover for my own toxicity. Some employers train interviewers on bias and explicitly call out ensuring qualified candidates get the consideration they deserve. If it’s a given this will not be your last job, I have no problem eventually losing teammmates to other departments and fields that use osquery or devtools scripting or containerized GitLab CI/CD or web-facing cloud service delivery, as long as we get the mutual benefit of our time together in enough of the core CPE disciplines.Īt (several, failed) Dropbox interviews I detected I wasn’t respected because I hadn’t gone to university, same due to my lack of ‘real’ Computer Science bonafides when I interviewed at Google (although they were still super nice about it). I, for one, don’t need people who religiously follow the blogs or Apple’s mercurial shifts, but I do want folks who know how important gitops and code review and visualization of metrics are and yeah, also happen to be able to deliver operating system/workstation platform lifecycle management. Apple’s continuous churn, breaking and giving us QA tasks for the disruption they cause ~being courageous~ ‘innovating’ means we also have to continuously learn and stay on top of change, more than almost any other tech discipline (besides I guess JavaScript frameworks). Tech workers are kept afloat in seemingly all economic conditions and are finally getting salaries to show proper respect for the breadth of skill we display across various parts of the IT ‘stack’. But as a devops mindset and its topics crept in to how MacAdmins can get their job done, we (should be able to have) increased who can do this job. My personality means I’ve followed Mac blogs since it was hard to blog, I’m a lifer for this work. But one of my favorite quotes from a manager I’ve heard in passing was ‘this isn’t going to be your last job, so I’m hoping we can help you improve in the way you want to evolve’. Speaking for myself, I’ve enjoyed making this my career. Opportunities abound! (And we can get compensated accordingly – it’s valuable work.) ![]() Now there’s enough of a gap in tooling from the MDM perspective that vendors are recognizing you don’t get better without people from the trenches with problem space expertise. Around the same time securing Corp meant pulling the people who know how to patch and inspect configs on the fleet (we even have the highest count of CPUs) into Security-dedicated roles. Then being fluent in Continuous Integration/Continuous Development supporting the building of iOS apps became prolific. Starting at the beginning, why am I intending to encourage the talent pool of CPE’s to increase, and saying it’s both a great time to be one and ok if you don’t want to do this work (forever)? Years ago the MacAdmin community would lose talent to Linux sysadminery/devops-y folk. ![]() In the day-to-day it would be less helping end users in real time, have less interactions with locked-down ‘appliance’-style mobile devices, but it’s definitely about making sure computers get patches, secure configurations, and groups can be identified that an appropriate environment is maintained on applicable devices. To grow/find those people, I have used the same interview questions which can be reverse-engineered into a bunch of advice for those still feeling like they have skills to acquire before being able to call themselves a CPEĪs a definition of what *Client Platform Engineering* is, we’d be the team that ‘manages the life cycle’ of workstation platforms. If current CPE’s aren’t doing explicit outreach to under-represented-in-tech groups and investing in the growth of the motivated people out there, our standing in our organizations (and the future of our speciality) is the lesser for itģ. With 50k people in the MacAdmins Slack, it’s fine if you don’t want to be a Client Platform Engineer, but ~be a lot cooler if you did~ it’s a better time than ever to become oneĢ. I’m going to ping pong between a few topics here, so to give everyone guideposts, here are the three main topics I’d like to stay with you, dear reader:ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |