98codes

We do still need it. Any time to need to scroll through any extremely long list in order to find a single particular item, the scroll wheel beats the manual binary search of scrollscrollscroll... too far... scrollscrollscroll back... too far... etc.

I would, unironically, use a device that had that iPod interface as a music device until my dying day. Make it only able to stream from Apple Music, make me load up songs through USB -- I'll do it.

We had Slashdot in the late 90s.

The big difference is that when the web blew up, there were new players in every direction. Now, we get to hear from the same 3-4 companies over and over and over and over again.

It doesn't remotely hit the same way.

My immediate thought: "Ah, SimSeattleProcess"

You're telling me this author uses that many em-dashes in their normal writing?

I know enough about Shkreli to know that the intern is right.

They do.

It's worth nothing that this IS Google.

Given that it's an ad company, they want something to connect what you're doing to the rest of their data, and they couldn't possibly keep the old image search results there if they want people to use this.

Just don't blame the user and/or their internet service when the service you're relying on inevitably goes down.

It is definitely worth asking for a copy of those notes, verbatim, as-is from the automatic transcription, to check for errors while the session is fresh in your mind.

If your doctor is worth seeing at all, they will be glad for the corrections.

I graduated quickly from Borland Turbo Basic to Turbo Pascal, and really wish I'd bothered to hold onto all those old floppies. I do still have a Visual Studio / VSCode color settings file that matches the old look -- I used those colors for a good long time, longer than it took me to stop coding in all caps.

Don't worry, nobody but Colorado is ever going to try to, or even think to, fix this one.

> so there must be some market for it out there.

Not anymore, looks like.

At home? Not really, no.

At work? I've got ADHD, so the idea of making a to-do list is fine but keeping it up to date was a challenge. I've created a set of agentic skills that comes through the last 36 hours of emails, meetings, chats, and gathers up all the work I volunteered to do (or was told to do), triages them across urgency/impact, and sorts them into Do/Defer/Schedule/Delegate piles.

Last, I created an app to give a UI to this data to see and act on it all, including a way to flag a to-do that was found and enter why I thought the status or categorization was wrong. On the next run, a review skill reads those comments, makes changes to the other skills accordingly, and sends me an email with details of the changes, and the commit I can use to roll back the change if I'd like.

I've been running it since April and while there were a lot of updates at first, I haven't had to flag anything for review in months, and I get to feel a whole lot better about managing my to-do pile.

I'm looking at open-sourcing it, but since I created it with work resources on work time, I need to jump through a few hoops first.

I've gotten "Hi" with zero other context from people of all backgrounds.