There are a lot of cottage food bakers out there, making/selling artisan bread at farmers' markets and through side shelves in established retail/grocery spaces.
The big issue with home baking is scale -- there are often regulations that limit what you can use (often it MUST be in the kitchen within your primary residence, and it can ONLY use a standard residential oven). And if you can't make many loaves, the prices end up being about double compared to industrial produced bread. Hence the $10-25 per loaf at the farmers' market.
So I've been reverse engineering what's possible, given the cottage food law constraints (specifically in Ohio, but applies to a lot of states).
There are lots of non-standard things that I've found actually work quite well for me: Kneading the dough by slowly rotating it in a dough tub (no stretch-and-folds). 18hr+ room temperature bulk fermentation (using just a few grams of starter). Standard oven with 2 "decks" using baking stones. Using only a 10-15 minute bench rest (microproof) then quickly shaping loaves before going straight in the oven (no pans, parchment, banneton, or couche).
So I've put it together as open research for anyone to use. There's also a dynamic recipe page with my production quantities for various breads over here: https://palmbread.com/open_research/baker_recipes/
If you've ever considered baking bread at scale, please give it a look and let me know what you think. Thanks!
Some context: I have kids and I build functional prototypes as my day job.
There are tons of circuit kits out there, but I’ve been surprised/disappointed with how pretty much all of them are designed. So I’ve built out a new approach that uses a graphical sticker on a breadboard to make it easy, but still uses the raw components to make it work so the maker can gain comfort/experience with real engineering.
I also wanted the kit to do something truly interesting/useful. Not just blinking a light or mimicking something else you can easy find elsewhere. This first kit is a fully generative music box that can play millions of different song patterns.
Would love to hear thoughts from the other maker/engineer parents on here :)
Five years ago I worked on an app called Fiddlewax Pro (later renamed Firo); an advanced chord/drum/keyboard/looper. Unfortunately, as iOS updated, the app eventually stopped working and fell out of fashion.
Firo4 is an attempt to bring an old app (that I truly loved both making and using) back to life.
Since it's a continuation of an old app (that originally sold for $20, but was made Free for its final days), launching Firo4 for Free seems like the right move for now. Still deciding where to take its revenue model, but it definitely feels good to move it out of the archived box and get it running again.
Any suggestions on what kind of pricing models are best for a situation like this?
In short, Picnic is google docs-style collaboration for graphic design using just a synced filesystem (google drive, dropbox, sync, local shared folder, etc.).
There's a video of it in action at the bottom of the page.
It's essentially google-docs style collaboration (multiple users in a single doc), but doesn't require a dedicated server and has to get around using all the diff/match/patch magic you can apply when working mainly with text (since Sketch uses lots of binary files).
What's particularly cool is making an existing app collaborative by simply creating a plugin and leveraging realtime syncing services. Curious how many other apps could use this same approach. :)
If you inspect most of the FDM (maker-style, RepRap, etc.) printers, you'll notice that they themselves are constructed of 3D printed parts. But the way they use the parts is a lot different than most end-users (a single purpose item that works stand-alone; like a statue, cup, wall hook, etc.).
Instead, the way the 3D printed parts on the printer are used (in general) is by combining the strengths/attributes of multiple materials. All fasteners are standard metal parts, with mating metal nuts (often embedded or even hot-inserted into the back of a printed part). Precision bushings are press-fit into printed parts to use along steel guide rails.
The TAZ assembly docs show a lot of that thinking, so I thought I'd link over to it in the write-up.
In short, it's the kind of thing that I'd love to see more of because it leverages the best properties of multiple materials instead of being all one or the other. :)
This has been a lot of fun exploring over the past few days. Let me know if you have suggestions/questions about this kind of hybrid approach using 3D printers.
Anything else you'd like to see printed with multiple materials?
*Under Pressure = Barometer (which is correlated with various weather patterns and doesn't require other connectivity to function).
Full disclosure: I'm one of the devs and I would greatly appreciate hearing your thoughts about LightNudge. What do you like about it? What is confusing or unappealing about it?
For those a bit more technically minded and looking to choose colors in an optimal way (for things like data visualization, intuitive interfaces, etc.), look into Munsell colors!
I made a quick tool for playing with Munsell colors and explaining how to use them here:
The "Under the hood" visualization is awesome. I think more projects need to take the time to communicate details like this (without just big blobs of text or links to big piles of source code without a high-level overview).
I ask because this is a major hurdle with the Diaspora* model, in my opinion. I just created two accounts with the same username on different servers to test, and the fact that I could do that bummed me out a bit...
It's great that my data can be free, but if my account is tied to a specific host and I must make a separate, unique account with another host later then I'm still substantially locked in. Essentially, switching accounts likely means all my social connections will have out-of-date contact info, urls, etc. when I switch.
If, however, my user ID is global across the distributed network and there is a way to gracefully transfer my account/data/info to another server seamlessly (without my social connections even knowing/caring about it) then I think distributed social networks like GNU Social could be a game changer.
How hard/easy is it to switch servers and retain @accountname references (i.e. your username)?
When faced with a big list of servers to choose between, my hesitation is that I'll pick one now and realize later that another one is better. For example, I may someday want to host GNU social myself, but if I do so will I essentially be starting over (even if I can retain my data, will my connections still retain a relationship to the new server?).
A nice little diagram and/or technical details page would be much appreciated :)
Serial/UART is just a simple way of organizing how 1s and 0s are sent (start bit, data bits, optional parity, and stop bit, all at an agreed upon baud rate).
To send data to the robot, the transmitter (computer + headphones) encodes 1s as tone (9876Hz) and 0s at another frequency (12345Hz).
So for the decoding circuit all you really need are 3 stages: a microphone, an amplifier (opamp chip), and something that can very tightly look to see if the 0s frequency (12345Hz) is present since UART rests high when idle. A phase locked loop (PLL) is excellent for frequency locking, but can be a little hairy to use. The LM567 tone decoder chip however has a PLL inside but is a simple chip to work with.
A little variable resistor next to the tone decoder is used to precisely dial in the frequency.
Lots of other resistors and capacitors in there to hook everything together, but that's essentially it. Does that make sense? Happy to answer more questions if you have any :)
