“Another option” meaning what? Drive thru coffee? We do have Dunkin’s here, but none of them are drive-through. This may be different the further north you go, however.
Going to Starbucks doesn’t mean I have to look down on people. Life’s too short for that. I judge people on the complexity of content of character, not “Oh look, a ‘basic bitch’ with Starbucks and Ugg boots. How droll.” Having “no taste” and “too lazy” are classist statements anyway, “no taste” according to what standard? Lazy compared to what? What standard are you adhering to to “be proud of not being a tool?” Anyway, independent of your personal judgement of people just trying to get through their day, they are going to keep doing it and not caring about any of the complexities.
Starbucks is a service. You don’t have to like the service. I don’t get my legs waxed, but I don’t look down on those who do. Same thing. People are more than just their personal choices of our selective judgement. I recognize that Starbucks is popular, even if I don’t care for it. My reasons are basically I am cheap, and have to watch my sugar intake, so most of those milkshakes-posing-as-coffee are off limits. But if I am on a Starbucks run with someone, I am not going to patronize them like somehow I am some intellectual balloon rising above the mists of their complacency. Life is too short for that nonsense.
Yes. Most of them were east-to-find solutions on the web, or someone else giving me access. “Can you reset my password on Blah?” “Try TempP@ass123.” “I’m in, changed password. Thanks.”
A few times when I am really acting like a Senior Linux Administrator is figuring out a kludge or back door nobody had thought of. Recently, a client told me that the former admin had left and didn’t leave the password to over 300 systems (it turns out he did, the client was clueless, but I didn’t know that in the moment). I found every system the admin had access to, and looked for a dev box where he had access but I could take down during production hours. I took it down, booted into init with /bin/bash, changed root password, brought it back up. Then I checked his home directory to see what public keys he had. Based on that, I checked to see if there were any private keys on the bastion systems that matched as a pair (using ssh-keygen -l -f on each pair to see if the signatures matched). They checked which pair had no password. That was pretty quick because I quickly discovered a majority of these cloud systems also had an ec2-user that could escalate to root via private/public key pairs (it is supposed to be removed for security reasons, but wasn’t). Within a few hours, I had full access back to all their systems. Without taking down production.