aes

I worked on exactly this for a while, a long, long time ago. It turns out to be an annoyingly difficult bag of problems. The record companies don’t really care, they sell (sold, I guess) pieces of plastic. (Idk if they fixed it yet, but the same Turbonegro album kept getting sent with the same scratches, kept getting taken down a while later, for years.) So, good luck trusting them to label anything.

Puritans are so much more aggressive than sane people that making mistakes one way is much more expensive than the other way.

Anyway, we ended up trying to work out which tracks are actually the same song, (Easy for you, harder for friend computer, yes?) and then if one of them is marked explicit, they all are, unless marked “radio edit” or “clean”, or whatever. If you think about this for a minute, if one track is labeled “radio edit”, maybe the other ones should be marked explicit…

It’s a deep rabbit hole, is what I’m saying.

And the people with the pitchforks are never happy.

Ok, so it’s to hear from people building stuff, but isn’t it maybe a little light on details? I feel the consultancy contact details to profound insights ratio is a bit underwhelming.

Yeah, but we’re just not incentivizing him enough, right? If we just give his publishers more help enforcing their rights on the English language, he’ll write some more, for sure

Ok, TIL there’s a thing called Required, but otherwise, one way to do this is to rename the other part/field/key(s), so that old code reveals itself in much the same way as using a deleted field (because it does, actually)

Another way is explicitly have a separate type for records with/without the feature. (if one is a strict subset, you can have a downgrade/slice method on the more capable class.

Lastly, I would say that you need static typing, testing, both. People from static-land get vertigo without types, and it does give good night sleep, but it’s no substitute for testing. Testing can be a substitute for static typing in combination with coverage requirements, but at that point you’re doing so much more work that the static typing straight jacket seems pretty chill.

They come in groups, in a way, but they also refer back any which way, anyway. I recommend just the order they were written, it’s worked well so far. (about half way through, I think)

Yeah, but they didn’t serve ‘fresh’ coffee, the whole point was to make a giant urn of coffee and sell coffee from that all day. I don’t know what the boundaries of those rules were, it’s entirely possible it’s different if you serve it in an open steaming cup, but this was Styrofoam take away cups.

Their customers had had problems before, but they didn’t care. I think that’s what got them in the end.

There’s a safety regulation, but the mcd manual almost said outright to ignore it. And there had been numerous incidents before, and even court cases. They were finally fined something like half a days’ profit from the sale of coffee. Only the scale of of mcd makes it seem like more than what the paperwork costs anyway. Personally, I think someone in the C-suite should get jail time for ‘gross bodily harm’, or whatever.

Turn the mouse upside down.

Also, check your BIOS settings. Turning it on from completely off also sounds sus, surely it’s ‘hibernating’ or something, right?

A terminal is the thing that looks like it might be a computer, but nobody is home, it’s just connected to a modem. Or, maybe, if you’re lucky, The Computer of your university.

A terminal emulator is, well, an emulator, so you can use a 1970’s shell, right there on your computer, just like you can emulate and play Pong or Space Invaders…

Hope that helps

Yes, typo