Kinrany

21 ms·

361.
by Kinrany 2y ago
Beautiful, thank you!
362.
by Kinrany 2y ago
The holy grail of a stacked diff workflow would be making multiple Github PRs each made against the previous branch instead of trunk, and then updating the branch that's closest to trunk and rebasing all of the children PRs without hav
363.
by Kinrany 2y ago
That's fair: even if their team has a problem with PR size, this doesn't have all that much to do with the pattern the article describes.
364.
by Kinrany 2y ago
I thought that at first, but the article literally says "getting their big PR out".
365.
by Kinrany 2y ago
Thanks for the name!
366.
by Kinrany 2y ago
You're not addressing the issue of triage also being an interruption.
367.
by Kinrany 2y ago
It's a common and pervasive mistake to assume the meaning of a term by association with the words used in the term. Names of terms are at best mnemonics.
368.
by Kinrany 2y ago
By "constantly", do you mean for 2-4 weeks in a row?
369.
by Kinrany 2y ago
Do you have a name for this practice?
370.
by Kinrany 2y ago
It's a team of 4, so the only options are 25% and 50%. But the fact that this explicit split makes the choice visible is clearly an upside.
371.
by Kinrany 2y ago
The title reminded me of this article, that claims that the new culture war is weird vs normal: https://studio.ribbonfarm.com/p/the-new-systems-of-survival
372.
by Kinrany 2y ago
There should be a unified theory that all auth can be stacked on top of. Like, a theory of secure communication, that deals with the problem of adding security/reliability/etc. properties to a communication channel.
373.
by Kinrany 2y ago
Thr current Scrum guide also defines two separate backlogs: sprint and product.
374.
by Kinrany 2y ago
> Most software businesses don’t need a bunch of Picassos, they need house painters with spray guns and buckets of off-white. This doesn't add anything to the rest of the comment, does it? It insults the developers with the implicat
375.
by Kinrany 2y ago
There's little to disagree with here, and yet this comment reads like a slogan soup.
376.
J8 Notation – Fixing the JSON-Unix Mismatch(oilshell.org)
2 points by Kinrany 2y ago|0 comments
377.
by Kinrany 2y ago
I have the experience of reading an ffmpeg one-liner (that really took more like five lines with wraparound) and trying to understand it. Half the options seemed unnecessary, but every single one of them would break the script when removed.
378.
by Kinrany 2y ago
I thought this was about BlueSky using NATS!
379.
by Kinrany 2y ago
If someone will pay for the solution, the problem may still be utterly unimportant. So this tells us nothing.
380.
by Kinrany 2y ago
Any examples? Searching for this is hard. What would `foo | bar | baz` look like in a lisp?
381.
by Kinrany 2y ago
Process composition is one thing that shell languages do better than traditional programming languages
382.
by Kinrany 2y ago
I wish Rust had a good dependency injection library. More specifically, a library that solves the problem of having long chains of constructors calling each other. The two main use cases are routing frameworks and tests. Axum already has th
383.
by Kinrany 2y ago
> Much of the time your API is more or less a wrapper around the DB, so why introduce more indirection? That's an easy scenario. General utilities should aim to make hard things possible and then minimize the overhead in easy scenar
384.
by Kinrany 2y ago
> There's actually another (better IMO) solution to this problem Is it standardized?
385.
by Kinrany 2y ago
Agree. Except, to be very pedantic, with this? > then you've basically just succumbed to Goodhart's Law We're talking about adding more metrics that should be considered, and treating or not treating them as the ultimate g
386.
by Kinrany 2y ago
This is not true in practice because the consequences of bad code show up months and years later and in a way that makes it impossible to attribute to any one business decision.
387.
by Kinrany 2y ago
Do they have an article that explains their approach? I couldn't get through the marketing-speak.
388.
by Kinrany 2y ago
A blog post explaining these two common approaches would solve the same problem though
389.
by Kinrany 2y ago
The first two are product quality, not code quality
390.
by Kinrany 2y ago
And yet: https://xkcd.com/2347/

More ›