Put aside the technology completely. What is the value proposition you are delivering. Base your work around that.— Tim Manning (@design4services) October 3, 2020
✏️ Coding tip: whenever possible, avoid embedding types in variable and function names, specially in statically typed languages.— Mario Cervera (@macerub) October 6, 2020
❌ It is redundant.
❌ It hurts readability.
❌ You must update the name if the type changes.
Which statement reads better? pic.twitter.com/k9reESiXWu
Decisions about what is in the problem frame and what gets excluded are not separate from the “problem” itself. These decisions “set” the problem and crystalize how you will filter and interpret new information moving forward.— Charles Lambdin (@CGLambdin) October 16, 2020
A QC process that's separate from development is an anti-pattern in Agile. QC is integrated into development—in fact, tests are often written before the code is written. The very existence of a separate testing team is a huge red flag.— Allen Holub (@allenholub) October 16, 2020
Totally forgot I made a recording of the talk I did last year, “Fighting Code Rot With Continuous Improvement”.— Gary Fleming (@garyfleming) October 17, 2020
It’s about how you keep systems updated: automatically updating dependencies, keeping docker and VMs updated, all the way through to your teamhttps://t.co/5a5UnF1LBv
The feature I miss most in IDEs is the ability to write well-formatted architectural comments that include diagrams, etc. I'd be happy with markdown support & automatic expansion of image URLs. The best place for the architectural docs, as with all docs, is in the code itself.— Allen Holub (@allenholub) October 18, 2020
Architecture is a living, breathing thing. I don't care much about what an architecture looked like in the past or how it evolved. For actual work, I do need to understand it's current state, and I need to figure out how to incrementally change it to accommodate new requirements.— Allen Holub (@allenholub) October 18, 2020
"If we drive the cost of failure down low enough, we'll do it more often"— Bob Allen (@CuriousAgilist) October 18, 2020
"Wisdom comes from experience. Experience comes from making mistakes. So make lots of mistakes"
Hmm. Lesson there perhaps?
No work is "done" until it's in your customer's hands.— Allen Holub (@allenholub) October 20, 2020
Otherwise, it's just an expense.
To increase that confidence, equip yourself with a good grasp on basics. Don't try to chase the trends. While you're reading on a shiny new lib, two others are being pushed to GitHub. You're better off reading old Kent Beck or Martin Flower books. Or becoming friends with Deming. https://t.co/CvRJmyXHWA— Peter Podgorski ⚡️ ***** *** (@peter_podgorski) October 20, 2020
A kanban board must reflect every step of your actual process from idea to delivery. Most boards I see use some sort of idealized board that doesn't reflect the reality of your actual processes, and is way too abbreviated. 1/4— Allen Holub (@allenholub) October 20, 2020
How Much Autonomy Should Teams get from Their Agile Leader? - https://t.co/Raxv087Eww— Agile4ScrumMasters (@Agile4Scrum) October 20, 2020
The correlation between the estimate and the actual gets lower, the larger the estimate. The only accurate estimates are for work so small that you don't really need to estimate it. Making the work small. Forget the estimate.— Allen Holub (@allenholub) October 21, 2020
✨ I'm building a new mini startup this week— (@levelsio) October 21, 2020
I found a new idea while 🛣 road tripping in 🇵🇹 Portugal
A thread 👇
Change is constant and inevitable.— Stoic Corner | Principles (@stoic_corner) October 21, 2020
Your resistance to change is avoidable and extremely painful
Using value questions with stakeholders to dig down and generate options:— Charles Lambdin (@CGLambdin) October 28, 2020
A: "I want X."
B: "What will X do for you?"
A: "It will give me Y."
B: "And what's important about Y?"
A: "We need something to Z."
B: "What other paths to Z have you considered?"
When #MobProgramming, everybody is engaged. You're all literally working on the same thing, so no coordination is reqd. Communication is constant. The problem of "needing help" goes away. Everybody helps everybody all the time. The collaborative mind creates better solutions. https://t.co/N7zdXBFQr9— Allen Holub (@allenholub) October 30, 2020