0xEFF

I do the same as GP on a regular 2 hour drive up I-5 I take.

The vetting process is the same as if I were driving up I-5 with a gear head friend of mine having a conversation with them as we go.

It literally says spy cam in the product title.

No company reflects “we’re family” in contracts or compensation packages. That fact alone tells us the message is and always has been bullshit.

I think it’s reasonable that 95% of people would choose generational wealth for their families given the opportunity.

Is it really unquestionable?

Even so, the suggestion is a good one. Modern proxies have gotten much better at handling auth and processing the traffic as the GP describes. Service meshes have these features built in now when a few years ago we had to roll our own solutions with haproxy or nginx.

A bank is a bad example. The only thing we use bank websites for is to check our transactions and transfer money.

My business checking account has started offering partner promotions from the transfer screen and I’m tempted to switch to another bank because of it. Their developers and designers were tasked with delivering that component. At the same time they took away their mobile app and mobile check deposit because it was not secured properly.

Most bank websites and apps are examples of teams and organizations focusing on the wrong thing in my opinion.

See for yourself, 4.0 is clearly improved over 3.5.

Every access and id token issued by oidc already has an issued at (iat) and expiration (exp) fields.

Splunk has delivered this level of innovation and quality since 2007 when I first used it.

We used Splunk to associate a change request ticket number all the way through the change control process to the Puppet log output tagging each change to the original business purpose.

It was like magic for auditors back then and I rarely see that depth of tracing automated changes to business purpose in the field today, though we get close with gitops.

It’s historically been abbreviated AAA “triple A” for Access, Authentication, and Authorization. Each being a separate system, VPN’s and Firewalls traditionally controlling access for example.

RedHat has traditionally.

The platform slack with over 10,000 users uses linen. It’s good. Wonder how long it will last though.

There are loads of startups offering platforms as a service for about half the cost per year of one devops engineer.