Amitai Schleier
@schmonz@schmonz.com
If your business makes software, I might be good for your business.
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.)
\# 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
🔐
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
If there is one thing I could pass along to folk:
Your career will outlive every bad decision that someone in upper management will make. Your role is to learn what you can, not just the task or tech, but what to watch out for next time. Help the folk who will get caught up in the next bad decision, because they will help when you get hit.
And if you are in the position to make bad decisions, have a failure plan that protects your team. It’s easy to get someone to follow you once.
Getting them to follow you the second time makes you a leader.
You should know #pkgsrc 2025Q3 was released yesterday:
https://mail-index.netbsd.org/pkgsrc-users/2025/09/25/msg042016.html
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.
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.
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.
@schmonz I am almost never satisfied with neither "my", nor "others'" code. That's why I insist on the code to be maintained relentlessly (TDD, refactoring and CI above all) and that's what I expect from others. Because currently most of the others act as if the code they write is perfect (the write once mentality and the notion that the code can be "done" which it never is).
Lastly, there should be no such thing as my and your code.
I appreciate the reminder to consider systemic factors that push people to make such choices. The systemic factors suck. But also people who make any part of others' lives miserable suck.
Maybe in your case it’ll be what it sounds like. I hope so. But beware. https://schmonz.com/snac/schmonz/p/1757721641.814818
If you’re still sure of your understanding, regardless of cost to you and others… clownshoes.
If you do this while claiming to be an #XP expert, that’s clownshoes.
What does this feedback reveal about the giver? Would you expect them to be a skilled leader or manager?
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 influential developers of the highest caliber keep not meeting your expectations, you have much more to learn about #EngineeringLeadership.
Not all “XP” jobs, authors, experts, or leaders are what they claim. Before applying, ask around your network.
History