9 ms·
> Therefore, if my linux laptop was to die (like one of my dev's linux laptops did on Monday night) and then I was to miss a day of work, I could afford the dif
by sfhdfhsdsdfh 4y ago
> Therefore, if my linux laptop was to die (like one of my dev's linux laptops did on Monday night) and then I was to miss a day of work, I could afford the difference between a linux craptop and a mac in lost productivity.
As a Linux laptop user with an overbearing asshat of a boss, I fucking love this misconception. Getting my working environment set back up after a fresh install is a git clone and 2 minute Ansible run (the majority of the time is spent on packages downloading).
Fortunately, however, if I want to ditch my boss for the day, I can blame Linux. Don't wanna be on video for that call? Sorry, Linux. Don't wanna attend the call at all? Sorry, Linux must have $(bofh excuse).
I'd have absolutely zero motivation to do this if it weren't for my boss blaming everything on Linux out of the gate, but hey, if that's what he wants to do, I'm gonna lean the fuck into it.
- aunty_helen 4y agoSome people have very basic setups and use everything out of the box and that's fine. I could have an editor with git checked out and publish code in probably 20 minutes. But there's so much extra stuff to have everything functioning like keymap, licensing, vpn, restoring file backups, password manager, slack, web browser with security / personalisation settings, aliases, zshrc, ssh keys, every other program that I need to function as a dev (zoom etc). At a speedrun my local machine would take more than 2 hours to setup. That would be after I sourced a replacement, installed whatever os. As for my dev missing the day, that wouldn't be a happening thing. If he wants to take time off he's entitled to but turning up for work means turning up ready to go. I handed him my spare linux laptop and told him to fix his one in his own time. No B players on my team.