Top 10 Posts
Home » My Blog
Thursday, January 10, 2013 at 9:38 pm
If I ever had two pets at the same time, they would be two weiner dogs, named Pepperoni and Sausage. Oh sure, it would be a cute name and all, but the real reason would be at their death. I would choose to memorialize them just so I can answer the question "What do you want on your tombstone?" with Pepperoni and Sausage.
Wednesday, November 14, 2012 at 3:23 pm
I love a good meatloaf. I made meatloaf just last night. Here's how it went together.
We bought some lovely, very tomato-ey BBQ sauce at the Spoon River Scenic Drive. No idea who makes it, but it's not available in stores.
Here's what went in:
- One pound each of ground beef and ground pork
- Two Eggs
- 1 Red Bell Pepper, diced
- 1/2 Green Bell Pepper, diced
- 1/2 onion, diced
- Black pepper
- Loads of Lea & Perrins Worcestershire
- Panko, italian bread crumbs, and crushed saltines (had a lot of dry breads to rid myself of).
- A small amount of a very tomatoey BBQ sauce (not store-bought)
I topped it with a glaze made of that same BBQ sauce, loads of ketchup, honey, and worcestershire. I coated the meatloaf with the sauce and put it in the oven at 500 degrees for the first 10 minutes to dry on the sauce and brown the meat, then down to 375 for the next 45. After that, I put another layer of sauce and then some ketchup swirls, and back in the oven another 10 minutes.
Served with the rest of the sauce.
My only regret was not cutting the peppers/onions smaller, and/or sauteing them first. They made it too crumbly, and it was hard to cut. It was very good.
Yes, this post mostly exists because I haven't touched my blog in 2 years, 1 month. But I love meatloaf, too. P.S. I also chopped up a strip of bacon to go in with the meat.
Monday, September 20, 2010 at 12:06 am
My wife Rachel went yard sale shopping and found me a Nintendo (NES) for only $3. After some maintenance and cleaning, it looks as good as new and works just as well. What a great way to celebrate Mario's 25th birthday! It had a LOT of the original documentation. In fact, it had the original warranty form included. I wondered what the people at Nintendo would think if they received this.
As you can see, I've filled it out and I'm dropping it in the mail tomorrow. Afraid their business reply mail permit has changed or expired so I'm putting postage on this one.
I wonder how many Club Nintendo coins I might earn for this purchase.
If anyone has an old NES Control Deck lying around, and it doesn't read cartridges - try the instructions I used to make mine as good as new. Well that, lots of Lysol cleaning wipes, and a Magic Eraser.
Friday, April 16, 2010 at 11:34 am
I was working today on compiling a program that would help a company stream their webcam over the Internet. I decided to try out a program called Xuggler.
Anyone that's ever tried to compile software on Linux knows that ./configure pumps out hundreds of lines of checks in a few moments' time.
This time was different...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether to use captive versions of dependent libraries... yes
checking whether to enable compiler optimizations... yes
checking whether to regnerate java interfaces from swig... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking whether we saw a bunny... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether we smell bunny poop... no
checking whether to build 64 bit version of package... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
No, those lines weren't highlighted in bright white when I ran the command. I happened to see them while it was scrolling by at 20 lines a second.
Reminds me of the Mozy backup service's Terms & Conditions. A couple years ago, I decided for no apparent reason at all to skim through them, and it said. "Furthermore, you agree to use Mozy for good or for awesome." They've since changed their terms, but I assure you that it was there. It's not so much that it's in there that's funny, it's that it's almost invisible and yet still people notice it.
Sunday, April 11, 2010 at 5:26 pm
I got a Russell Stover solid milk chocolate bunny to celebrate Easter with. As I was eating away on it, I saw a nice little letter on the back saying how they use only the finest ingredients.
And then, of course, I had to read the ingredients. I'm very glad that they use cocoa butter for their chocolate. I can't stand “chocolate” made from palm kernel oil. But I noticed that they also use vanillin.
Why vanillin? There has to be what - one drop of vanilla flavoring in the whole thing. Why on earth would you cut corners there? For those that don't know, vanillin (imitation vanilla extract) is usually commercially extracted by soaking burnt wood or coal tar in alcohol. Yum!