longcommonname

I wonder if the NHTSA could require all self driving cars to use lidar if the safety stats show it is a significant safety improvement.

We wrote a custom controller that manages Google workspace and github groups. This allows us to use those groups for identity.

Changes to those groups happen solely by the PR process.

HR, is only responsible for adding them to the single group which allows single sign on access not does not give any other access.

Here come the tesla fans quoting stats about how safe tesla is.

I don't care how safe it is, its nowhere near as safe or reliable as the sales and marketing are pushing. I wish it was criminal how misleading tesla has been regarding reliability, and regarding how close they are to full self driving.

What resources are there that go inepth into platform engineering?

I currently see myself in a position where I'm responsible for direction of a platform.

What best practices are there around common things like urn, config management, infra provisioning, and other common components.

I have my best practices, which I could enforce on users. But how do I know what is most important to focus on.

I tried to use managed elk from elastic.co.

The actual product is pretty decent. They have sane defaults for security and unlike their open source product they enable security by default.

The management of it sucks. Management console is tied to a single email, theres no MFA, and the ui is only good for creating es instances. Anything production that stores data and open to public internet full stop must have MFA.

I'm not sure what elastic should have done here, but this is not the right move.

Imo a sysadmin that transitions to sre has a higher capacity for immediate impact, and a higher propensity for long term toil increase.

A dev moving to sre will often need to be taught the importance of documentation, how to have smaller immediate impacts and a customer service mindset.

Theres a middle ground that is difficult to find, but is essential to balance the value you bring to the company with the amount of future work you're making for yourself.

Some of the worst sre I've seen involve a dev taking the title and refusing to support, collaborate, or communicate. Alongside a former sysadmin that refused to document, bypassed ci/cd process, and constantly declared tasks as impossible.

When I'm interviewing a sre candidate I focus on identifying if this person has behaviors that make them Ill suited for sre. Technical skill is often easily faked, and your behaviors around how you admit you don't know are more telling than you not knowing.

At some point this will be like taking out the trash. Lots of money in making sure it's done right.

Companies who can do this correctly and cheaply will be able to charge for this service.

Op question made me think of a few others.

Why is a molecules with high energy density so difficult to break down?

Why are there so few natural decomposers of plastics?

Is this because bacteria haven't evolved the correct enzymes, and many other non plastics globally have bacteria consumers that we can just assume that they decompose naturally?

This is often quoted that tesla has a lower accident rate than other vehicles.

Comparatively, how often do those vehicles cause deaths while directly taking control of the vehicle.

How comments in school indicate to the grader that you not only can write code but you can explain what it's doing in another way.

It's actually a somewhat decent way to catch cheaters. As it provides a better likeness score between two code comparisons.

We recently did a similar thing at the company I work for in response to similar pressures.

The effort to make that change was significantly less than the continual effort required to deal with the pressures. From a cost perspective their decision makes sense, from a customer perspective less so.

It took a few months, working In a massive multiple million lines of code "rules engine". The first bit was really understanding how recursion works and how to trace the code.

After that close understanding of logical operations like cut, or negation, and the most important was how certain operations could really impact performance to the point the were mostly "outlawed".

It's been years since I've used prolog, but I could probably pick it back up in a few weeks.

I would expect the communication to be directly targeted to customers not the general public.

Sre workbook page 317.

In addition to the others answers, memcpy of size zero is undefined in certain cases.

This and the other two bugs can be particularly nasty when doing something such as an arena allocator or any other means of user memory pools.

After an incredibly long slog on some particularly nasty corruption issues years ago I was only able to identify the problem by using ld preload and patching memcpy with some simple value and boundary checks for these three problems. Each of them was a source of the corruption.

We use it, I'm not on the team that uses it. Basically a lift and shift of our backup data center which came with all sorts of improvements. It's quite a bit more expensive, the projects that it runs in cost more than the rest of our cloud costs in total. But the man hours we've done to set up those other cloud systems (Terraform) are much more costly.

They can pin an older version and have it work.

One of the most disruptive changes was the master-> something else.

Sure the default is now main. But for a few months teams came up with their own standards. Now when I'm working on large scale changes across many systems I continously have too be aware of these new defaults.

trunk main dev develop main prod Canary ...etc this is time I wish I didn't have to spend. The amount of effort I've had to spend has done nothing to benefit race relationships and of course we still have master branches laying around.

I mostly disagree, but in a native implementation you probably do have strong data coupling. You can have cdc feed to another system that performs enrichment or transformation.

Cdc also enables all sorts of non obvious changes that are infra focused. It's much easier to update your version of sql server, db2, mongo, etc. If you don't have to worry about every other app and how it connects to your shared service.

You may think that you're being smooth by updating a A record or Cname when doing a migration but very often there's an app out there accessing using an ip.

Maintenance costs of any software should be taken into consideration.

I can say that we've had our troubles with kafka sure. But app teams 100% love working with it instead of having to have familiarity with all the various data sources we have.

Working with all sorts of different data but all of its kafka is much easier than all sorts of data from Many data sources.

That's a useful stategy, yes. But scaling your database is one of the more costly things you can scale.

When you have a monolith database that everybody wants to access Kafka with CDC is a very good pattern for teams to adopt.

The alternative is modifying your app for arbitrary data access and dealing with auth or giving direct data access.

Giving direct access to your database is fast but leads to very strong data coupling.

Exposing the data through the app layer is slower than cdc kafka integration but comes with a long term commitment to support that access. I have seen these type of data access queries easily hit performance edge cases.

There are other pros and cons but those are the ones that end up being the most troubling.

Often a single apps data can be incredibly valuable and many teams want to access it. So coming up with patterns that

1. Protect the app 2. Protect the data store 3. Decrease the maintenance cost of the app 4. Decrease maintenance cost of the datatype 5. Add sight complexities from kafka.

Can be very valuable.

Because there are great tools like artifactory that can handle all the arrifact types.

Theres a huge benefit to having an entire company help you out with kernel fixes, and all sorts of problems.

This means you don't have manage this yourself.

Shouldn't this warrant a 2.0 release?

For anyone following along. Don't do this if the code base is already hotshit. This will only make things worse and not prevent errors, just cause more outages.

I don't like devel, because its usually coupled with git flow and stale release branches.

How much money does your company contribute to Jeff?

Good. My kids got me into minecreaft recently. The concept of bedrock, windows10 java. Was a really stupid concept.

Figuring out how to buy the right one, and then getting frustrated with cross-platform.

Note that I had a beta minecraft account years ago... but I never used it. They did a similar thing a few years ago and people had to migrate their accounts.

Let's hope they don't fuck it up like league. Their account conversion changed my username because I had another account with same login in a different region.

Coming from a company that has capital one as a customer. They are one of the dumbest related to security.

Banks are still in the stone age when it comes to NIST and cyber security.