I'm part owner and roaster at a little coffee company in Wisconsin. Author of Typica, a popular free program used to capture and work with coffee roasting production records that's used at roasting companies all over the world. Volunteer on the Roasters Guild education committee. Available for paid coffee consulting, training, open source software development. Living with a cat who broke into my house and decided to stay. Likes: cute, travel, food. Dislikes: blinking lights.
Helped my mother with some Computering. I'm assuming there are settings I don't know about to tone down all the Apple trying to be helpful but really just getting in the way crap, but it makes me sad. They used to have taste. At least I was able to make it so she'll have an easier time with printing stuff now, but I probably need to spend more time on a current Mac to get more familiar with what settings need changing to make things easier for her. I'll also need that for upcoming sw releases.
Pushed some new updates out to the computer at the coffee roaster and while waiting on things there I took a little time to finish eliminating all the compiler warnings. One was a case of the compiler not having enough information to prove that the problem flagged could never happen, but I fixed it anyway so that future me can't break it. The rest were all about C++20 deprecating implicit this capture through =. I'd already cleaned up a bunch of those so I only had a few left to take care of.
Started playing the Dragon Quest 2D HD remakes. Thoughts so far: I am disappointed that the game gave me a ghost instead of a slime as the first enemy (also, why are the slimes now gendered?) and I'm tempted to start over at the highest difficulty since I seem to want to play this more cautiously than normal difficulty warrants (I'm too used to NES Dragon Warrior, I guess). I do like a lot of the quality of life improvements and I adore the orchestral music.
The vast majority of my toll use is going to/from the airport since I'm about the same distance to either Milwaukee or Chicago and it's usually cheaper to fly out of Chicago (I always check both or in cases where the client is buying the flight I advise them to check both and go with whichever is cheaper) so the money in that account lasts a long time.
There's some overlap with accessibility here. Some of my first users to respond enthusiastically were people who didn't need all the features, but loved that they could make what they did need huge enough for their aging eyes to make out easily.
While it wasn't an intentional design goal, the way Typica lays out roasting data is working very well in a training environment. I have the data on a nicely sized screen well positioned so I can hang back and give the trainee space to work while still being able to see exactly what's going on and call out advice as needed.
While starting with sample roasting does mean that messed up batches waste less coffee, those sample roasts should be getting used in service of high impact purchasing decisions, so mistakes can be a lot more costly unless you're just drilling on things you don't intend use (in which case 100% of the coffee is waste instead of being able to sell the successful batches).
The main problems with starting on sample roasting are down to differences in why you're roasting which impact you roasting needs to be approached and (to an increasingly lesser extent for new installations) substantially worse instrumentation on smaller machines. It means you end up with no experience dealing with 2nd crack at all and learn a lot less on earlier parts of the roast since you're really trying to do everything the same, often without the tools that make this easier.
New roaster training continues today. He's got decent instincts so it's mostly about gaining the experience with different roasting situations and how to approach them and that's happening through doing production roasts. I've never been a fan of the approach of starting new people on sample roasters.
New Papua New Guinea is now up for sale on the web site. It should be hitting the shelf locally later today or tomorrow (I need to change the label as the flavor profile is very different from the previous lot). My idea of roasting the coffee faster based on what I was tasting yesterday worked out very well so now I have an Ethiopian coffee that tastes more like a Brazilian coffee and a Papua New Guinea coffee that tastes more like an Ethiopian coffee.
The coffee is a natural from Papua New Guinea. Very fruity (blueberry) aroma, not so much in the flavor. I'm going to try roasting it faster to see if I can bring a bit more of that into the cup.
Today's programming has been a continuation of work on the interface for entering green coffee purchase data. This is completely redesigned compared with 1.x and uses a lot less screen space (meaning there's now lots of room for more features). The old UI was a common area of confusion so I'm hoping people find the new one easier to use successfully.
Author of Typica software for coffee roasters.