Skip to main content
  1. Mastodons/

Mastodon - 2024-04-04

·348 words·2 mins
Matt Weagle
Author
Matt Weagle

Toots from 2024-04-04
#

“1. Understand the real-world problem. 2. Analyze it from a software point of view. 3. Imagin…
#

“1. Understand the real-world problem.

  1. Analyze it from a software point of view.

  2. Imagine a solution.

  3. Align a team on the problem, the solution, and the values that shape the solution.

  4. Coordinate to express that understanding in code.

  5. Get feedback and iterate.

  6. SHIP IT.”

https://blog.ceejbot.com/posts/understanding-software/

Mastodon Source 🐘
#

“This work became a regular fixture in Jade’s schedule. So much so that he learned a peculiar…
#

“This work became a regular fixture in Jade’s schedule. So much so that he learned a peculiar thing.

Leaders surrounding these affected teams thought they knew what the problems were. But the actual problems that Jade uncovered were nothing like what the leaders told him.”

https://www.srepath.com/danger-of-unreliable-platform-engineering/

Mastodon Source 🐘
#

“If you read the story, it becomes obvious that the key vulnerability wasn’t technical, it wa…
#

“If you read the story, it becomes obvious that the key vulnerability wasn’t technical, it was the fact that a whole lot of Open-Source software is on the undermaintained-to-neglected axis, because there’s no business case for paying people to take care of it. Which is a problem, because there is a strong business case for paying people to attack it.“

https://www.tbray.org/ongoing/When/202x/2024/04/01/OSQI

Mastodon Source 🐘
#

Rereading Chapter 1 of <https://www.amazon.com/How-Infrastructure-Works-Inside-Systems-ebook/dp/B…
#

Rereading Chapter 1 of https://www.amazon.com/How-Infrastructure-Works-Inside-Systems-ebook/dp/B0BV1LSLCH for tomorrow’s Paper’s in Systems conversation (https://ti.to/bredemeyer/howinfrastructureworks - signup, it’s a great group! Thx to @RuthMalan for setting it up). ..

Mastodon Source 🐘
#

Anyways, this reminded me of the XZ exploit, the problem of measuring platform team impact, allocating sustaining engineering, ops work being relegated to junior team members, and the allure of One More Feature.

“Infrastructural systems are famously boring because the best possible outcome is nothing happening, or at least nothing unexpected or untoward. But nothing happens, and nothing continues to happen, as a result of sufficient attention, specialized care, and unceasing oversight.”

Mastodon Source 🐘
#

Channeling Erik Hollnagel : “What’s happening when nothing (bad) is happening?”

https://www.hqsc.govt.nz/assets/Our-work/System-safety/Resilient-healthcare/Publications-resources/Delivering-resilient-health-care-Dec-2018.pdf

Mastodon Source 🐘
#