t3rabytes

Agency heads can be SES and can make more than GS-15, but the max is still far lower than private sector equivalent.

Right up there with New Relic writing a blog post about how you couldn't trust Sumo Logic (and should move to NR) after they got bought by Francisco Partners, only to be bought by Francisco Partners themselves.

It was available for 6 years (2011-2017), that's hardly a failure relative to other Apple products that have only made it through 2 cycles (the most recently iPhone Mini sub-family that lasted 2 years).

Bezos isn't the CEO, and hasn't been since 2021.

It seemed like the initial Direct File rollout was limited to states that didn't have a state-level income tax, or directly cooperated with the IRS. Are they forcing all states to play ball, or will Direct File not cover state tax submissions?

Essentially. Take the Visa credit card lines for example -- Visa Infinite cards have a higher transaction fee than a Visa Signature card, and the high-end travel cards will be of the Infinite variety (Chase Sapphire Reserve).

It works (and is the best option bar-none) until the big few lobby the state to outright ban municipal ISPs as happened in my state (NC). So frustrating.

AWS has a UI for resources in the cluster but it relies on the IAM role you're using in the console to have configured perms in the cluster, and our AWS SSO setup prevents that from working properly (this isn't usually the case for AWS SSO users, it's a known quirk of our particular auth setup between EKS and IAM -- we'll fix it sometime).

Yep, I'd say >half of the teams with K8s services have adopted KEDA, but we've got some HPA stragglers for sure.

HPA is useful until your maxReplicas count is set too low and you're already tapped out.

My current company is split... maybe 75/25 (at this point) between Kubernetes and a bespoke, Ansible-driven deployment system that manually runs Docker containers on nodes in an AWS ASG and will take care of deregistering/reregistering the nodes with the ALB while the containers on a given node are getting futzed with. The Ansible method works remarkably well for it's age, but the big thing I use to convince teams to move to Kubernetes is that we can take your peak deploy times from, say, a couple hours down to a few minutes, and you can autoscale far faster and more efficiently than you can with CPU-based scaling on an ASG.

From service teams that have done the migrations, the things I hear consistently though are:

- when a Helm deploy fails, finding the reason why is a PITA (we run with --atomic so it'll rollback on a failed deploy. What failed? Was it bad code causing a pod to crash loop? Failed k8s resource create? who knows! have fun finding out!)

- they have to learn a whole new way of operating, particularly around in-the-moment scaling. A team today can go into the AWS Console at 4am during an incident and change the ASG scaling targets, but to do that with a service running in Kubernetes means making sure they have kubectl (and it's deps, for us that's aws-cli) installed and configured, AND remembering the `kubectl scale deployment X --replicas X` syntax.

[Both of those things are very much fixable]

They might not still have the game source and/or knowledge on how to recompile the game. There are lots of technical reasons that it might be entirely unworkable to do that even if they wanted to.

(disclosure: work in video games at a big studio where I know for certain there are things we couldn't build again at this point without a ton of work)