Amitai Schleier
@schmonz@schmonz.com
@schmonz It was great to catch up with you on Monday :) Maybe we can meet in person if you’re ever back in Europe.
When I was a consultant, I chose to get rusty with technologies rather than with team skills — and I'd choose the same a million more times.
@schmonz Why are you presenting it as an either/or choice? I work alone most of the time (which means I'm not practicing team skills) and I still manage to get rusty with technologies too!
I have a "theory" :)
The announcement is for #pkgsrc source code. It takes about 2 or 3 weeks for things to replicate and binaries to be built.
Hmm... You do know pkgsrc is "download source and compile", right?
@ParadeGrotesque
Yes. but it also has a binary component with pkgin
@schmonz
New account on your own server?
(Before that, I was nervous I wouldn't get it done before the old instance goes offline in a few days: https://octodon.social/@CobaltVelvet/112897672123037837)
@schmonz
Ahh, self hosting: the joy of knowing you can set things up the way you want; the drudgery of knowing you have to set things up the way you want. 🥹
I've moved to @schmonz@schmonz.com. Follow me there if you're not already automatically doing so.
@schmonz@octodon.social. Follow me here if you're not already automatically doing so.We usually assume it also means you know how to do X. Often true, but not always.
But don't sleep on how it also makes you likely more amenable to the next needed refactoring.
Projects that by design cannot promptly demonstrate return (or no return) on investment are extra risky.
Saying these things out loud does not suffice to indemnify us, or me.
When negative feedback that’s vague and unactionable comes from someone with power-over, it’s negligent, irresponsible, and destructive.
In the same message: "Is this a bug in acceptutils or did I make a configuration mistake?" A bug, and now I'm freshly motivated to fix!
When designing a project, do you always prioritize closing the feedback loop of ROI (or lack thereof) as early as possible?
Might you ever choose to defer closing that loop because you need something else sooner? If so, what kind of something could that be?
(1) Collective ownership and incremental shared learning over the absolute quality of today’s code
or
(2) The other way around
or
(3) Both, somehow
?
I imagine there are workplaces wishing for this. But first, more time for more reflection.
Last time I saw @Soulcraftswoman was only slightly less long ago. Any minute now!
einfach = simple
vielfach = complicated
nullfach = impossible
(It’s foundational to my coaching practice that I not be the expert. As usual, working as intended.)
On the other hand (the hand I often manage to continue on to), I was able to make the trip, am already booked for the next one, and can easily imagine it’ll go better.
1. Not your code, but can break your code
2. Will one day dictate your schedule
3. Will own you more superlinearly the more you defer dealing with it
