This is super cool, but I’d worry a lot about passing on the domain knowledge to somebody else without a dead-simple TUI/GUI. Eventually somebody else will need to run things.
Will this be software the author will ever have to pass on? I'd guess probably not, considering it's software for his small bakery. It's software directly tied to his identity - he's the sole consumers. That's exactly the kind of software emacs is great for, and precisely the kind of software "hacker" types use. He's not going to sell this as a "bakery management system" and become a software company, he's just going…
Running a Bakery on Emacs and PostgreSQL (2019)
41–50 of 52 posts
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#42Earlier quoted context omitted.
Will this be software the author will ever have to pass on? I'd guess probably not, considering it's software for his small bakery. It's software directly tied to his identity - he's the sole consumers. That's exactly the kind of software emacs is great for, and precisely the kind of software "hacker" types use. He's not going to sell this as a "bakery management system" and become a software company, he's just going…
If he wants to grow beyond a single shop, he'll either need a standard entry format, or be prepared to compete for employees against enterprises which actually need a high degree of technical literacy.
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#43Earlier quoted context omitted.
Indeed, though his work-around of adding a path column is something is worth having anyway, because it makes it much easier to see where the generated output has come from.
It is forcing the engine to do more work though, because it demands a distinct result set, so it adds extra nodes to the plan to remove duplicates. If you know your query doesn't have duplicates, it's much smarter to not add an extra whole sort/distinct when totally unnecessary for correct results.
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#44There was a post a few years ago with the message "don't get too clever or special when designing a system if you want it to be maintainable for any reasonable cost by an average programmer". I think this is related...
Edit: the bakery website is gone or down, 2 years after the story.
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#45Yeah, this is geeky and technically pleasing, but destined to live only as long as the guy has enthusiasm or the will to keep doing this as a small business. As soon as it comes time to have someone take ownership or manage the system, the model breaks. What retail bakery employee is he going to find to maintain the SELECT * FROM statements and look at the Github repo for release notes? There was a post a few years a…
Or it might not, but if he's successful to the point of getting employees, he can start worrying about it then. Isn't that like the number one advice for entrepreneurs? Don't worry prematurely about scaling out.
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#46I‘ve been using MS Access some twenty years ago to do all sorts of magic for small businesses. That was from the 90s to the early 2000s. - Later I‘d use Python to do magic for companies who didn‘t know anything better than MS Excel to handle large sets of data, and when they were lost in chaos, I‘d start to streamline, process, tidy their data and help them make sense. Just two examples that showed me: Use whatever h…
Only vaguely related: what would be the Access equivalent of today? Somethings with low learning curve and forms. Any suggestions?
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#47Re: Running a Bakery on Emacs and PostgreSQL (2019)
#48However, are there viable open-source programs to specifically meet this need (i.e. the daily operations of a small business)? I've seen a lot of startups around this (e.g. ipads at a lot of checkouts now for small businesses), but is there anything that allows the business to not have their data beholden to some 3rd party?
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#49I‘ve been using MS Access some twenty years ago to do all sorts of magic for small businesses. That was from the 90s to the early 2000s. - Later I‘d use Python to do magic for companies who didn‘t know anything better than MS Excel to handle large sets of data, and when they were lost in chaos, I‘d start to streamline, process, tidy their data and help them make sense. Just two examples that showed me: Use whatever h…
Only vaguely related: what would be the Access equivalent of today? Somethings with low learning curve and forms. Any suggestions?
The conventional wisdom in 2021 would probably lean toward python+flask+postgre rather then the traditional lamp stack but i am not sure that's actually an superior solution for the entry level user/designer compared.
Re: Running a Bakery on Emacs and PostgreSQL (2019)
#50Earlier quoted context omitted.
It is forcing the engine to do more work though, because it demands a distinct result set, so it adds extra nodes to the plan to remove duplicates. If you know your query doesn't have duplicates, it's much smarter to not add an extra whole sort/distinct when totally unnecessary for correct results.
I'm fairly sure that a bakery doesn't produce the amounts of data where you need to worry about such things.