@HandstandSam Totally relate and have gotten that request before. Staging as separate commits can sometimes be an ok option for those requests you know (which I always do for the large changes)?? Odds of losing the context across a couple prs are high also.
https://t.co/CwSEQRw6qh
i cant be the first to think 'Cancelling (transient state), completed = false, isCancelled = true' is weak. Feels like we needed an api state of .isCancelling = true, .isCancelled = false
Published my first Rust cargo crate 🦀! It's a simple Text UI for moving between recent git branches, something I've been wanting for my own git workflow. https://t.co/wLO8L78Tob .
Intuition for how to refactor can’t just be read about. subconscious pattern matching is an important element, and the right choice requires applying that intuition to experimentation. - paraphrasing a resonant convo w a colleague about redesigning elaborate code.
@nickblack we might need to tweak the law a bit, "a software which explicitly claims positive qualities in its title will have exactly the opposite quality". "SecureBank" will decidedly be insecure, "easypay" will be "difficultpay", etc.
Skeen's law: A software's behavior will be exactly opposite of its title. For example, the quickplay library should be expected to be slow, and to not actually play.
Really excited about this PR removing 43 suspend functions.
Coroutines are great! BUT.
Wrapping callback based APIs involving serial threads with dispatcher calls to provide suspend APIs is an antipattern that leads to queue based slow downs.
I need to write about this :)
@s1m0nw1 seems pretty miscalibrated doesn't it? text-based comms, this happens way too easily.. put it in the random weird stuff bucket and laugh it off!