118 karma · joined August 25, 2023
Lens shows me repeats of log lines when I'm trying to scroll down in a live log. It has checkboxes but no means to operate on checked boxes. If I have my Secret set to show b64 decoded, and paste in a new secret that is very clearly non b64 encoded, it tries to push it as-is and fails quietly. It shows things as Healthy whose only sub resources are not healthy, but that's par for the course in Kubernetes land. I also have to fully quit it (not just close the window) on my new MacBook whenever I make the mistake of looking at it after a gcloud auth timeout, even when simply running fresh kubectl commands in the background every time would outperform the garbage Electron tab changes.
Plus, this new thing has resource diffs, which I was surprised Lens didn't have. Frankly I was surprised how little Lens has once I started actually using it and figured there'd be easy money in building the community's new favorite editor. But I'm glad to have seen this post, here's hoping it becomes the new standard.
Node.js sets stdin to nonblocking. This is great because it means copy and pasting a shell script containing an npm install into your shell will work, since the description is reset between each program by your terminal. But when those same lines are executed by the bash interpreter directly, processes after npm will randomly fail by failing to read from stdin with a return value they never expected to see. Ask me how I know
The lesson for me here is that there is no substitute for knowing or caring about what you're doing. Dancing cents don't happen when eng cared about correctness in the first place. I feel like I just read a college freshman explaining how there's no possible way they could have passed their first exam. Better yet he's here to sell us on his thought leadership without ever explaining why he failed the first exam.
For the lanes, they had some fancy new tablets in place of the old school 80s keyboard system.
We couldn't figure out how to change our names from "Player 1". Tapping the name did nothing. Navigating all over the various screens revealed nothing helpful. No help page. Turns out you need to tap the little default avatar for your player, barely a fingertip large. None of us imagined it was a touch target. When someone quit, it turns out you need to ask the front desk to remove them.
Eventually I noticed that there were no fun animations between plays, like the old animated videos of a bowling pin stopping his car to get out a "spare" tire. Just a scoreboard. You might say they were imitating the professional atmosphere upstairs, but then I wouldn't have bright lights flashing in my eyes during my approach to bowl.
The lane next to me reached a stuck state where no matter how many balls they sent down the lane, the system wouldn't pick the pins up or send the balls back. I had never seen this happen in my prior 20 years of yearly bowling, though I'm sure it happens occasionally.
What happened to computing? Are we the only industry whose output quality seems to go backwards every year? Is it just a beginning lull while we figure out how to provide lane bumpers for the Eternal September programmers? Or do we accept the econ-left topic of the year and blame private equity for our inability to produce UX, too?
Anyways, I do recommend the bowling hall of fame. The HOF player pictures look exactly like you want them to. Late in my last game a guy strolled by and explained how to bowl a strike by lining up on the right side instead of the left like I was doing. I handed him the ball and he threw a slow, easy strike, which scored me a spare because I suck. I thought he was an employee but I was later filled in that he was a hall of famer leaving the upstairs tournament late.