Live data from Hacker News

Running a Bakery on Emacs and PostgreSQL

bofh.org.uk

111–120 of 194 posts

Re: Running a Bakery on Emacs and PostgreSQL

#111

Using emacs with 7 million keyboard shortcuts to accidentally press, and then... lisp!! No thanks. This would be more approachable in an Anaconda notebook.

Your loss.

(Also, Org Mode beats the crap out of Anaconda/Jupyter notebooks. You can still code Python, but the interface is actually ergonomic.)

Re: Running a Bakery on Emacs and PostgreSQL

#112

Earlier quoted context omitted.

I'm not saying it's the wrong approach, I'm saying I don't understand what the problem is. The initial example to motivate moving from a spreadsheet to SQL is only this: recipe ingredient quantity Small Seedy Malt Seedy malt dough .61 kg Large Seedy Malt Seedy malt dough .92 kg Having to tinker with recipes in SQL sounds really bad as well compared to editing a spreadsheet even if you were an SQL expert.

Yeah, he didn't explain that part well. Bakers typically have ingredients in terms of ratios with respect (usually) to the mass of the main flour. There could be up to a dozen ingredients (sometimes just 3) with time and temperature sensitive processes. A typical small artisinal bakery will have a repertoire of a couple dozen baked goods. It's a fair amount of stuff to keep track of especially when you throw planning…

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 from top level “product” nodes (a loaf of bread, say) through one or more intermediate formulae until you reach basic ingredients. For a given set of orders, you need to work out how much of which ingredient to mix at each step in the process. If I were only working in, say six loaf batches, it’d probably be easier to use a ready reckoner approach, but it’s a tiny bakery and I’d rather not deal with the wastage so I only bake what’s ordered.

After about the third time I fucked up the pencil and paper calculations, I decided to automate (then at least the bad calculations were repeatable, and only needed fixing once).

Re: Running a Bakery on Emacs and PostgreSQL

#113

I haven't read the article (yes, I know, sorry), but the headline reminded me of a donut shop here in Houston. I don't know if the sign is intentionally this way, or if the middle letter of the first word in the name fell off, leaving behind the short, horizontal mount point, but either way it amuses emacs folks a lot, because it appears to say: M-x Donuts Who among us hasn't wanted, at least once, to invoke that mod…

When I was a child, we would always drive past a particular convenience store on our way to my grandmother's house. At some point in history, it must have been called "Self Service Mart," but the first S had long since fallen off. I loved imagining what the staff were like. It's probably for the best that we never went inside.

Re: Running a Bakery on Emacs and PostgreSQL

#114

I keep coming back to Emacs reading these stories but it never became a habit primarily I have to work across many desktops/laptops computers with Windows & Linux as well as Android mobile. Emacs not being usable on mobile is a big problem and biggest roadblock in the path.

Emacs runs on Windows as well as Linux (& on macOS, too). It works fine on the terminal in Android, but you'll want a keyboard, too.

In principle you could add special Android bindings for emacs which would make using it without a keyboard somewhat useful.

Re: Running a Bakery on Emacs and PostgreSQL

#115

Earlier quoted context omitted.

I think you have a biased outlook, to be honest. For every handful of programmers I know, I know at least 100 others who maybe can barely use their computer besides basic apps. Programming is still not intuitive (nor enjoyable) for the vast majority of people, and I believe it will stay that way.

Agreed, I think programming as a skill will follow a similar arc to automotive engineering. Early on it was highly specialized, but from the 50s-80s it was generally expected that you knew how to maintain your car and would do the basic jobs yourself (oil, tires, maybe even filters). But now? A lot of people now would even call out AAA to change a wheel.

Cheap tyre iron included with your vehicle vs nuts over-tightened with commercial pneumatic wrench ... it's not that unlikely that the tyre-iron breaks. If it doesn't you may be unable to loosen the nuts. It's pretty reasonable to call out a mechanic.

If you're doing anything complicated you have to wrangle the vehicle computer.

I expect you're right, computers will get more complex, more proprietary, less open, less likely to use open standards, companies will do more to prevent users adapting or repairing them.

Re: Running a Bakery on Emacs and PostgreSQL

#116
post #107

I'm going to be the unfortunate hater, but it sounds like he should spend more time on actually learning how to be a baker and less time writing code in this particular case. This is what I'd imagine most of the people on here would fall into the trap of when the monthly 'I want to quit and work with my hands' post comes up. It's the cliche, I want to disrupt the industry before I even learn it. My girlfriend works a…

May be you got it backwards: people who can't deal with numbers have to stick to the same routine. They can't afford the flexibility, the optimization.

That's what I was thinking too. Perhaps this guy has greater aspirations for his bakery and laying out the foundation like this from day 1 will enable him to grow without many of the pains you might otherwise experience when expanding your business.

Re: Running a Bakery on Emacs and PostgreSQL

#117

Earlier quoted context omitted.

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 make an Alexa skill, but it’s not a priority.

Yeah, named timers are A+ and also having basic math functions at hand is great. We have a couple different tasks that need to be started at a certain time each day, so we also have reminders that go off at said time.

Yeah, the calculation stuff is so handy.

Re: Running a Bakery on Emacs and PostgreSQL

#118

Using emacs with 7 million keyboard shortcuts to accidentally press, and then... lisp!! No thanks. This would be more approachable in an Anaconda notebook.

Your loss. (Also, Org Mode beats the crap out of Anaconda/Jupyter notebooks. You can still code Python, but the interface is actually ergonomic.)

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.

Re: Running a Bakery on Emacs and PostgreSQL

#119
This reminds me of the time I used Python to fill out my Wife's 4th grade report cards. She kept all the records in google sheets, so when it came time to do report cars, she already knew what all the grades should be. But the school only provided a terrible app where you literally had to make three clicks with a mouse to enter each grade. Each kid had about 20 grades to enter, and there were 30 kids. That was a lot of clicking and a lot of RSI.

The app had no import/export, but it turned out you could save your work in progress to a proprietary file format. I figured out the format, and then figured out how to basically take the data in google sheets and munge it into the save file format.

It took about 3 hours to enter all the grades manually, and it took about 3 hours to develop the app. So for the first time we used it, it was a wash, but then we got to use it twice more.

Sadly, then they changed report card programs and the new one used a binary file format. At least the new program allowed keyboard input with shortcuts, so it wasn't as a bad.

Re: Running a Bakery on Emacs and PostgreSQL

#120

Earlier quoted context omitted.

I still miss VB6. It was a beautiful tool and easy to make GUIs with. I still can’t handle writing native GUIs without a good WYSIWYG editor. Delphi was cool, but Object Pascal?! Many people still swear by Delphi and it’s because when your code is UI focused Delphi makes that super easy.

Object Pascal vs Visual Basic? That's not even a competition, Object Pascal, of course. At least it was somewhat internally consistent.

Agree. It was mostly nostalgia. That is just what I learned on. Object pascal was (is) a real language at least
Post reply on HN