skarlso

Just a small remark that dog-autoscaler which is `cluster-autoscaler` supports scaling to and from 0 pretty nicely. I even implemented that functionality in cluster api provider aws using cluster autoscaler. Which probably why the native support isn’t going along so nicely.

Thanks very much!!!

I _WISH_ this would be 2005. Did you ever work at a bank? They are still using 1.6-1.9 maybe.

I still know modern Java codebases where long descriptive class names are a must. So sadly, while I understand your sarcasm, it is not the case.

This feels like it has been written by someone who recently started using the language, considering that the code in many places simply doesn't compile and has syntax errors or logical errors in it.

Many people coming into Go as a new language immediately start bickering about how they want their previous language features in Go rather than accept what Go has to offer and at least try to understand it. This is the equivalent of moving to another country and then refusing to integrate but being very vocal about how said country sucks.

I genuinely appreciate Go's error handling because it's clean and on the nose. It's not hidden behind weird syntax/values that you have to unpack. It's right in your face all the time. When you read the code, it reads cleanly and understandably, even for a beginner. They don't have to adapt to some weird combination of failures / unpacking/choosing something different when there is an error; you immediately see that there could be an error.

And regarding stack traces, wrapping errors will provide you with failure locations to the line code. You can have all sorts of nice output for errors you can later parse and identify.

I get that some people go into Go because of a shift in the company and have no choice; I feel you. For me, it was a life changer. I learned to love coding again after 15 years of writing Java Beans, Spring annotations, CreateMyFriggingObjectFactorySingletonBuilderFactoryBuilders.

Heh this just happened to me. I have to go through some loops to get a really good solution. I call it think by doing. I suck at very high level abstract things to find problems. But once I begin working on it and fleshing out details and seeing actual code that’s when my mind kicks in and finds problems and better solutions to the overall design.

If you want to stay in the command line there is an excellent cli you can use https://github.com/yitsushi/totp-cli.

It’s an excellent tool that has great encryption and handles multiple accounts and can paste into your clipboard with `totp account.name|pbcopy` and asks for a password on stderr. Pretty cool stuff.

Aye. I feel you and I’m with you! Thank you for your words!:)

A little story about how I got into journaling the old way. Why digital didn't work for me and how I rediscovered my passion for writing.

This is not a self-validation story, nor is it trying to convince anyone about their way of being wrong. This is a story about me. :) And I hope an enjoyable one. Whatever works for you, dear reader is whatever works for you!

*Warning*: Light mode only on my blog, sorry. I'm working on it.

A practical summary of the book. Contains a summary of the book but also my musings about what was interesting for me in particular.

Is everyone forgetting about mutt (http://www.mutt.org/) being a thing?