I think that recipes should replace phrases like medium high heat or simmer with temperatures. I interpret medium high heat to mean about 350-370 degrees Fahrenheit (175-190 C). Likewise, I call a simmer about 200 degrees (about 95 C).
For measuring pan tempuratures, I use a point and shoot infrared thermometer like this model on Amazon: https://www.amazon.com/dp/B00DMI632G/.
For several years I’ve kept a WordPress instance running in my basement for storing my recipes. I recently uploaded the data to wordpress.com. I may move to a custom domain, but for now it is on a free WordPress sub-domain. Visit it at: https://boydrecipes.wordpress.com/.
When it was in the basement, I didn’t add pictures or worry much about nicely formatting the recipes, sold old entries will likely to revised as I make them again.
\copy (select fields from table where something=otherthing) to '/tmp/test.csv' with HEADER CSV;
On swift.org’s downloads page Swift 3 comes with builds for Ubuntu 14.04 and Ubuntu 16.04, but not 16.10. It is a reasonable guess that the 16.04 build will still work on 16.10, but once downloaded and extracted, it complained about missing
libicuuc.so.55. 16.10 only offers the ICU version 57.
There was a build of icu 55 made early during the development of 16.10. This shouldn’t be scary since it is just a new build a stable library that I think was only dropped because they decided to ship only 57. The .deb file can still be downloaded here: https://launchpad.net/ubuntu/yakkety/amd64/libicu55/55.1-7. Once downloaded, just install with
dpkg -i libicu55_55.1-7_amd64.deb
Now problem solved, swift3 works on Ubuntu 16.10.
Windows 10’s Anniversary Update just force installed itself in the middle of typing a git commit message in the middle of the work day. An hour later, it finished. Of course, it removed my VMs (but did leave the Docker for Windows VM alone).
See my new github project: https://github.com/jd-boyd/simplebatch
The goal of this is to be reasonable fast and powerful, while being dead simple to install and configure.
Installation and configuration should be as simple as:
$ pip install simplebatch
$ batchd &
$ bsubmit -- my_first_job
The current status is pretty much there. There are rough edges, but it is as simple to get started as above.
Using more than working machine will initially require running batchd on the first one and batch_manager on additional machines, but eventually batchd will have a –slave mode.
My first use case for simplebatch will be running graphics magick over directories of images. Other places that it could be useful would be blender rendering, batch downloading, ffmpeg, R jobs, reporting, and many more.
Test large numbers of jobs in the queue.
Support postgres in addition to sqlite. Sqlite was initially chosen to make it easy to get going.
Support what Sun Grid Engine calls Array Jobs. This will make managing animation renders even easier. Currently you would presumably assign one job per frame, but with array jobs you would be able to submit a single job for an array of N frames, and simplebatch would track them as a group.