Everyone else: “Dogfood update: features w,x,y,z are all working great in the latest build”
Me: Stonk Tracker is working.
Everyone else: “Dogfood update: features w,x,y,z are all working great in the latest build”
Me: Stonk Tracker is working.
Was teaching a coworker Terraform today, the question was asked:
“So what happens if changes are made to something that was spun up with Terraform via the AWS console?”
The answer, of course, is that no one is really sure because the second they do it they lose access to the AWS console forever.
Me to other dad at kids birthday party: “so you work in tech.”
Other dad: “yeah how did you know?”
Me: “your eyes are those of a tortured soul who is constantly being pushed to do more, with less, in pursuit of an always moving goal that you can never achieve. All the while being made to attend mandatory sessions to set objectives and key results that should align with a top down vision that constantly changes anyway.”
Other dad: “woah.”
Me: “also the splunk t-shirt.”
As far as I'm concerned, the hardest part about teaching a technical course is "Day 0: Laptop Setup". When students bring their own devices, you have very little control over the environment:
- "work laptop, I can't get VMWare to install"
- "I run Redhat - do you have something for that?"
- <Virtual Network Troubleshooting Terror>
To avoid this in the future, I've been tinkering with JupyterHub and Code-Server to provide a "DIY Github Codespaces" experience.
What I'm realizing now is, this is also perfect for engineers who work a companies that:
- Won't let them have local admin to manage their dev tools
- Don't have the budget for Codespaces
My favorite part is integrating Github OAuth. If you're a member of my Github Org, you can get to work.
Here's a copy of the configs I used to get things up and running... https://github.com/hashtagcyber/coderhubK8s