Have you written about your journey from homebrewer to pro somewhere?
Would love to read about it! Especially about the initial sizing of the equipment ..
Nah, it isn’t anything all that impressive. I actually just sold a majority of my ownership to pursue other interests. Retained a small stake just in case it goes regional.
I worked full time as a software engineer(remote since 2016) while opening and running the production side of my brewery for about 3 years before I could afford to hire help. Hired a brewer, got him up to speed then Covid hit. We kept him on full time during Covid and I didn’t spend much time there.
Once covid calmed down I still didn’t do much reengaging on production and just managed brew schedule and ordering shit.
Went from pulling 70-80 work weeks prior to Covid to a standard 40-45 hours.
Covid basically made my wife and I realize that our kids learned more with us driving their education for 2-3 hours a day than they were getting in 8 hours at school.
Sold most of my ownership as we plan to move onto a sailboat and travel the world with our kids until they go to college. My wife and I both have remote jobs and plan to continue working.
The newer houses here in Japan tend to be all-electric (water, stove, AC) and the current prices (~¥40/kWh) make a lot wish for kerosene heaters of the past decades.
Not trying to defend them but I often see these sentences when Japanese is translated too verbatim.
「申し訳ございませんが…出来ません。」is a very formal way of saying this. Context then of course tells the receiver if they really can’t or just don’t want to ..
When a company simply chooses not to do something, they often use 致しません。When they use 出来ません it would mean not possible (eg unable to ship an order due to time constraints) or because they want to pretend it’s too difficult and unreasonable of a request.
I don't know much Japanese, but yeah that's one of the ideas that comes up immediately. Definitely not my place to say if it's too verbatim, the one I've heard several times is muzukashii / 難しい.
I think it's hard to translate because just 'no' loses part of it, "no thank you (but I didn't actually say no)". So it sort of develops into the translation having a coded meaning, where difficult things are 'polite' refusals.
Yeah, this is very much in line with [1] (see Access under $1billion section):
> Access. You now can just ask your staff to contact anyone and you will get a call back. [..] Within 60 minutes, we had a call back. I was in B1's home talking to him the next day.
I think this is a case where the Free Monad could help a lot. I've only ever built toy-examples but I really liked the way it allows you to structure the program's plan separately from interpreting it.
A dry-run mode could be implemented as a side-effect free interpreter .. without ever having to touch the plan or the program's grammar.
In that case reading about RED/USE (https://medium.com/thron-tech/how-we-implemented-red-and-use...) was a real eye-opener.