Neal Wilson ✅ @neal@social.typica.us

Tested turning on the new case (you're supposed to wait 24 hours before turning it on). It lights up and gets cold. Now I just need the electrician to return my call and get some work scheduled so this can be installed where it's really going.

Almost finished with the initial visual design for graphs out of a tool I've been working on lately. I'm starting with hand-crafted SVG before I write the code to generate that.

New refrigerated case arrived today. Very heavy, somehow got stacked on top of a 2nd skid during shipment so it's harder than it should be to get it on to the floor. Called in some extra help from people with appropriate tools.

Working on the SVG generation. Not sure if I'm going to finish that today, but this is getting close to something that I'd be willing to throw online and let other people start using.

Put in the export to Typica feature on the web thingy I've been working on. This can now officially replace my old C++ utility, though I still intend to add at least a few more features before I put it online for others to use. The next big one would be SVG generation so people can eyeball that the plan is what they had in mind before exporting that for use.

The cat has noticed that my lap did not contain a cat and moved to correct that problem.

And there is such an event coming up in a couple months.

The latter seems like the easiest option and would be handy to have at events where there may or may not be a computer hooked up to the roaster at all and if there is it's probably not set up in a way that's convenient for taking your data with you.

The other option, which I haven't seen before, would be to have a timer update the time field continuously and raise the temperature value with each insertion so you could just hit the button when the temperature gets to the next value. No typing at all.

I'm kind of tempted to add a couple of live logging features, but if I start adding stuff like that I'll definitely need to add some styling to avoid confusing people with more advanced features. One option would be an auto-increment on the time field (so once you put in a point it'll advance that to the next 30s and focus the temperature field so there's just one number to put in when it's time).

Added CSV export to the thing I'm working on. Typica export can follow the same pattern. I'm not opposed to exporting for other software, but it's not something I need so I'll move on to other features.

Did a slightly clever thing for removing control points. It puts the point removed into the controls for inserting a new point so it's fast to undo the change and easy to edit the position before reinserting it.

I could throw together an API endpoint to generate a PDF and serve that, but I very much don't want to.

Does anybody happen to know how good/bad support for CSS for printing is these days? For the on screen thing I'm fine with unstyled defaults (though I'm not opposed to something that looks a little nicer), but I'd like it if people could print the page and get something that's arranged to fit nicely on a page with space in the right places to write notes on and without the stuff that doesn't make sense to include in a printout.

Last night I tackled the heaviest math of my current project. I already had a working C++ implementation so it was just a matter of porting it over to Javascript. Also did a tiny amount of quality of life features. It still looks very 90s (I may keep it that way), but slightly more than the absolute minimum needed to be useful is done.

Cat does not like the borg, wants hugs, not assimilation.

Remembered I have popcorn.

Getting something similar built into Typica at some point is likely, but I really do think there's value in splitting this one thing out to be its own thing.

2. This is something that's useful for anybody doing profile coffee roasting regardless of what machine they're on, what software they're using (if they're using any at all). I didn't want to tie this too closely to Typica so people who are good with using paper and pen or competing software can also use this.

Some reasons I wanted to do this in the browser:

1. Editors in other programs don't have the right feature set at a fundamental level. They look suitable for the task and if you get over the overly steep learning curve that arises from that mismatch you can kind of make it work, but the real result is people don't use the tool as often as they would if it were good.