#root-beer

Ordered a root beer float. It cost 2.499999999999999998

A programmer walks into a bar. He says "I'll have 0x01 root beers".

The bartender pours him a root beer.

Another programmer walks into a bar. He says "I'll have 1.0f root beers".

The bartender pours the second programmer a root beer float.

I think I made someone angry, then sad, then depressed.

I usually shrink a VM before archiving them, to have a backup snapshot as a template. So Workflow: prepare, test, shrink, backup -> template, document.

Shrinking means... Resetting root user to /etc/skel, deleting history, deleting caches, deleting logs, zeroing out free HD space, shutdown.

Coworker wanted to do prep a VM for docker (stuff he's experienced with, not me) so we can mass rollout the template for migration after I converted his steps into ansible or the template.

I gave him SSH access, explained the usual stuff and explained in detail the shrinking part (which is a script that must be explicitly called and has a confirmation dialog).

Weeeeellll. Then I had a lil meeting, then the postman came, then someone called.

I had... Around 30 private messages afterwards...

- it took him ~ 15 minutes to figure out that the APT cache was removed, so searching won't work
- setting up APT lists by copy pasta is hard as root when sudo is missing....
- seems like he only uses aliases, as root is a default skel, there were no aliases he has in his "private home"
- Well... VIM was missing, as I hate VIM (personal preferences xD)... Which made him cry.
- He somehow achieved to get docker working as "it should" (read: working like he expects it, but that's not my beer).

While reading all this -sometimes very whiney- crap, I went to the fridge and got a beer.

The last part was golden.

He explicitly called the shrink script.
And guess what, after a reboot... History was gone.

And the last message said:

Why did the script delete the history? How should I write the documentation? I dunno what I did!

*sigh* I expected the worse, got the worse and a good laugh in the end.

Guess I'll be babysitting tomorrow someone who's clearly unable to think for himself and / or listen....

Yay... 4h plus phone calls. *cries internally*

Today I experimented a bit with Dockerfile's.
Was quite surprised how far you could go with a spicy salsa of ARG, ENV, SHELL and multi stage builds.

But... For fucks sake....the debugging is like poking a light year long rod into a black hole, trying to fish something out of the event horizon....

In the end I got a nice setup for Java build's, version injectable with ENV/ARG, non root user and version specific behaviour.

As the debugging is non existing...

I filled up more than once my SSD....

It was an annoying brain damaged repetitive cycle of changing Dockerfile, pruning all images if docker build stopped because of missing free space, waiting for all stages to complete, start new.

And caching is a fragile thing that puzzles me .........

Guess more fishing tomorrow.

*Gives a happy deep throat to the beer bottle in hope of death*

Not my week for tech.

5 year old 21" desktop monitor burns out. 2nd monitor, so at least not completely down.

Then my toddler reached for my root beer and spills it on my 1 month old laptop. I quickly pull the plug and turn upside down, get it wiped off and pray. Next day, arrow and enter keys a little sticky and battery is blown. The 2 exact fucking reasons I bought the new laptop. (keyboard issues and battery)

Keep em coming tech gods.

The trifecta: Software, Root Beer, and Comic Books

!rant I made the mistake of consuming a root beer float too fast and ended up feeling nauseous.

But then I remembered there’s a stupid trick that sometimes works where sniffing rubbing alcohol can sidetrack your system to prevent nausea so sniffed the heck out of an alcohol wipe.

Successfully avoided puking. Great success.