I have used native dataclasses with pydantic starting with v1.5 and it’s only improved with the the newer 2.x releases.
Aside from basic inheritance and complex nested types, the pydantic ‘TypeAdapter’ is awesome for simply validating native dataclasses. It’s a little slow, but everything pydantic is =)
> But maybe the CO2 removal stuff really is a big deal.
It’s definitely a thing. There are some super light roasts that if you try to brew them without enough resting time, you can sort of cheat by just grinding the coffee about 30mins before you brew for a hacky quick degas. It really helps get rid of that grassy vegetal taste.
There should be no grassy taste, that’s a roast defect and comes from inconsistent roasting. You should find a better roaster. You can roast really light and not get that taste, but you need to be consistent.
Maybe grassy wasn’t the right term. I don’t mean under developed, it’s kinda bitter and sharp without any sweetness. I’ve experienced this with pretty legit roasters like apollons gold. It seems like the lighter the roast, the more time it needs to degas before it hits the sweet spot.
I've found that lighter roasts don't degas/bloom anywhere near as much as coffees that are taken even a little more darker (like talking about the difference between super light and light). I think this continues up to second crack. I'd guess that the breaking down of the cell walls in the bean has something to do with it, more roast more breakdown = more C02. I actually think the C02 is just probably not even created in lighter roasts.
16:1 water:coffee ratio is a pretty common starting point. Your brew is pretty intense!
I’ve found that darker roasts are much nicer around 195F, I mainly brew very light roast and almost all of them come out under extracted at temps below 200F
> Agile speaks nothing of these sorts of processes
Agile is less specific about the how, but is very much centered on team-led adaptation of concrete process to specific circumstances.
Lean does the same thing, but actually talks about how to achieve that.
(Lean and Agile are mostly built on the same ideas, but the Lean literature comes at the ideas from an engineering mindset, while Agile literature does it from a fuzzier and more touchy-feely mindset.)
The pissing match above has at its root a global namespace conflict around the term “Lean”.
To clarify, the underlying heirachy is:
Shewhart cycle “PDCA” (1939)
Lean manufacturing “Lean” (1988)
Agile Manifesto “Agile” (2001)
The Lean Startup [subset of lean] (2011)
Lean around here often handwaves to mean the Lean startup with Lean manufacturing under that. Technically I’d suggest Lean on its own is really a reference back to Lean manufacturing and the principals of Lean developed by Toyota in the 1960-1980’s in what they later named “The Toyota Way”
You leave out Lean Software Development (2003-, there are several works from the same authors), which is fairly directly about applying/adapting Lean manufacturing to software development. (And is situated within the Agile space, but a lot more focussed on the meta-level process of controlling/adapting process than most Agile work, which often focusses on specific process that worked specific places, and gets easily bent to support the kind of adaopting canned process that is anathema to the Manifesto.)
Where does the manifesto talk about a process of any sort? It’s a set of values. It doesn’t mention anything about iterations, breaking things down, etc
PDCA, in more humanities than engineering terms, is basically the final Agile Principle “At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts its behavior accordingly.”
The “resting time” after roasting depends heavily on the bean and roast level.
Soft beans that are roasted dark don’t require much time since most of the oils have been brought close to the surface already.
Very dense beans roasted lightly take time to degas. In my experience 4-7 days is the sweet spot.
It’s not even a subtle difference. Drinking a very light roast right after roasting will be very sharp/sour/acidic, many times undrinkable. After a several days they will get sweet and fruity and delicious.
Try any natural process bean, medium-light to light roast.
I don't understand what chemistry is going on, but I have personally roasted beans (I don't even work on this very hard, max power, wait for first crack, then eyeball it) and they will consistently take at least 14 days to start tasting good, and last for well over a month without much of the typically stale bean attributes. They degrade a bit, but still taste good.
My record for one of my own roasts is maybe 3 months. It may have tasted good for longer, but I brewed and drank it all. I've had some random washed ethiopians that took a long time to mature, but by and large natural processes really take a long time to mature and last a long time for me.
Yeah, coffee from apollon's gold and manhattan coffee often require this long. Not all manhattan coffees require 40+ days, but all apollons gold do: https://apollons-gold.com/
Even really dark coffees should be good for at least a month, but maybe you just like that fresher roast flavor, and there is nothing wrong with that!!
Really interesting coffee, but expensive for sure. I don't always get their coffee. But other specialty roasters do well 3-4 weeks too.
Regulating horizontal integration seems like it would be very difficult. How exactly would those horizons be clearly defined?
I’ve always thought of Apple having an emphasis on vertical integration(hardware+software=product). So maybe their foray into services would be the line in the sand?
This is a take on the Yamaha Tenori-on[0] style of sequencing which is legendary(but sadly no longer made).
I’m surprised there aren’t more software clones of this available. Even the official iOS app clone was discontinued a few years back. It’s such a fun and highly creative way to sequence, though better suited to melodic phrases than rhythmic patterns imo.
Pretty sure I've seen multiple people doing step sequencing like this in software with the Monome Grid and similar software-driven grids. No idea which application or plugin were they using, though.
Did a brief Google and didn't find anything describing how the tenori on sequencing style differs from other grid based sequences. Mind going into some detail on that?
I remember getting into the Monome ecosystem around 2005 (also a grid-based device) and being surprised by Tenori-on coming along and making something so visually similar. I guess grid-based tools feel natural to a lot of people!
Aside from basic inheritance and complex nested types, the pydantic ‘TypeAdapter’ is awesome for simply validating native dataclasses. It’s a little slow, but everything pydantic is =)