The #OpenAI soap-opera hijacked the attention of millions of productive people and nonsensually crammed the fine details of the debate between #EffectiveAltruism and #EffectiveAccelerationism into them, a genuinely absurd debate that was allegedly at the center of the drama.
1/
Through random probability, you will always find statistically significant correlations in any large dataset. Doesn't mean the correlation represents anything other than you went looking for one.
Today, we're releasing "Patterns of Systems Renewal", a white paper introducing a set of patterns and activities that support the process of rapidly understanding a system and making it workable over time.
https://t.co/h585QUJDfv
Feedback welcome as we elaborate this topic.
Huge shout out to the US Government Accountability Office and my buddy SCRUM BOB @AgileInfusion and the team that put this awesome AGILE GUIDE together! You really should check it out. It has some answers to a lot of problems som…https://t.co/rD1rbCEXCz https://t.co/XYp0G12Nq2
Over the last 9 months we’ve deleted close to 80% of the marketing footprint off https://t.co/eBb3igwTKa.
Tens of thousands of pages.
The result is that traffic, conversion and all our experience and NPS metrics are up.
It was a gross project but I’ll tell you about it.
ChatGPT is said to be statistical with, say, a ~95% accuracy.
That's NOT how experts function, only academics, or, worse, students.
An expert who DOES things, (#SkinInTheGame) & that's definition of expertise, KNOWS where to limit his or her error rate or have an ASYMMETRY by overshooting in a GIVEN direction.
Engineers will NEVER make a mistake of underestimation for the strength or material; pilots will never accept a mistake on landing, etc.
This instinct in finding asymmetry is obtained by survival & practice & is difficult to express explicitly, which is why academics almost always blow up in finance.
NEW POST: Many software teams pack too much work into their iterations. Teams will usually run better when they have deliberate slack, as it allows their delivery to be more predictable and gives them time to improve their environment.
https://t.co/YW7NtxVVt2
How did we let so many people believe that "waiter" is the appropriate role for a SW Dev to play?
2023 - time to reclaim professional responsibility and respect?
https://t.co/WAt6i8hwCv
Remote Pair Programming Good Practices: A Thread.
Found the slides of a presentation that @qcoding and I gave to the entire CTO Org at Amex two years ago when we were both there.
Thought it had a lot of great stuff that could still be useful to others.
Why not share?
🧵
I posted a few of Deming's "14 points" (from "Out of the Crisis"; 1982) the other day. Pretty much all of these are relevant today in every software organization. Let's look at the whole list 👇 1/18
Them: "We never have enough time to do proper user interviews."
Me: "How much time do you have?"
Them: "a week."
Me: "Let me tell you a story..."
And the story, #UX and #design friends, goes like this:
(1/11)
I wrote a long and rambling post on why the hierarchy is bullshit (and bad for business). Includes digressions on
* the big lie of hierarchy (higher is always better)
* why hierarchy endures as a data structure
* why it sucks (we imbue it with dominance)
https://t.co/wsR3kXW1Jn