That doesn't seem so bad to me. I have always preferred personal device whenever possible. Why not cut out the ewaste?
As another commenter said, you're adding wear and tear to your own device. Sure, I have my own computers, but they're all spoken for, hosting VMs and containers or acting as my lab. Why should I subsidize the profits of a multi-million-dollar, for-profit company by letting them use my computer at no extra cost?
Your e-waste point is a good one, but I don't think Canonical's managers were looking out for mother nature when they made that choice.
At least it's not as bad as the gilded age where workers got paid in company-store scrip and lived in company housing in a company-run town. Still, I think it's a step in the wrong direction.
I'm not trying to be dramatic or imply that Canonical's device policy is some act of pure evil, but it was a contributing factor to my decision not to move forward. I have a computer that would serve the purpose just fine. It's more about principles. By itself, that policy wouldn't have been so bad, but combined with other red flags it was enough for me to stay away.
Funny, I actually mentioned Snap-On by name in one of my other replies, probably around the same time you were commenting. They've got good brand recognition, apparently!
I actually agree, I would personally not work somewhere that made me bring my own laptop, I prefer having a solid divide between work and home. But on that note, I also don't like having a work laptop, I prefer to have a desktop, that way I know I'm never taking work home lol
Most knowledge workers cannot deduct their laptop.
My company gives me a stipend for use of my own phone every month.
Sounds horrible to me. Work and personal are always completely separate.
Because it externalizes their costs to employees and creates a bidirectional privacy nightmare (company data is exposed to programs running on a personal machine, and personal data is exposed to company programs - worse if they have any sort of management software but iffy even if not).
The second reason is that I don't want my personal devices subject to security monitoring, and most companies that at least pretend to care about security require some level of endpoint monitoring.
Small companies usually can't be bothered worrying about those risks (and small companies aren't typically worth suing anyway). But a company of any appreciable size needs to worry about the kinds of things mentioned in the comment.
Why won't your personal devices be subject to discovery anyways?
For me, I have a separate laptop for every contract I work on, sometimes more than one for a given contract (for complicated compliance reasons). The reason for this is to a) prevent cross-contamination between projects, and b) because the laptops could get caught up in legal shenanigans. If one contract ends up in dispute, the laptop could end up getting subpoenaed, and if it was my only laptop I would be SOL. Or god forbid, code from two projects gets mixed by accident, and now I'm in violations of multiple NDAs. In one case, the customer paid for my hardware during development, and when we were done they took ownership of the laptops along with the code.
Your work computer is just like your work code: At the end of the day it's not really yours, don't get attached.
Of course, if you can bill the machines through to the clients, why bother!
Good luck switching hard drives on locked down customer provided laptops, or from the own IT on the consulting firm for that matter.
but you can with Linux.
I've never tried it with MacOS but the days of swapping Apple harddrives are in the past anyway.
Now, if you're doing this for concerns regarding discovery, I'd just use separate devices, as my confidence is low the court wouldn't just require the entire host(s) involved anyway.
This is personally why my environment is not tied to a specific host. Should any given device(s) get caught up in discovery I can still build/recover a full fresh environment on a new device relatively unimpeded - and do so regularly to ensure it's not just a theoretical. It can be a hassle, but at least I'm not trying to juggle devices in that way and have flexibility to either BYOB or work with client supplied kit and still bring my env and tools with me.
Not saying this is their reasoning - and if they're not too cheap, it would surely be better for tax purposes to buy your employees computers than pay them the equivalent in cash - but it's a reason at least.
There are many reasons not to work for Canonical, but the opportunity to pick and choose your own hardware rather than suffer what someone else thought your would need seems an odd choice.
Thats just asking for trouble.
So just add the cost of acquiring employer-specific hardware to the compensation package during salary negotiations, is it really a big deal? Don't you generally have your own hardware preferences anyways?
The problem would be if they insist on what software you run on that machine and if they put crap like spyware/backdoors on your device.
If it's just a "we don't care what you run, just be productive and do good work" kind of attitude, BYOD could totally be ideal.
Nothing is more annoying than having an employer shove something like an imac down your throat with a "use this backdoored garbage or quit" mentality.
It is a sign the company will resist spending modest amounts to improve efficiency and morale. Including pay increases likely.
One position required me to take a psychoanalytical test where they judge your personality traits to A.) make sure you have the desired personality traits for the role and B.) that you're smart enough for the role. I looked at the terms of service for the company they outsourced this test to, and it seemed like a data breach waiting to happen. I expressed my concern to the HR team in charge of hiring, and said I wouldn't feel comfortable having that kind of deeply personal info shared. I further expressed surprise that an open-source software company was using this test at all, given the usual penchant for data privacy in the FLOSS community. They (cordially) said I could either take the test or drop out-- I chose the latter.
For the other role, the interview process was going well, and I made it to final round. But, I ran when I saw their tech stack and tech debt. Lots of Jenkins and heavy reliance on Launchpad for almost everything. Launchpad might not technically be proprietary since it's GNU-licensed, but it's as good as proprietary if Canonical is one of the few companies using it commercially. And Jenkins is just Java / Groovy garbage all the way down.
It also struck me as a red flag that Canonical is 100% BYOD (Bring Your Own Device), and they do not provide a work computer. You can apply for a _loan_ to buy a computer for work, but they will not pay for one. If a company is too cheap to provide a computer at a job where you work remotely and exclusively on a computer, I don't want to be a part of that company.
Lastly, I read a lot of negative press about Canonical's CEO Mark Shuttleworth while researching the company. In general, Canonical seems like a sketchy place to work.