Re:It Takes 16 Clicks for a Student to Open a PowerPoint on ...
by Viliam1234 on Saturday November 14, 2026 @04:52PM
(#50501310)
My morning: Turn on the Mac. Username, password. Switch to insecure wifi. Microsoft username, password, phone call. Then for some reason Mac asks for the password again. Switch to secure wifi. Kerberos username, password. Microsoft username, password, phone call. Finally logged in!
Well, that's not the end of the story, because despite having a "single sign on", I actually have to log in to everything separately... using the same username and password. So I open Jira: username, password. Bitbucket: username, password. Jenkins: username, password. AWS... well, that's where it gets too complicated.
My first 15 minutes of work are spent logging in. On a good day, everything works predictably. On a bad day, something randomly breaks, and the easiest way is to restart the machine and do the 15 minutes again. If it fails the second time, I check if my colleagues are complaining, too, and then we wait for the tech support to tell us what broke recently.
1. Log in to OKTA and choose my specific account (we have 2 accounts for some reason, and only one of them is used for development) 2. Log into AWS with that account 3. Select another sub-account in AWS 4. Navigate to my developer EC2 5. Start the instance 6. In VS Code, open a terminal and log in with “aws login —profile myName” 7. Wait for redirect to AWS in the browser window 8. Click ok and close the tab 9. Back in VS Code, open remote explorer and click on a preset that does an ssh tunnel to my workspace on the EC2 10. Wait for VS Code to spawn a new window 11. Now I can go through all of my other development setup tasks (another 6-10 steps depending on what I need to do)
Every day. And our instances force auto-shutdown at 9pm, so if you need to work late, better save your work, log off preemptively, and go through the same process.