I'd bet the kind of people who care about the RAM usage of their media player haven't used Windows Media Player in a decade and disable as much telemetry as they can.
And even if you don't have seasonal products, you still need an end date to mark when you stop selling a product; otherwise you have to do something hacky like defining "<price> = NULL means we stopped selling the product after <valid_from>" and inserting an extra record.
I think the end date should be nullable though, but valid_to is NOT NULL in the starting example... later in the article, when showing the "new way" using date ranges, it inserts a row with an open-ended range, which is more what I'd expect.
Google's whole business is built on top management abandoning its moral compass. Sergey Brin and Larry Page wrote that "advertising funded search engines will be inherently biased towards the advertisers and away from the needs of the consumers". Then they got into advertising anyway.
I enjoy playing video games but I recognize them for what they are: a luxury past-time that is not necessary for life and one that would probably leave most of us better off if they all disappeared tomorrow.
> one that would probably leave most of us better off if they all disappeared tomorrow
I get what you are trying to say, but in general video games offer unique experience that no other media can provide - interactivity, e.g. exploring different worlds with different mechanics. I think this experience can invoke something in people that no other media can replicate. So I think we will lose something important if it suddenly vanishes.
We had a way of measuring velocity, but who cares about estimating stories when we could be spinning up more agents? Burn a bunch of tokens and those stories will be DONE before you could even find your planning poker cards!
I've lived through a bunch of initiatives about improving planning and estimation. None of them turned into a stable process that worked for anyone. I don't know if I can extrapolate from that, but it gives me an inclination that no one really trusts anything that comes out of task estimation. Which would be why we're looking for more objective metrics like token burn rate. No room for argument - tokens are tokens!
A token is approximately word generated by a LLM; a few dozen tokens gets you a line of code... so measuring token burn rate is the same as counting lines of code. All it took was a change of name, and we're back to the most primitive metric we ever got for measuring programmer productivity.
I don't think I can take anything from management in tech seriously again after tokenmaxxing.
They obfuscate it more than just pressing "Yes". You get a big warning saying Microsoft Defender has protected you, and the only clear option is "Don't run"
reply