Neal Wilson ✅ @neal@social.typica.us

@cwebber https://www.youtube.com/watch?v=EtOoQFa5ug8

Bought a little more coffee. (900 pounds)

The time fields are kind of neat because rather than try to be rigid with the format, if there's no : the number gets interpreted as seconds. If there is a :, everything to the left gets treated as minutes and everything to the right gets treated as seconds, which means if you want to add 30 seconds to a time like 8:47, you could put in 8.5:47 (8 and a half minutes and 47 seconds) and it'll normalize to the right thing, or similarly 8:77 and again it'll do the right thing.

I'm going to add a side bar element to the left of that section listing different data series so it's convenient to switch among multiple curves, but otherwise I think that section is basically finished.

A look at data entry in CRUCS. The top section is for putting in additional control points. There's another section that lets you specify an end point. If you don't do that, the point with the largest time is used as the end point, but you can also extrapolate from the curve or set an earlier end time. The control points section lets you remove points (which sticks the data back into the insert section for ease of undo/editing that point).

It's far enough along that it would be obnoxious to have to re-brand it before launch.

Went ahead and bought the crucs.net domain. I haven't set anything up on it yet, but that's where I'm going to put the project I've been working on lately. I've decided to call it CRUCS - Coffee Roasting Using Cubic Splines.

Continuing to make adjustments to the page I've been working on. It's starting to come together rather nicely now. Maybe I can do some testing to make sure everything is fine in Safari/Edge soon.

Pretty sure my mother owns a chainsaw. She'll probably let me borrow that.

Internet is back on. I have another new cable running to the house installed in such a way that it's highly likely someone will need to come back out and do that again, so I'll have to see what I can do to mitigate that risk. I'm thinking I'll need a chainsaw.

Spent some time reworking some of the visual styling. It's pretty obvious that I'm not any kind of visual designer but at least it looks less messy.

Got another text message from my Internet provider letting me know that my service has been restored and asking me to cancel my scheduled technician visit. Only problem with that is my service has not been restored.

Commented and re-organized the code. I want this whole thing to stay self-contained in a single HTML file so someone could just File->Save Page As and get something that they can run locally without a network connection and I also don't want a build step while I continue to work on this so I'll be making it easier on myself if there's some kind of organizational structure instead of just throwing everything someplace convenient at random.

Continuing to refactor the code on my current web project. Initially I did everything quick and dirty to make sure it was working for a single data series, but multiple data series are too useful to leave out. I'd already done the math heavy part of this work previously so now it's making all the user facing stuff work with that. This is letting me delete a whole bunch of code which'll also make the next round of feature work easier.

Since I don't want to chew up my phone bandwidth on streaming, today's background noise is Tetris Effect theater mode on auto-play.

Internet company will send someone out to fix things for real hopefully tomorrow morning. The cat won't like that.

Internet company says they've fixed things, but they didn't.

Still no wired Internet at home.

Spending quality time with the cat.

Still no wired Internet at home, but at least this time it's not a case of the wire going just to my house being snapped.