Non-clickbait title: Teslas running Autopilot have been in 0.0000273 crashes/km in less than a year!
I've been alive long enough to see a considerable sample set of human drivers and I've got to say the bar Autopilot needs to exceed in order to save limb and life is incredibly low. Couple that with the fact that just here in SoCal Tesla has become a common sight, 273 crashes sounds like a hell of a lot of human suffering was avoided.
As I've used slack over the last 5 years I've come to the conclusion that they have a quality problem of some sort. The software just behaves weird, especially in the voice and screen sharing areas.
It seems like their management runs the "quality via escalation" anti-pattern.
My grandfather, who I respected very much, was an accomplished career bureaucrat and considered any sort of promotion beneath him, and for sure crafting clickbait would earn his scorn. Thus marketing, promotion and crafting clickbait goes against everything I come from.
But, making something that I think will actually help people, and then watching it go unseen because I wouldn't do the thing required to spread the message via the network effect is a far worse fate.
“Tell me how you will measure me, and then I will tell you how I will behave. If you measure me in an illogical way, don't complain about illogical behavior.” – Eli Goldratt
Tables are probably the most overlooked feature of Excel.
Why use tables?
* Each column is uniquely named - no more wondering if you are referencing the right cell, no more thinking about "to $ or not to $"
* The table's rows and columns are reliably discovered by pivot tables - no more wondering if the entire dataset is referenced by the pivot
* New columns that are formulas are automatically applied to every row
* Tables have names, so it is easy to understand which table a pivot is referencing
The true, reliable and sane power of excel lies in Tables + Pivots + Charts. If you drive most of the problem solving into those paradigms you will keep hair!
A large part portion of the software industry skips this form of testing in favor of using a portion of production with health metrics to detect chaos. Which is alright, unless someone like Boeing does it with an airplane.
If unleashing chaos on users is bad enough for your business, then TLYF is a good pattern. Here are some scenarios that call for TLYF:
* Customer will die from chaos in software
* Customer will remove product if they experience any chaos
* Software is deployed somewhere that is hard to update - think non-internet connected devices, or regulatory required change control
* Chaos will cause significant loss of value
Both Boeing and Toyota failed to apply TLYF rigorously, resulting in uneccessary deaths.
The physical dependencies of a house vs the abstract nature of software interdependencies really makes the analogy fail for me. Houses just don't don't regularly fall down 8 times a day because one framer is putting a nail in a new wall and that caused the fireplace to explode.
How do you reconcile how bespoke and ever changing the requirements are for software products vs how stable the requirements are for garages?
I'm asking because I see the construction analogy pop up a lot and I just can't reconcile the two things.
To me the development of a new blueprint for a new kind of garage for a new kind of vehicle operated by a never before seen alien species is a bit closer to creating a software product.
I mean, who would ask a contractor to do what people regularly ask software engineering teams to do?
I started using slack about two years ago, and in my opinion they have a quality problem. There are just too many issues that crop up when they roll out change.
It reeks of the "just get it done" anti-pattern where done is change that hasn't had the chaos tracked down and killed.
I bet internally they are waiting for bugs to get reported instead of pro-actively running the changed software under representative load to hunt and kill chaos.
>The thing that hasn't come about yet though is, sales, marketing, accounting can also be outsourced. Dare I say automated.
Yep, just consider how much sales, marketing and accounting work the App and Play store has automated. Not to mention software delivery and installation work.
As a matter of fact I've seen the super-opposite more than once.
That's where the organization figures out they are having the team work on something no customer wants, but they decide the team should go ahead "finish" it, as if there is value in the company maintaining filler.
The worst part of the anti-pattern is when a software leader is trying to do a good job, but finds this puzzling behavior where people in the org just want to hurry up and finish the filler project instead of resolving problems like poor performance, bad customer experience, etc.
I've been alive long enough to see a considerable sample set of human drivers and I've got to say the bar Autopilot needs to exceed in order to save limb and life is incredibly low. Couple that with the fact that just here in SoCal Tesla has become a common sight, 273 crashes sounds like a hell of a lot of human suffering was avoided.