Amitai Schleier
@schmonz@schmonz.com
If your business makes software, I might be good for your business.
- See and fix any remaining ones
- Recompose parts to add functionality
- Adjust to meet people's real needs
Messy code is a competitive disadvantage. #refactoring
If not, oops, we fix it.
If yes, we can ask more of it.
I hadn't been aiming that far ahead; I'd been looking for a foothold to climb out of a persistent hole.
A bit more about that: https://www.linkedin.com/posts/jack-hannah_by-default-i-wasnt-effective-in-a-business-activity-7221620343000477696-3jI8
(For long-winded personal reasons I run and develop @notqmail instead of using Postfix. https://schmonz.com/2017/03/27/automation-for-mail-hosting/ says more in terms that might appeal to your XP feelings, but I cannot yet honestly recommend notqmail to folks who aren't already running qmail. Someday.)
(Developers at every level can be thinking about how well the two are correlated. A good way to acquire seasoning.)
@schmonz @logosity Klein’s /Sources of Power: How People Make Decisions/ is good on expert decision-making. “When it feels good” can be a symptom of tacit knowledge being put to use.
https://www.goodreads.com/book/show/65229.Sources_of_Power
Building up such tacit knowledge takes time.
1. It feels good
2. It invests company money wisely
When I get carried away with #refactoring, they both turn false. Same when I haven’t been doing nearly enough of it.
Upon our return there today I made sure to say it.
*by age, size, and frequency and obviousness of communications with other dimensions
Now, instead of
$ nb boot ubuntu 24 arm64
I can just type
$ nb boot ubuntu
to bring up the latest version matching the host's arch.
https://github.com/schmonz/nbvm/commit/a1a3a363552f24549e458ecad203d40af75cb4b1
When we trust ourselves later, we can do less now.
When we do less now, later gets easier.
Given a completed test run
When it included all possible tests in the project
And all of them ran green
Then a particular file’s timestamp gets updated
Easy peasy! Let’s teach every test framework to do this.
If you run #JUnit 5 tests on pre-commit, here’s your bonus: https://schmonz.com/software/greencently
(Pays off on day 1.)
For other frameworks, help wanted! #tdd #xp
(Something short and sweet and stepwise, akin to #TDD's "Red, Green, Refactor", would be amazing.)
Expect to learn more, plan a little less.
An even older USB printer staying useful.
https://schmonz.com/2024/06/07/small-arms/
https://octodon.social/@schmonz/112434238894485284
Claim 1: Compared with other ways to try to ensure ROI, #XP is hardly extreme at all.
Claim 2: XP is therefore for everyone involved with software teams.
"Not So #ExtremeProgramming": https://schmonz.com/2024/05/10/nyc-large-scale-scrum-may-2024-not-so-extreme-programming/
How: Give us good choices to make
How:
- Risk intentionality + cost control
- Situational awareness
- Predictability (in some actually useful way)
- Conserve "surprise!" budget for market discoveries
Slides + Video: https://schmonz.com/2024/05/10/nyc-large-scale-scrum-may-2024-not-so-extreme-programming/
It's for anyone who cares about software investments yielding returns.
It's called "Not So #ExtremeProgramming":
https://youtu.be/dqABaoybMM8?si=sS3MIBiI-lkXhutZ
#XP #XPLives #Agile #Scrum #LeSSIsMore
(Including that you feel safe to do so. So if you don't… don't.)
notqmail 1.09 is here: https://schmonz.com/2024/05/07/notqmail-109-released/
#qmail #notqmail #smtp #OpenSource
When you've felt it, what are some of the factors that made it possible?
When it's been out of reach, what were some of the obstacles?
#XPLives #ExtremeProgramming #dev
https://mastodon.social/@christianhujer/112383270758236826
My first public talk in years: https://schmonz.com/talk/2024-lessnyc-may/
#SoftwareDevelopment #Coaching