Amitai Schleier
banner
schmonz.com
Amitai Schleier
@schmonz.com
430 followers 320 following 330 posts
Force multiplier. Outcome improver. Decision sharer. Developer, leader, coach. agilein3minut.es podcaster. Musician. Bad poet (award-winning).
Posts Media Videos Starter Packs
Pinned
Teammate on most recent team gave me this parting feedback: “I learned a ton, we got lots done, our team dynamics were awesome, and I’ve never felt this kind of team feeling before.”

If your business makes software, I might be good for your business.
Did you know I'm looking for my next employer? Here's what's on offer:

1. Technical breadth and depth
2. Proven delivery experience
3. Thoughtful communication and teaching
4. Bridge-building across roles, silos
5. Team culture and developer happiness
6. Respected industry voice
Reposted by Amitai Schleier
Got some slack time? Pick a risk to reduce.

Got no slack time? Defer something, then pick a cost to reduce.

#ContinuousImprovement
#SenderRewritingScheme with #notqmail via #pkgsrc:

echo srs.dom.ain > control/srs_domain
echo "$SECRET" > control/srs_secrets
echo srs.dom.ain >> control/rcpthosts
echo srs.dom.ain:srs >> control/virtualdomains
echo "| srsfilter" > alias/.qmail-srs-default

+ MX for srs.dom.ain
#qmail lacks #TLS. #notqmail doesn't include it either (yet!). But if you install from #pkgsrc

# chown qmaild:nofiles control/servercert.pem
# chmod 640 control/servercert.pem
# ln -s control/servercert.pem control/clientcert.pem
# update_tmprsadh
# /etc/rc.d/qmail restart

🔐
For our next trick with #notqmail from #pkgsrc:

Want to SMTP-reject SPF failures when the source domain specifies explicit-fail?

1. Add SPP_SPF_RESULT_FAIL="E550 spf_smtp_msg" to
control/tcprules/smtp
2. Run "/etc/rc.d/qmailsmtpd cdb"
3. There is no 3rd thing, is that clear?
Another neat trick with #notqmail from #pkgsrc:

The default SMTP configuration rejects nonexistent recipients.

(qmail famously accepts all recipients for its domains even when those recipients don't exist, and then has to queue totally avoidable bounce messages. But you won't.)
Another #notqmail from #pkgsrc trick:

To enable #greylisting, simply uncomment "greylisting-spp-wrapper" in control/smtpplugins. That’s it.

(Add any exempt recipient addresses to control/greylist/exemptrcpts, or entire recipient domains to control/greylist/exemptrcpthosts.)
Running #notqmail via qmail-run from #pkgsrc? Cool. Add #DKIM signing like so, then publish a TXT record with your `default` policy. Done!
Most practical experts don’t write a book. Distinct tasks, incentives, skills.

For the same reasons, some published authors are better at describing than at enacting.

Maybe an author really knows, in context, under stress, how to *do* the thing. Maybe not.

#ExtremeProgramming
Reposted by Amitai Schleier
Unfortunately, even if the person following these steps loves #ExtremeProgramming (and is widely held to be expert in it), they’re no less destructive.
Hate #ExtremeProgramming and want others to hate it?

1. Become Director of Engineering

2. Tell org and stakeholders that XP will fix longstanding problems

3. Regularly interfere with devs’ learning

4. Design projects to delay ROI

5. Find scapegoats

Maybe they’ll blame #XP.
Unfortunately, even if the person following these steps loves #ExtremeProgramming (and is widely held to be expert in it), they’re no less destructive.
Hate #ExtremeProgramming and want others to hate it?

1. Become Director of Engineering

2. Tell org and stakeholders that XP will fix longstanding problems

3. Regularly interfere with devs’ learning

4. Design projects to delay ROI

5. Find scapegoats

Maybe they’ll blame #XP.
Hate #ExtremeProgramming and want others to hate it?

1. Become Director of Engineering

2. Tell org and stakeholders that XP will fix longstanding problems

3. Regularly interfere with devs’ learning

4. Design projects to delay ROI

5. Find scapegoats

Maybe they’ll blame #XP.
Also: not a success, at least not in his eyes. I've had a much easier time making appreciable progress when working with folks in power positions who don't imagine themselves to be XP experts.
It ended a while back. The guy is still periodically hiring for job descriptions featuring #ExtremeProgramming, cashing in on his reputation in this niche. After plenty of time to decompress, I continue to feel the need to warn folks as best I can.
Ha. I wonder what the audience for that might be. My most recent talk (which was also the first in quite a while) was sort of in the same vein: schmonz.com/2024/05/10/n...
NYC Large Scale Scrum May 2024: Not So Extreme Programming
schmonz.com
Demoralizing, too. Had me (and not only me) questioning my competence and perceptions. And the guy is still hiring.
If you love #ExtremeProgramming and you see a rare opportunity to be hired specifically for that, you might jump at the chance. I do. I did.

Maybe in your case it’ll be what it sounds like. I hope so. But beware.
If the only code you’re ever satisfied with is your own, you’re not qualified for #TechnicalLeadership. Especially if you’re sure you are.

If the only bits of #ExtremeProgramming you’ve mastered are the technical ones, you’re not an XP expert. Especially if you’re sure you are.
If the only code you’re ever satisfied with is your own, you’re not qualified for #TechnicalLeadership. Especially if you’re sure you are.

If the only bits of #ExtremeProgramming you’ve mastered are the technical ones, you’re not an XP expert. Especially if you’re sure you are.
If you think #ExtremeProgramming coaches have to “know the most” or “be the most technical”, you might not understand coaching, influence, or your own technique-acquisition process.

If you’re still sure of your understanding, regardless of cost to you and others… clownshoes.
🤡👞
If you repeatedly fail to perceive or appreciate what reputable #ExtremeProgramming coaches are accomplishing in your org, maybe you’re a great leader who doesn’t know yet what specifically to look for.

If you do this while claiming to be an #XP expert, that’s clownshoes.
If you repeatedly fail to perceive or appreciate what reputable #ExtremeProgramming coaches are accomplishing in your org, maybe you’re a great leader who doesn’t know yet what specifically to look for.

If you do this while claiming to be an #XP expert, that’s clownshoes.
Fascinating 1:1 feedback: “I hired you largely on the strength of recommendations from our shared network. But maybe that was just a mutual admiration society.”

What does this feedback reveal about the giver? Would you expect them to be a skilled leader or manager?
“We learned a ton, we got lots done, our team dynamics were awesome, and I’ve never felt this kind of team feeling before.”

Leaders are not obligated to value such feedback.

But if they don’t, they oughtn’t claim to value #ExtremeProgramming. They value something incompatible.
If you believe the remit of an expert is to (1) know what’s best and (2) push everyone through doing it, you might not understand expertise. #KnowledgeWork #EngineeringLeadership