Octabrain

Thanks for creating this. However, I was a bit puzzled when I found a packages.json and then saw that all the heavy lifting is done from bash. I don't understand the need for having to install Yarn for just running a bunch of bash scripts. IMHO, after seeing the size and the amount of logic within the scripts, I think you could have made it more ergonomic by just building a bash script that takes parameters and that's it.

Yes, at least conceptually. However, CDK is more opinionated, uses Cloudformation and depends on its own CLI.

I'm working on a side project which is a Python library that provides of an abstraction layer to manage infrastructure in cloud providers by interacting with their APIs. This is something I've been developing every now and then for the last months after years of working with Terraform and getting tired of the limitations of it's DSL (yeah, Pullumi is better but I just simply want a generic library with classes representing services in the cloud I can call natively in Python without having to deal with a 3rd party application like Pullumi is!).

I can relate to this. I used to be on call for many years and honestly, it destroyed my mental health. In the last company I did it, it felt like falling in a meat grinder for a week. I remember once spending a whole weekend giving support on an bug that was introduced by a recent release. 72 hours of working non stop. Because of that among others, I got a severe burnt out that took me to the deepest dark place I've ever been.

To this day, I simply refuse to do on call. There's no enough money you can pay me that would make me to suffer that again.

PS: Fuck you, Rackspace.

I hate flying with passion and get extremely scared when flying through turbulences but, there was a journalist in my country, that also had experience as a pilot and said once on TV that during turbulences, is one of the safest moments in a plane. I don't remember the reasons but is there anybody in here with knowledge in the field that could confirm/deny this?

Same thing happened to me when I moved to the UK: I went to the supermarket, bought one jar or Marmite, went back home, had a toast with it expecting to have some sweet-close-to-chocolate flavour and then I was shocked. I have to admit that I actually liked although I don't eat it regularly these days because that wild amount of salt cannot be healthy in any manner.

I don't get your point. I just use two ways:

1. With mouse -> Up left corner (a.k.a hot corner) -> Click on the window I want.

2. With keyboard -> Alt + Tab -> Select the window I want.

I find that quite straight forward. Again, it's a personal thing.

It's just a personal thing. I try to stick to using tools that provide me the best defaults + being open source. I don't want to spend time customizing my desktop or getting overwhelmed by the amount of different choices I have available. Don't get me wrong, KDE is a beautiful and great project, it's just that, a very personal thing.

I like its simplicity and the straight forward workflow it provides. Years ago, I used to use KDE and enjoyed it but these days, I want something that is functional while being vanilla and standard as possible and personally, that's what GNOME gives me.

My conclusion is that this "chaotic scenario" happens when humans work in big groups. It's extremely hard/pretty much impossible to coordinate big group of humans and made them to work efficiently. In fact, this is one of the reasons by which nowadays, I personally prefer to work on a small start up environment instead of a big corporation.

Where I work, we use Confluence and Backstage. Confluence sucks and Backstage, although I conceptually consider it appealing, sucks too.

Would be this something that can be avoided by setting up BitLocker with the encryption password to be provided at boot time by the user? Because that's the way I've always configured it when I've used Windows in the past, due to me being paranoid and suspicious about the default "key saved on TPM" approach.