[1]: https://dbeaver.io/
93 karma · joined January 15, 2015
[1]: https://dbeaver.io/
Don't be hard on yourself for not spending every waking minute of your life working, preparing for work, or feeling bad because you "should" be doing one of those two. That's a very quick way get burned out.
YMMV, but in my experience, even if you want to optimize your life for doing the best work possible, not working all the time is a winning strategy!
I don't remember if they answered exactly what you are asking, but my memory of the episode is definitely positive!
We started by using https://github.com/segmentio/chamber/, but because of the way we decided to structure our secrets we decided to write a clone of it ourselves (https://github.com/micvbang/confman-go).
In practice, we have a client written in Python that grabs configuration from Parameter Store and puts it into the process' ENV variables at startup. This allows us to avoid vendor lockin in the rest of our code, since we still just fetch all config from the environment. I like it so far :)
(I'm in no way affiliated, but stumbled upon it on twitter a few weeks ago)
The somewhat silly video on that page shows the actual difference in performance our users felt after the change. It was a _huge_ benefit, both in terms of loading time, but also in terms of memory, vastly increasing the number of CS:GO rounds that could be analyzed simultaneously.
After being given the advice couple years ago, I found it to be applicable to quite a number of scenarios me and my colleagues faced. In my experience its pretty solid!
EDIT: For those who do not want to google it themselves: https://forum.51nb.com/forum.php?mod=viewthread&tid=1699442&...