Amitai Schleier
@schmonz@schmonz.com
https://sw-development-is.social/@emilybache/111176572807433174
Q1. What was happening for (and around) you when you first realized that your code is gonna need to communicate with humans?
Q2. What were your first best ideas for how to make it do that (or how to learn to make it do that)?
What's a #CodingTour, and what did it teach me about making the world safe for programmers (à la @kentbeck )?
How well did solo #OpenSource prepare me to return from parental leave?
- I miss way more than it does
- The music will find you anyway
As is always the case with Medtner, this one is important to me. Let it sing to you as best it can.
https://octodon.social/@schmonz/111172310353422266
https://www.youtube.com/watch?v=JPa-zFg8Q74&list=PLkuryjnRFclTzNyap3TRgLtWxgQmbu5Am&index=49
#PianoMiniature #PianoMiniatures @classicalpiano
What's on your mind? Drop by today's office hours and ask.
https://octodon.social/@schmonz/111131958589273543
What are your favorite ways to get some level of understanding on the current state of your understanding?
#SoftwareDevelopment #EngineeringLeadership #SystemsThinking #CognitiveLoad
https://octodon.social/@schmonz/111165750607585068
What’s the nicest way to find out you’re wrong?
(P.S. Live-coding in 10 minutes at https://www.twitch.tv/schmonzie)
- Devs make 1000s of decisions per day
- Emotions are first-order decision inputs
- Emotions derive from information and can lead us to new information
- Programming faster happens when we remove friction, get stuck less often for less time
https://octodon.social/@schmonz/111162007959878626
Before setting some code back down, first arrange it in the best order you can quickly feel.
When picking some code back up, first arrange it in the best order you can quickly feel.
Growth hacks for the aforementioned productivity hack:
Practice the “feel” part.
Practice the “arrange” part.
Practice the “quickly” part.
Meta-growth hack for the aforementioned growth hacks:
Practice practicing with other people.
Communication hack for the previous hacks:
With other devotees of these hacks, you can just call them #Refactoring, #DeliberatePractice, and #EnsembleProgramming (a.k.a. #MobProgramming).
I don't run exim, but when the universe suggests that it's a good time to inspect my own code, I try to accept.
#SMTP #Refactoring #SecureProgramming #C #dev #qmail
Note the higher-than-usual marginal value of the #refactoring steps. Shell scripting has an especially low comprehensibility floor, so a tiny bit of structure goes a long way.
1. Our intuition exerts tremendous influence over our decision-making,
2. It can lead us astray, and
3. It can be developed."
— @schmonz
https://octodon.social/@schmonz/111148793690174809
Today’s prompt: When developing software, how many decisions do we make every day?
Some starter thoughts: https://agilein3minut.es/4
#SoftwareEngineering #EngineeringLeadership #Agile #Scrum #ExtremeProgramming #XPLives #dev
1. Unstuck
2. A GitHub access token
3. Logged into #ikiwiki
4. Clarity on what's left to do
Watch: https://www.youtube.com/watch?v=dR3BYww45P0&list=PLkuryjnRFclRpPiXrM4oNSY1_RJHMRcYs&index=1
Don't miss the next one (Monday 10am US/Eastern): subscribe https://www.twitch.tv/schmonzie
If I had to bet:
They're the emotional responses of the relevant people.
Cost and risk are used primarily as proxy metrics.
We have to lean on these proxies because we've so thoroughly devalued emotional responses in business contexts.
W pm: I'm a guest on someone's podcast
M & F am: Here's a convo-starter from Agile in 3 Minutes
M 10am & R 1pm: Live-coding at https://www.twitch.tv/schmonzie
T 12:15pm: Open office hours
1. How best to define #LegacyCode? (problem-framing)
2. How best to approach living with it? (solution-finding)
https://legacycoderocks.libsyn.com/defining-legacy-code-with-amitai-schleier
Here’s #Medtner’s response to his publisher requesting something more accessible for amateur pianists (i.e., me): yes, and still 100% himself.
#PianoMiniature #PianoMiniatures @classicalmusic @classicalpiano
Sometimes it is.
"Amitai is AMAZING at bringing a sense of calm and sustainability to software teams! I can't recommend him highly enough and whoever is lucky enough to hire him will be in very good hands. ❤️"
—@andreagoulet
https://octodon.social/@schmonz/111131958589273543
You're in luck! (Wait, what?) That's right, because I'm holding office hours today.
12:15-12:45pm US/Eastern, here: https://us02web.zoom.us/j/89405675221?pwd=WHRueXFFbzZoaUsyTkxFV3hrOWpvQT09
Good ideas. For free.
#XP #Agile #SoftwareEngineering #EngineeringLeadership #ProductDevelopment
https://octodon.social/@schmonz/111126035235742233
It's so perfectly wrong, it undermines the speaker nearly as much as the target.
The last thing we want to get merged before release is your Maildir-uniqueness patch. I'm assuming you're very tired of the git rebasing (etc.) required to get your PR merge-ready, so I'm I'm happy to handle it -- but I'd be happier knowing you're happy having me handle it.
What we've done when merging other patches, and what I'd do here, is define a branch made up of the following:
1. Apply your published patch precisely as is, with git author attributing it to you
2. Add commits (attributed to me) that change whatever we think needs changing to better fit into the notqmail codebase
Then I'd submit a PR for the usual review (which you'd be more than welcome to participate in if you want to, and more than welcome to skip if you don't).
If this sounds okay, can you say so on https://github.com/notqmail/notqmail/pull/90#issuecomment-1731495439 ? Or if it sounds not okay, please do say that.
![[?]](https://schmonz.com/snac/schmonz/s/506a4e5be3c4eba4d0539c833aea957a.jpg)