Amitai Schleier
@schmonz@schmonz.com
https://www.youtube.com/watch?v=eahdJBWS6_k&list=PLkuryjnRFclTzNyap3TRgLtWxgQmbu5Am&index=21
$ xq '.project.component[] | select(.["@name"] == "TestHistory") | .["history-entry"][]["@file"]'
But it doesn’t update anywhere near real time. Also I couldn’t see how to deduce green or not from the results.
Might just have to write my first IntelliJ plugin.
I want: a pre-commit hook that runs the tests if and only if they haven’t been run greenly in IntelliJ within the last minute.
I need: how to interrogate IntelliJ for this information.
Ideas? Anyone already done this?
- "Open the baby box" opens the glove box
- "Open the poop baby" opens the charge port
- "Do auto-steer to baby" sets climate control to auto
- "Turn on honk" sets air to recirculate
1. Try to learn something bigger well enough in time
2. If it’s time and it’s not ready, learn another Mordasov miniature on the spot
As compensation, I’ve had my entire adult life to appreciate music that was designed to be appreciated for a lifetime.
#medtner #classicalmusic #pianomusic #romanticism @classicalmusic
- time for actual lazy cuddling on the couch with my one and only (this got rare somehow)
- a passel of sick kids managing to still be mostly sweet and funny
- homemade cards and not-cake
- nonzero piano minutes
- feeling familiar (and long-lost) efficacy at work
#pianominiature #pianominiatures #jazz
mob.sh handles a temporary branch in a particular repo. That suffices when all the code being worked on is in that repo. What about when it’s not? Say, for a simple case, when we’re making changes to a REST endpoint and a consumer of it. How do?
For everyone to pass around every potentially involved repo on every handoff without effort, my best idea so far is to use myrepos with this .mrconfig:
[DEFAULT]
git_mob1 = echo MOB_WIP_BRANCH_QUALIFIER="mob1" "$@"
git_mob2 = echo MOB_WIP_BRANCH_QUALIFIER="mob2" "$@"
Then you can say mr mob1 start 25
or mr mob1 next
and it'll run on all repos in rapid succession. All done? mr mob1 done
followed by mr status
to see which repos actually need us to compose a commit message.
So those are my best ideas so far to adapt http://mob.sh to this situation. What else could we try?
When two ensembles are using mob.sh on the same repo, they’ll trample on each other’s work without meaning to. MOB_WIP_BRANCH_QUALIFIER looks like (if everyone sets it correctly) the two sessions will each have a distinct working branch.
For everyone to set it correctly every time, my best idea so far is for everyone’s .profile:
MOB_PROG=$(command -v mob)
mob() {
echo >&2 "nope, run mob1 or mob2"
}
mob1() {
MOB_WIP_BRANCH_QUALIFIER="mob1" ${MOB_PROG}
}
mob2() {
MOB_WIP_BRANCH_QUALIFIER="mob2" ${MOB_PROG}
}
Then nobody can run mob
, they have to run the one for the session they’re in (and we always know this). And nobody has to remember anything else.
1. Two simultaneous sessions on the same repo
2. Each session involving multiple repos
MOB_WIP_BRANCH_QUALIFIER and https://myrepos.branchable.com are my ideas. What are yours, please?
#MobProgramming #EnsembleProgramming
Here’s a quickie #weeklypiano, the second of Mordasov’s 30 Jazz Miniatures. https://youtu.be/Pzgql21X738
#pianominiature #pianominiatures #mordasov #jazz #pianosolo #solopiano #pianomusic
#pianominiature #pianominiatures #classicalpiano #pianomusic #pianosolo #romanticism #medtner #skazka #skazki #maerchen
#pianominiatures #pianosolo #pianomusic #classicalpiano #classicalmusic #romanticism
https://octodon.social/@schmonz/109535028897721263