People who code for a living: how much of the code you've written in your career has ended up getting thrown away before anyone used it?
(Boost for reach, if you'd be so kind)
@cstross @mrintergalactickeyboard @lauren @vvandinsky yes the 10” was much more practical. (You remind me about the tail end of that subsequent ultrabook era, the Samsung “ultrabook” fridge). I saw a GPT pocket 3 last FOSDEM and it was highly desirable!
@mu yeah for papers I think printing and scribbling are still best for me too. Remarkable2 too small to comfortably do that for traditional journal layouts. Where it shined for me was reviewing my own thesis chapters, over and over
The Remarkable2 was incredibly useful whilst I was doing my PhD. Now I don’t really need it. So of course I’m looking at the remarkable pro…
tfw researching a topic you turn up a question you asked and have forgotten about for 15 years… https://exim-users.exim.narkive.com/BSnc11jb/smtp-time-spam-filtering-with-crm114-best-approach
@aeva I’d love your opinion on JACK. Signed: embarrassed, who has yet to get his synth to be audible from his Linux machine
Sigh, Prusa Mini failed to print a simple trapezoid. I'm having a lot of failures since input shaping was added. #3dprinting
Free Software needs to get better at, and less scared of, doing politics. Blog post, by me.
Just cut a new IkiWiki release. Hopefully I didn’t break anything. This is intended for Debian Trixie
@pndc it’s the bounce that concerns me. I could live with spooled retries. From the docs I think it might depend on the return code
@pndc i do! But as I understand it’s “pipe” command, I’m concerned about the behaviour if the command fails
@mcc I’m out of touch on current fashions, but my last project used stack and it solves a couple of the issues you’ve hit so far