My biggest gripe with Apple Music is shuffling. When I shuffle my entire library of thousands of songs, I'm hearing the same ~50 songs over and over UNTIL I add a new song to my library. Then suddenly I'm hearing songs I haven't heard in years. How does one screw up randomization that bad, and how has it not been fixed over the past several years?
Well that's. Just. Great. I bought a 64GB M4 Max MBP last month. I'm past the 14-day return window. I figured the M5 was near, but assumed M5 Max would come a bit later. Not sure where I came up with that.
You can console yourself with the fact that your laptop, unlike one of the new ones if you'd bought that instead, can run macOS Sequoia (without "Liquid Glass") rather than Tahoe.
This is always the gamble with buying a Mac. Either purchase right when the new is released, or be on the fence of your new becoming old a couple of weeks after purchase.
Coincidentally, I was asking Claude today if something existed that could identify the key, chord progression, tempo, etc from a playlist of my favorite songs to see if there was any pattern that stood out so I could find similar songs with that vibe. Like a more music theory approach to discovering new songs versus the "people who liked this song, also liked these songs" way.
Even more coincidental, earlier today my wife was saying we should take our "Skylight Calendar" screen device that is hardwired into our wall with us when we move. I said I could just make a DIY one... and then I open HN and see the top post: https://news.ycombinator.com/item?id=47113728
Spooky.
Oh by the way, all of the "Open on Bandcamp" links I clicked were 404 pages.
I'd argue that a models ability to ignore/manage/sift through the noise added to the training set from other LLMs increases in importance and value as time goes on.
My "actual job" is a designer, not a career engineer, so for me code has always been how I ship. AI makes that separation clearer now. I just recently wrote about this.[0]
But I think the cognitive debt framing is useful: reading and approving code is not the same as building the mental model you get from writing, probing, and breaking things yourself. So the win (more time on problem solving) only holds if you're still intentionally doing enough of the concrete work to stay anchored in the system.
That said, if you're someone like me, I don't always need to fully master everything, but I do need to stay close enough to reality that I'm not shipping guesses.
reply