yes. TLA and XTLA overloading is a real problem, particularly when going cross domain.
Maybe we should insist on some standardised expansion of TLAs and XTLAs so you know unambiguously what any particular Three Letter Acronym or eXtended Three Letter Acronym means. I wish I could think of a way of doing that...
Thank you for posting this. I thought I knew a bit about what was going on with audio sampling and reproduction, but I learned a surprising amount from this well presented introduction
until quite recently I dealt with a machine that had uptime in excess of 16,000 days. Before anyone panics, it was on a closed network. It was a second hand machine and we were very worried that if it was shut down the disk wouldn't recover, hence just not touching it. It was in a hut in the back of beyond so exceedingly tedious to replace if we needed to.
and the comment there about using emacs for the different shells in different modes possibly explains the un-resolved nit in TFA about proportional and monospaced fonts in different areas
I think it's more like the old adage 'the first 50% of the job takes the first 90% of the time, and the other 50% of the job takes the other 90%'.
Except that with vibe-coded AI stuff it's more like there's yet another 50% of the job to deal with the edge cases that takes yet another 90% of the time
That wouldn't work (for me, at least). As soon as I figured out the pattern, I'd know I had a week after the 'deadline' and then the pressure is off until that week is passed/nearly up
And then there's trucks flashing an indicator to say it's safe to overtake if you're behind them. In the UK it's the nearside indicator, which makes sense: it's a bit like the truck is pulling over to let you pass. In Aotearo, it's often the off-side indicator, so you think the truck is going to pull out in front of you. I've never understood what the Aotearoa drivers are thinking there
All. The. Time. And I hate it. Imagine giving a customer a rebate based on buggy code. You fix a bug, the customer comes back and wants to check that the rebate was correct that last time. Now you have to somehow hard-code the rebate they did get so that your (slightly less buggy) code gives the same result. But hard-coding has the risk of introducing other errors on its own. Oh yes, and you've never enough time to do things properly because Customers (or maybe Management). A tangled mess of soul destroying lifeblood-sucking code and pressures ensues.