zlacker

[return to "Running a Bakery on Emacs and PostgreSQL"]
1. seanwi+e9[view] [source] 2019-02-26 11:51:01
>>flocia+(OP)
> The key insight is that a bakery formula is so cliched that it can be represented as data. Here’s the formula for seedy malt loaves:

> Of course, that’s not the full set of formulae, because it doesn’t tell you how to make ‘Seedy malt dough’, but that’s just another formula, which consists of flour, water, starter, salt and a multiseed ‘soaker’, where the starter and the soaker are the results of other formulae, which are (finally) made from basic ingredients1. I did consider reaching for the object oriented hammer at this point, but thought that I might be able to do everything I needed without leaving SQL.

There's no way you can do something similar with spreadsheets? The example wasn't in enough detail for me to understand why not. The jump from spreadsheet to SQL seems massive in terms of ease of use.

◧◩
2. rahimn+8a[view] [source] 2019-02-26 12:04:03
>>seanwi+e9
"There's no way you can do something similar with spreadsheets?"

You can, but the author is using tools that are more familiar to him, and hence more productive for him.

Just like when doing some quick and dirty analysis, some people will reach for Excel, some for R, some for Pandas. None of those people is wrong.

Some people go too far the other way: spend too much time learning new tools, and not enough creating things of value.

◧◩◪
3. kiallm+Ta[view] [source] 2019-02-26 12:13:32
>>rahimn+8a
There is a downside to this though .. For this bakery, if you hire someone, theres a reasonable chance they can use a spreadsheet (maybe not add new recipes etc, but use..). I'd bet is very unlikely the same will be true of SQL and emacs.

In tech/development, it's akin to someone building a system in some obscure language, because they are most productive and the only ones developing it today.. It's likely that system will end up being entirely replaced if the team maintaining it grows.

(To be clear, I'm not saying the Bakery made a bad choice, or what using obscure languages is a bad choice, or that optimising for immediate productivity through familiar - to you - tools is bad.. just that there is lots to think about when building a new system..)

◧◩◪◨
4. whynot+Vb[view] [source] 2019-02-26 12:27:37
>>kiallm+Ta
This is a very important point.

Choose tools that are: (1) right for the project (2) right for the current team (3) right for the future team

(3) might be hard given you don't know who joins later, and the engineers might also not have a say if they're not involved in hiring. But you can generally make decent guesses. The odds of the next baker you higher knowing SQL and emacs? Pretty low... the odds they know Excel? Probably higher.

With that said, this was still fun. I enjoy seeing technology used in interesting ways, even if I don't think it's necessarily the most sustainable way to do something.

◧◩◪◨⬒
5. retzke+vw[view] [source] 2019-02-26 15:23:38
>>whynot+Vb
> The odds of the next baker you higher knowing SQL and emacs?

Maybe he'll be looking to hire another person like himself, moving from tech - I'm sure many (most?) of us have toyed with the idea of becoming a baker, cook, farmer, cabinetmaker, wainwright, shipwright, etc. Blog posts like this certainly don't help!

[go to top]