hcrean

Well, there are: The provable lack of regulatory oversight and demonstration of the existence of poor practices at the company.

The argument that just because one of a company's trials are unsound doesn't mean that the rest aren't is not a good one, when the whole objective is to provide assurance in proving the safety of a product.

Clamp it, charge the statutory maximum for parking on private property; then after a relatively short period of time you can start the claim for ownership on the grounds of abandonment. (There is some DMV paperwork involved).

That van is worth something if repaired, airflow on a sprinter is normally something you can do yourself. If not there is a whole lot of scrap metal sitting there...

For some it is a joke, for others it just reminds them of what the codebase looks like after the juniors have been peer reviewing each other...

There is an "ignorance is bliss" argument and a "if you don't know what is on offer, you can't ask for it" argument.

The whole privacy system is geared towards supporting employers and people in the upper echelons of salary.

I'm a DevOps engineer embedded in a Development team, (something about Spotify models being popular). Stand-Ups are a complete and utter waste of time and a lovely way to break flow in the middle of the morning.

No one knows what anyone else is doing, 99% of the time no one cares, Moreover people are all dealing with context switch and ineffective at relating how their thing might have a knock-on effect for others.

Sure makes team leaders feel like they are in the loop and valuable to an organisation though, especially ones that don't know how to ask effectively.

Thank you, this is better, but if I cat a 1000 line file I can only scroll up about 150 lines, I think this has something to do with the speed of the output(?); how does this work under the hood?

It is a VERY useful tool that I have used every day for at least 3 years.

There are two really annoying niggles that I have with it, but both I have solved by using a Screen session on the server:

- Scrolling turns out to be very important to most workflows. The choice to start mosh in Append mode (with chance of output corruption) rather than replace mode would be a cool thing.

- There is no easy way to pick up a session again when the client dies. I understand that this is an intended security "feature" though.

But beyond this it is a truly fabulous tool that has saved me many many hours of frustration.

Third over here.

I would be happily be friends with any person who says "it is more complicated than that", because it is a stepping stone to "let's investigate and understand a bit more". These are the people you learn from, regardless or political or religious affiliation...

I live half a mile from this, it is nothing short of creepy. They displayed it in the Grand Arcade when it was first introduced and people would actively walk the long way round to avoid it.

There are certain proofs of the dimensionality of space at different scales.

The equipartition theorem details that thermal energy is divided down by degrees of freedom. In higher dimensional space there are different ratios of translations to rotations, so observations of the triple state diagrams of diatomic vs monatomic molecules would diverge from observation.

The time it takes spheres to settle after falling into a square container is a function of the dimensionality of the container. Observations as we scale real experiments with steel ball bearings suggest that the balls can't move in any other dimensions.

In higher dimensional space the great geodesics are longer, we would expect a deviation in the relativistic corrections to the GPS system that we don't observe.

The interesting question however is at the largest scales. The universe might have much higher dimensions, we just happen to be in a relatively "compact" part of it...

As a former pentester, this makes me happy inside.

As a DevSecOps Engineer, I field requests like this from frontend developers all the time. The answer is always no.

In this case it would be "I am sorry that you are not happy with inter-team planning and communication; please raise this with the appropriate project owner at the next scrum meeting. Sadly poor communication can not be allowed to drive well established systems planning and architecture best practices..."

When there is something I don't want to do, I think of what Billy Butcher would say.

Sadly we can't be that direct in most of life, but the thought is normally there.

They can do this without keeping any meaningful information quite easily: They sign a client certificate with an expiry date at time of purchase using their CA private key (that the court obviously can't force them to give up, HSM etcetera).

Into the client certificate's DN or extended field they write the allocated public IP.

The only information they need to store is that that IP is spoken for and not to be allocated again. They could also work this out on the fly.

When the client comes to connect, they note that the certificate is signed and presented, and they route the public IP to the in-tunnel address of the peer, which they will have standardized to something meaningless like 10.0.0.2

As long as they don't log anywhere in the process, the signing of certificates means you don't have to remember the client at all.