I am increasingly convinced that Starhip will never leave earth orbit. Whatever its owner believes.
OTOH if SpaceX manages to make it work as designed for orbital launches it will fundementally change the economics of space and enable many cool future projects.
This week's major project is splitting the tractor, to replace the failed oil seal which is leaking oil from the gearbox into the clutch housing. We've got to the point where the only thing still holding the front half of the tractor to the rear is the steering linkage, and I can't remember how we split that last time!
It feels that stream-aligned teams and the fluid teams is a big conflict? And I'm wondering what kind of tradeoffs you've found when working with one or the other?
For example, how do devs build deep domain expertise in fluid teams?
Or if you do TeamToplogies, does it always mean that you might need to rework your architecture so teams can work on value and not just on individual components?
While I think you may have a point with LeSS. They have long lived 7-10 person stable teams that are expected to be "fungible" but I think that you are discounting the various rapid reteaming processes within a FAST collective.
TBH it feels like a replay, at team level, the C2 wiki falling out between Coplien and the XP crowd over code ownership.
I'm not saying you are wrong in that it might not work. But I think code ownership is addressed at a different level.
One third of local councils are cutting support to the #Arts, one third are cutting support for parks & leisure... and a wide range of other service reductions or halts are expected.
The progressive destruction of local #democracy, accountability & social provision is now accelerating...
The hollowing out of our local government & the ever increasing centralisation of power & responsibility is unlikely to be reversed by the next Govt.
The value of municipal governance has been completely lost
Not a fan of the Victorians but they understood the power of properly funded local government - just look at the water and sewage projects undertaken by municipal authorities in this period.
In a work context did the trainer suggest an approach for the situation where your co-worker is, from your PoV, making a mistake? Is feels like pointing out your understanding of the situation and why you think they are having/about to have trouble would work. That way you can understand their PoV and either realise your or their understanding of the situation is wrong.
"The private sector is where all the innovation happens", he posted using a protocol developed at CERN built on top of communications technology developed by ARPA, on a device powered by technology created for the US Air Force and NASA in the 1960s.
This passage from @debcha's "How Infrastructure works" is such a truth that often gets forgotten or ignored on the hunt for profit. It's a very familiar and recurring theme in resilience engineering texts and research. And it also rings true for me in this current trend of continuous layoffs that take more and more slack and capacity out of tech systems being maintained (in addition to the human cost) as remaining humans need to do more work in the same amount of time.
All modern human-technical systems (i.e. ALL our systems) operate in failure mode except in extremely unusual "average" conditions and they ALL then require heroic human efforts to recover (or operate at all) when conditions deviate from average.
Okay, people. I need a phrase that is kinda the opposite of "Land and Expand" that big consultancies do. We want to emphasize coaching, building capability within the customer organization, acting as a TT Enabling team, etc. Sort of "consulting done right".
(We came up with "Coach and Poach" but obvs that is not exactly a good way of working! 🤣)