Working on a PC diagnosis HTML file to help people who aren’t educated in technology with PC problems. Finished the rendering part and finally moving on to the styling.
Working on a PC diagnosis HTML file to help people who aren’t educated in technology with PC problems. Finished the first few basic app logic and I’m going to work on the basic rendering soon
Working on a PC diagnosis HTML file to help people who aren’t educated in technology with PC problems. I finished the browser solutions and I’d be moving on to the app’s basic logic.
Working on a PC diagnosis HTML file to help people who aren’t educated in technology with PC problems. I finished the Internet solutions and next on the list is browser problems.
Working on a PC diagnosis HTML file to help people who aren’t that well educated on tech. Started working on main content and solutions for slow computers. Next on the checklist: Internet problems. Haven’t worked on the UI yet (probably last to code)
Ship
The big three from the “whats next” list are all in now: a real timezone search instead of my hand-typed shortlist, working hours you can actually set per person instead of assuming everyone works 9-6, and a shareable link so I stop readding my team everytime I open this on a different device.
The timezone search was the easy win, turns out the browser already knows every timezone (Intl.supportedValuesOf), I just didn’t know that existed when I first wrote it. The working hours thing took more thought since it touches basically every function that checks if a time is “good,” but it was mostly mechanical once I pulled that logic into its own function. Used Claude again for the CSS on the new bits (the working-hours inputs, the little clickable hours label) so it’d actually match the rest of the page instead of looking bolted on, and had it sanity-check the storage-loading code since I chained a few promises together in a way that felt fragile and wanted a second pair of eyes on it.
Still rough: editing hours is done through prompt() popups because I didn’t want to build a whole modal for it, and the shareable link is a bit theoretical since this is just a static file, it works, but only really makes sense if you host it somewhere. Good enough though. Onto whatever breaks next.
I built this because I was sick of doing timezone math by hand every time I had to schedule something with someone in another country. I kept opening tabs, converting “3pm PT” to five different cities, then hand-typing the result into Slack. Small annoyance, but it happened constantly. So now there’s Worldline: drag one slider, see everyone’s local time update live and color-coded, hit “find a good time” to get a few suggested windows, and copy a ready-made message instead of typing it out again.
I wrote the actual logic myself: the timezone conversion, the slider, the scoring for what counts as a “good” time. But I leaned on Claude a fair amount along the way. It helped me debug a nasty DST-related bug where everyone’s time except mine was off by an hour depending on the date; I could tell something was wrong but Claude spotted that I was building the reference date in the wrong spot relative to the timezone conversion. It also did most of the heavy lifting on styling, left alone this would’ve been black text on white with default buttons, so the color palette, spacing, and the slider actually looking like a slider is basically all Claude’s doing on the CSS side. I’m sorry I don’t know how to style ok? 🫠
It’s rough in places, the timezone dropdown is a shortlist of ~30 common zones, not the full IANA list, and “good time” just means 9–6 for everyone with no real concept of actual work schedules. But it does the one thing I built it to do: drag, copy, paste, done. v1.0, shipped.
