I was not able to understand why these code points are bad. The post states that they are bad, but why? Any examples? Any actual situations and PoC that might help me understand how will that break "my code"?
True. Most services (unless your service is a demo/toy project, as I stated earlier) have way more traffic. It might not be evenly distributed though the day, but if you add all the CPU time in a day, I’m sure it will exceed 24h. So that leaves me with the question for who is this? Developers that are starting and want to deploy something small?
Say I want to deploy a service that is currently receiving 1rps at a constant rate, no upticks, no gaps. Wouldn’t that be the cost? If the answer is “yes”, then no, that is a terrible pricing.
If my math is not wrong, running a single “standard” container during 1 month (non-stop) would cost ~55$.
This looks extremely expensive for anything other than a simple demo/toy project. I can’t think of a reason I’d use this for heavy services instead of using [anything else]. Maybe I’m not seeing the use-case?
Exactly. People usually think of “them” as the very wealthy, but they don’t even realize that earning just a little bit over $40.000/year makes you belong to the top 10% of the world measured by wealth. Earning $60.000/year takes you to the top 5%. Chances are that “you” (average reader of HN) belong to the “them” you critique so much.
I did an interview for a Senior Backend role with them. I’m very happy with how they managed the process. The interviews were technical, but in a practical way, not in the “let’s see if you can solve some leet code” way. Loved the guys I interviewed with. Loved the technical challenges they told me I’d be working on. I’m a little bit sad I wasn’t able to join them (despite them offering me the position) because they had a ridiculously restrictive contract (wasn’t allowed to have side projects, not even contribute to open source). I had to reject it :(
Not really sure why companies hurt themselves in this way.
No matter how many tech bros try to force it through.
Are you sure about that? My wife is a nurse and she has to deal with multiple machines that were put in her unit just because the hospital has a contract with XYZ brand. It doesn't matter at all if these machines are 5x more expensive, x10 slower, x80 less effective, etc... compared with the "other" machines (from other brands).
I'm actually terrified the same might happen with this.
Can’t we split the packages into logical groups and maybe have 20 or 30 monorepos of 70-100 packages? I doubt that all the devs involved in that monorepo have to deal with all the 2500 packages. And I doubt that there is a circular dependency that requires all of these packages to be managed in a single monorepo.
Context: I have +10y exp with Python, Linux (some packaging, kernel hacking, sys admin / SRE), C, several cloud providers (AWS, Azure, Hetzner, DO, OVH), etc...
Applied to a Canonical position (Senior Python Eng + required Linux exp + nice to have cloud knowledge), got rejected automatically because I don't have a university degree.
Tweeted about it, asking for some feedback. Tons of replies, same opinion: Canonical are plain elitists.
I have the feeling that any day now I’m gonna wake up in the morning and I’ll find out that there just isn’t internet anymore because somebody did something from a hotel room in the middle of nowhere with a raspberry pi connected to a wifi hotspot of a nearby coffee shop.
The article doesn’t say how he pulled off his escape, just that he got in a car and he got driven north to French administrative territory. Very vague.