**WARNING**

The survival techniques described in the following guide are to be used at  your own risk in case of emergency regarding software curiosity.
The publisher will not accept any responsability in case of damages caused by misuse, misundestanding of instruction or lack of curiosity. 
By trying the action exposed in the guide, you accept the responsability of loosing data or altering hardware, including hard disks, usb key, cloud storage, screens by throwing them on the floor, or even when falling on the floor with your laptop by tangling your feet in an entanglement of cables.
No arms have been done to human, animal, computers or plants while creating the guide. No firearms or any kind of weapon is needed in order to survive software.    
Just a little bit of patience.

**Software observation survival stresses**

**Physical fitness plays a great part of software observation. Be fit or CTRL-Quit.**

When trying to observe software you might experience stresses as such :

*Anxiety
*Sleep deprivation
*Forgetting about eating
*Loss of time tracking

**Can you cope with software ? You have to.**


> our methods for observation, like mapping, come with their luggage.


% SEEALSO: http://observatory.constantvzw.org/etherdump/toc.md.diff.html



% CSSHERE: section warning