pdcawley

22 ms·

1.
by pdcawley 8y ago
Nah. I just have a tiny capacity and a very variable order book. If I baked the same thing every day, the wastage would kill me.
2.
by pdcawley 8y ago
You have a point. If I were doing higher volumes at retail, the thought process would be much simpler. Make up a 60% starter on 8kg of flour in the evening. In the morning, empty a 16kg sack of flour into the mixer, chuck in 500g of salt an
3.
by pdcawley 8y ago
It. Doesn’t. Matter. Use the too, you’re comfortable in and you’ll be way more productive than dropping everything to learn something new. Do that when the limitations of your current tool start to grate on you.
4.
by pdcawley 8y ago
Yeah, the calculation stuff is so handy.
5.
by pdcawley 8y ago
Yeah. Lots of hand waving in the piece because it was a choice between something I could write in a morning for a general audience or, frankly, not bothering to write anything at all. A bakery formula is an acyclic directed graph running fr
6.
by pdcawley 8y ago
For the actual business of making the bread it’s a matter of printing off a single production schedule for the day and taking that into the bakehouse. Touchscreens are a hygiene nightmare in food prep areas.
7.
by pdcawley 8y ago
The echo dot is an essential part of the bakery. Multiple overlapping named timers, fired off without having to touch anything? Get in! Once I start the mixes, everything runs from paper though. Maybe somewhere a long way down the line I’ll
8.
by pdcawley 8y ago
Yup. The spreadsheet is an amazing innovation, I just find all the repetition when adding something that should just be data to be monumentally frustrating. And I have no idea how to make a sheet that copes with orders for Friday and Saturd
9.
by pdcawley 8y ago
Yup. Bakeries have been run using a pen and paper daybook and the master baker’s skill for centuries. But the calculations are still a pain in the arse, so automating that is a big win. The Bread Matters spreadsheet I based the database sch
10.
by pdcawley 14y ago
Yup. My bad. Hashing collision in my brain.
11.
by pdcawley 14y ago
Where's the fun in that? The first bug is pretty blatant and will leap out at you if you're reading the paper closely (it's of the order of a syntax error). Describing the second would have taken too much space, diverted from the thrust of
12.
by pdcawley 14y ago
I read it in Copeland's "The Essential Turing", which I recommend highly.
13.
by pdcawley 14y ago
A very useful comment, that. I've added an update to the bottom of the post. I'd always found the assembler story surprising give Turing's history of mechanising drudge work (the bombes, for instance) and now I know why.
14.
by pdcawley 17y ago
Which is why, if you're starting a Perl project today, you turn on warnings and strict, you choose between TryCatch and Try::Tiny and you seriously consider adding autodie to the mix.
15.
by pdcawley 17y ago
Well... there's CTAN. Oh, hang on, that came first didn't it? Forget I said anything.
16.
by pdcawley 17y ago
And a host of Perl makes it possible for the BBC to serve up its iPlayer content. Some of it is even modern MooseX::Declare based Perl.