The Most Authentic Thing about us is Our Capacity to CREATE, to OVERCOME, to ENDURE, to TRANSFORM, to LOVE, and to be Greater than our Suffering. ~Ben Okri https://t.co/dgZ8kQC2nW
#osschallenge
Software is a brutal business that chews people up and spits them out broken, but it doesn't always have to be.
Tell 3 library creators that you appreciate them and their work. Then, post that you've done so and ask others to do the same. It makes a difference.
The psychology of fighting Zoom fatigue:
(1) Increase mobility: give permission to walk around
(2) Reduce eye contact intensity: sit farther away
(3) Reduce mental load: hold audio-only sessions
(4) Reduce self-consciousness: turn off the self-view
https://t.co/NXGQn9Sf08
Best reason I’ve heard for serverless. If there are servers but I don’t have to know anything about them, win.
Now if only I didn’t have to know about IAM, SQS, CloudWatch, Terraform... https://t.co/DKnOOZHBgk
@IanColdwater that's crazy, my 6 month old just said this morning, "the problem with kubernetes specifically and devops generally is that it represents a broadening of the technical skills required to build an application. in the long run devops will inevitably lose to serverless"
And, for software engineers, an analogy to consider is in-band signaling in user plane protocols; much more efficient than control plane signaling up and down the protocol stack 🙃 https://t.co/hdtU2P9ogB
A simplified explanation of kanban systems.
"The basic idea is simple: If you work in a step in a process, you probably know better than anyone else when you need more material to work on, so why not put you in control?"
From the book I am working on.
#kanban#lean#agilehttps://t.co/P840XAY0df
occurred to me that some crazy high % of the management/leadership training industrial complex is targeted at pathological and/or bureaucratic organizations.
(there's way less focused on generative and/or the transition from bureaucratic to generative) https://t.co/paSp3OyB1J
There’s a very different approach to each of those. And very different outcomes.
One will give you cost savings, the other will help defend against competitors and grow your business.
Knowing where we are all going is key to undertaking any big product transformation. /end
They want to be more strategic with their software, but they are worried. “We can’t just stop serving our business needs to build something radically different!” No one said you had to, hence a portfolio approach to building horizon 1-3 products. /8
While that’s a fine way to optimize your tech teams, it’s not a true transformation.
The reason older enterprises get disrupted is because they don’t see software as a strategic lever to further or disrupt their business model. /7
So I ask them “if you really want to transform, how is this transformation going to disrupt your business?”
They’ll look confused. But we’re just making a new product portfolio? We’re streamlining. We are making things better for our business customers. /6
When I work with leadership to understand the outcomes of the product transformation I hear:
- streamline our products
- stop being reactive
- Lower cost of ownership
- better prioritization
Everything is cost related because IT is seen as a cost center. /5
In the advance of ideas and understanding one should always respect the insights of the past; but that does not require you to be bound by them. Understanding that something exists is not the same as understanding why and how it works
Polling and weighting: A quick thread.
One of the common criticisms levied at polls is "They only asked 1,000 people, how can that mean anything?"
Simply - So long as that sample is representative of the whole population, it can, within a known margin of error.
@shamziman@themapirati@jamesurquhart Which is why we often use maps to find a common understanding of the landscape, to consider the complexity and uncertainty within it, to identify possible options and then after much thought (or many calculations as Sun Tzu would say) then we convert them into stories for some.