HN user
Repetition is a very common tool in writing (ie 'I have a dream').
I'm just irked that it's being called out for AI slop because "I feel it in my bones!!"
There's a good chance it was written using AI -- should that matter? If the content is wrong/sucks, say that instead. If you're going to dismiss all AI assisted writing: good luck in the next decade.
Where do you think it learned that phrasing from?
As silly as this sounds, the same thing happened to me. I was getting pretty frustrated because all of my pants kept shrinking.. the truth hurt.
Pretty severe -- ADP allows users to store data with e2e encryption.
Disabling ADP is a pretty serious* thing to do -- and pretty disappointing since I was interested in the product. Since it's OSS though this might be something that can be worked around in the future.
Anyone who's trying to secure workloads running in any EC2 instance should know about this, there's nothing special about it being an ECS instance. You could do the same thing with EKS.
I find these kinds of articles very helpful in professional communication. It's not because they're scientifically accurate, but I often find myself pausing and thinking about what I've heard and how I will respond. As someone with ADHD, just that small moment allows me to take in information and compose my thoughts to communicate better.
I try to think about developer experience in my day-to-day. K8s might make deployment for the DevOps team easier but more painful for the devs, and that's not good because they are the ones who make the company money. So work together with the developers if they're complaining to make it possible to ship code as fast as possible. If the devs don't like settings in yaml files, find a way to abstract that away (use standardized naming so there's fewer values they have to care about, give sane defaults that won't be overwritten 90% of the time).
The DevOps team's sole existence is there to enable developers to ship better code faster. If DevOps practices are preventing this, that needs to be addressed.
One additional one I would add is: don't be an ass. I have seen a fair share of people in this role belittle QA, Devs, and interns because they're not able to follow along or understand how to use DevOps tooling.
I like to think of the role as hospitality; you don't particularly have to like the guest but try to create a good working atmosphere.
A specific example: if a particular dev runs to you every time a build fails and tries to blame the environment: force them to check their own work first. If there's another branch that builds, ask if it's related to one of the changes in this branch. Ask if the code builds locally. Ask them what they've tried so far to debug the issue. These questions will help out anyone who does not know how to actually troubleshoot build failures and discourage anyone who is simply trying to pawn off their work.
I've always wondered if being forced to live near the plants would change regulators minds. There are plants throughout the country, so if you want any say in safety regulations you'd have to live within 1km of the start of the safety zone.
I'm an advocate for nuclear power but it seems ridiculous that this warning was given 20 years after the initial find.
I understand that nuclear facilities are not like regular buildings and require more logistics for repairs but there's no way it would require 20 years.
While you can't explicitly allocate a process to E cores, I wonder if you'd be able to make a program which floods high QoS processes to saturate E cores until they are full and then launch the desired application into a P core