@jessfraz I've been calling this state probalistic production. Essentially the insecure code slop is iterated upon exclusively by agents piecemeal without architectural direction, coupled with DRY direction thereby rendering the code illegible within the project's context. Rewrite.
@ShawkyMesbah@Grady_Booch@gdb It is a bug. Ask a machine to do something 2x and if you can't substantiate the difference, one must be wrong or inferior. You can certainly quantify. The thing is, the whole thing is a ruse. The machine never thinks. You are getting a result based on a rand.
@FUKUHARABC@wrong_speak I think carry-on has turned into bag avoidance fees. Get rid of it all, and put everything bigger than a purse/tote in baggage. It is slowing down boarding/unboarding and. Then open ceilings like this pic
@ottowner@Peterson_IsKing Agree. This is a cultural issue. They don't have an identity. Throw the city unis out
Orange Blue only. If you want to express yourself you are Met on the diamond. You look like a retard when your sleeves don't match, yellow shoes and neon mitt. Then Baty learns/is tard.
@Grady_Booch@CrowdStrike Do you think CRWD users should've had a way to stage deployments of updates in rings prior to fleetwide rollouts? Subjecting production kernels to mandatory internet updates seems reckless. Root cause is customers bypassing zero trust tenet of file verification from vendor.
Clearly customers did not smoke test #Crowdstrike updates. This is an IT implementation failure as much as an upstream snafu.
IT departments must take responsibility.
Post mortem should highlight IT doesn't know how to quickly recover from a BSOD at scale and hasn't practiced.
People can blame #Crowdstrike, but the mass outages are the fault of Corp IT Depts. Trust was misplaced in an autoupdate process relying exclusively on vendor validation. IT failed Patching 101. It is their responsiblity to test and VERIFY SW updates are non-breaking changes.
@MetsLegends The absolute correct answer is David Liddell and it is not close by a mile.
There is noone more obscure and more perfect for an entire MLB career.
iykyk
@mipsytipsy@copyconstruct@hillelogram haha. Until I see coding tests disappear from interviews, this is nonsense. It is hard to write good code and should not be minimalized.
Being a big idea person and throwing around popular tech is more likely to get you a functional architecture than a functional codebase.
@Steve_MSFT@mrtaanderson Microsoft needs to lead by example, and remove internal dependencies on 5.1, not continue this madness. It was done for versions 1-5.x. This is a solvable problem.