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.
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.
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.
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.
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.
I've never used it although I've been aware of its existence for a long time. It's great to see a tool actively developed that uses a boring-yet-great-and-well-known framework (Django + Templates). Ironically, it's refreshing to see that stack in a world of JS frameworks, microservices and what not.
I've been using Firefox on the PC and phone for years now. I had the temptation a couple of years ago to use Chrome due to some issues I had on Linux (I don't remember what exactly) but then I concluded the obvious: using a browser made by a company that profits mainly on abusing user's privacy? Nah, I think I'm gonna pass.
Agree but, I have to say that, as a DevOps, it was infuriating to me to have to deal with developers without any care for the quality of what they were delivering. Sometimes for pressure from someone higher in the chain, other times, for pure laziness and/or incompetence. I remember coming in the morning after a hell of a night on the on-call, reporting the issues to the Devs in charge and being answered something along the lines of "fixing that is not the priority right now" and my replying on anger with "If it was your damn phone the one ringing during the whole night I'm pretty sure you would make it a priority".
On call sucks so badly. At this point of my life, I firmly believe that there's not enough amount of money that can compensate the mental suffering it implies. Even more if the company you work for has this mentality of "deal with it" without making improvements, which was my case in the last period I did on call and what made the camel's back to break for me. Nowadays I simply refuse it. For those who are still on the trenches, stay strong, never resígnate yourself to just "deal with it" and thank you.
Yes. I've been a long time Linux PC user (Thinkpads and Dell mostly) so without any shame, I have to admit that the quality of Apple devices is miles ahead anything else I've tried. Also yes, I simply cannot stand MacOS. I can recognise its virtues (and its limitations) but it's just not for me.
IMHO and I might be entirely wrong but placing and coupling all that logic into the database seems like a bad idea and it's not a question of speed, it's a question of separating responsibilities. Also, for the case shown in the article, it seems all right for a "hello world" kind of thing. For something complex or prone to deep changes (like most of software projects I've been involved with), this seems like a true nightmare.