Worked at a web property that took scrum, used it and found it lacking in certain cases for development. They Extend it And called the new creation beyond scrum, abbreviated as BS snickers.
Unrelated to the shortcomings
we found that Scrumm with the timeboxing concept did not work for infrastructure teams.
You cannot just time box most Infrastructure task and just ship whatever you have when you exceeded your initially planned timeframe.
We came up with Kanban as a way to document progress. The swimming lanes together with a limit on things that can be simultaneously in flight served to mirror reality as an operational team much better than pure Scrum.
Southwest Airlines Flight 1380 was a Boeing 737-700 that experienced an uncontained engine failure[a] in the left CFM56-7B engine after departing from New York–LaGuardia Airport en route to Dallas Love Field on April 17, 2018. […] One passenger was partially ejected from the aircraft and sustained fatal injuries[…]
The numbers would go up quite a bit if it included private and military. The numbers you linked to seem to have a very tight definition of which flights were considered, as the Wikipedia list showcases several more in-flight deaths involving air carrier class airplanes than just two.
I don't understand how you arrived at the number 51. Did you just tally up all the incidents in that list that occurred after 2009?
That list includes a bunch of incidents that are not really relevant for assessing risk level when flying on a commercial airline:
- Someone committing suicide by getting sucked into a plane engine while the plane was on the ground.
- Someone sneaking onto a runway and getting struck by a plane that was landing.
- Another person stealing a plane and intentionally crashing it into the ground.
- The Kobe Bryant helicopter crash.
Looking through the list I would conclude the parent comment was correct. The only incidents with passenger fatalities on US airlines since 2009 were Southwest 1380 and PenAir 3296.
If the person on the phone had said “Capone, Al” instead of “Uh…” he’d possibly not gone to jail.
Even ill gotten gains are taxable and the theory of one crime at a time suggests that even “other, unspecified” could be with paying taxes on to reduce the likelyhood of successful criminal persecution.
Nigeria and Ethiopia are both brimming with tech workers that are happy to relocate for money and better prospects. Whether a post-war Russia can offer either remains to be seen.
There are reasons for tools like https://github.com/ixs/kvm-cli. It seems like every operations team built their own version that logs into the web interfaces, downloads the java stuff and then runs it locally...
I was just fiddling around with a SuperMicro X8 IPMI the other day. The X8 IPMI stuff is terrible, e.g. the warning that your Java installation is outdated on opening the website etc.
Turns out, you can actually install X9 IPMI firmware on X8 boards as the platform files are still shipped.
Might be worth checking out, if this improves things for you. It did for me.
Check out https://github.com/devicenull/ipmi_firmware_tools for unpacking (and repacking) the SuperMicro firmware. The developer just merged my patches making it work with some of the X8 boards.
As long as your board is listed in /etc/defaults of the IPMI tree you should be good.
Unrelated to the shortcomings we found that Scrumm with the timeboxing concept did not work for infrastructure teams. You cannot just time box most Infrastructure task and just ship whatever you have when you exceeded your initially planned timeframe.
We came up with Kanban as a way to document progress. The swimming lanes together with a limit on things that can be simultaneously in flight served to mirror reality as an operational team much better than pure Scrum.