Skip to main content

making breakfast with RUCAS

If there was a lesson to be learned this morning it's practice makes perfect. It's not enough to boil some water with a new piece of kit. It means making some food, purifying some water, making camp and testing your skills and the systems you are going to depend on.

And here is why...


Here is my cook kit minus my long spoon. It's a RUCAS alcohol stove and a stanley pot.


The complete setup... minus the spoon. Making biscuits and gravy.


I tested a homemade windscreen as recommended. Either my tinfoil was inferior or the stove was too hot. The foil burned.

I cannot be 100% certain but I think the tab melted. There is a small ratchet in the tab that I did not notice when I started. I'm just not sure; upon close examination it's wonky.


I've boiled a few cups with this stove but the windscreen did something to the heat pattern that it stained my table. I suppose I could have started a fire if I had not been watching. On the trail this could be a very bad outcome.

The biscuits required 1 3/4 cups of water. The pot was in ml and oz so knowing that 8oz to a cup is important. More importantly the pot was so hot that as I was pouring the water into the meal bag the water hissed and spit. Clearly the top of the pot had retained some heat. This could have ended up in a 3rd degree burn on the trail.

Pouring the super heated water into the pouch was a trick. I had to hold the pouch open. Pour the water. Not scold myself and then hold the pouch and stir. I should have made a cozy or pouch from reflectix.

While I did not have any instant coffee I should have boiled a little extra water for coffee for more practice.


At this point the water is in the pouch. The water and food have been mixed. I'm just waiting for the stove to cool.

I tried using the bandanna to insulate my fingers but it's synthetic and slippery. So it's good to clean or dry my kit and kinda hold the bag. Not much more than that. I need to add a scraper and sponge to my kit in addition to the cozy.

Finally I learned a few other things.

  • keeping everything clean in order to prevent disease is non trivial. If I had made the meal from scratch or in my pot I would have a lot of cleanup before the next meal. Meaning, using my pot for water made the most sense and I won't try anything else.
  • While I'm waiting for the meal to steep I really wanted to cleanup my kitchen. The stove was super-hot so I had to wait. But even after it cooled I could not put my kitchen away. Unfortunately for me I still needed to put my spoon away.

So I added an s-biner to my spoon to clip onto the outside of the pack. Or I might clip it somewhere else but more accessible. But I'll not likely carry it inside my cook kit.


I might also take this cup, or one like it, with me. This is likely to be the last thing I drink from before continuing on. It also means I can have a coffee while breaking camp and not have to be concerned that my kitchen is not packed. There are pictures or drawings of wanderers with pots and pans on the outside of their bindle.

UPDATE and a few more things to learn...

  • 1/2oz of alcohol did not boil a cup of water
  • once the flame is out the stove is still hot and therefore may still vaporize meaning that the jets might reignite instead of the typical cool-preignition state
  • my bandanna is 100% cotton but still slippery and maybe black is not a good color if I need to see if it's clean so that I don't get germs.
  • having a second spoon in the cook kit might be a good idea but then that's just one more thing to clean or keep clean.
  • Read the instructions carefully. This egg and bacon breakfast is awful. Possibly because I'm supposed to drain the excess water or could it be that I need more bacon
  • Using the stanley pot instead of my tin cup [a] measuring marks [b] the handle is longer [c] the bot is taller and so the handle is away from the open flame
  • The reason the pot spits is because the flames from the stove extend up the side of the pot increasing the area of the heat transfer. This is goof for a fast boil but bad when you don't need that much hot water. The bottom of the pot is cooler because the heat has been absorbed by the liquid... and so it spits when pouring.
  • The s-biner on the spoon is a pain. Put it on the thing it is attached to


I thought this spoon was going to be a good idea.  It's not. While it has the reach of the toaks and does not absorb or transfer heat it more than makes up for it with nooks and cranneys. The spoon an fork connect like a transformer but while stirring a meal food can get trapped in the grooves. Takes more time and water to clean.

Maybe there is some wisdom to cooking and eating away from where you sleep. The obvious benefit is that you do not track smells that attract animals. But more importantly you should be focused on that one task. The food, the fire, cleanup etc. This way you do not walk away from the fire leaving it or your meal unattended whether the consequence is a forest fire or attracting animals. Localize and focus on the task.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…