
Every sysadmin, sooner or later, wonders what the first big project in history would have looked like if it had been done from the command line. This is the system log recovered, with respect and a bit of imagination, from a very, very old disk. No data was lost: it's just that nobody had invented backups yet.
Day one: light
> login creator
Password: ********
Welcome. Last login: never.
> light on
Command not recognised. Did you mean: create light?
> create light
Light created. Brightness: 100%. Warning: no night mode available.
> create darkness --night-mode
Dark theme enabled. Automatic day/night switching: configured. Future users will argue about it forever.
Day two: partitioning
> divide waters --above --below
Partitioning in progress... Partition sky created. Partition sea created. Unallocated space: loads.
Marginal note in the log: remember never to put the two partitions on the same level. Everything floods.
Day three: land and trees
> create land
Land mounted successfully under /world.
> create tree
Tree created. Branches: many. Leaves: very many.
At this point the log shows unusual enthusiasm: the tree was so well liked that the structure was reused for everything else. To this day the folders on every computer are organised as a tree. The leaves, on the other hand, are called files in computers, and they always fall in autumn, just when you need to recover them.
Day four: lighting
> create sun --backlight
Sun installed. Power consumption: considerable. Warranty: a few billion years.
> create moon --power-saving
Moon installed. Recharge phases: roughly every twenty-eight days.
> create stars
How many? Enter a number.
> yes
Invalid value, interpreted as “infinite”. Proceed? Yes.
In the log, the stars are catalogued as status LEDs. All green. Situation nominal.
Day five: fish and birds
> create fish --environment sea
Fish created. Memory: three seconds. Feature, not bug.
> create birds --environment sky
Birds created. Warning: the birds have started tweeting very short messages all day long, to everyone, without anyone asking. The first social network in history was born. Nobody has yet managed to turn off the notifications at dawn.
Day six: animals and humans
> create animals --all
Animals created. Warning: the cat walked across the keyboard. Command executed: sdfghjkkkkk. Platypus created.
The log makes no comment. It simply marks the platypus as experimental build, keep.
> create human --with-love
Human created. Configuration: curiosity at maximum, patience to be adjusted manually.
> assign garden human
Garden access granted. Only file with read-only permissions: one tree, marked with a post-it.
Computing historians agree: it is the first documented case of a user receiving a very clear instruction and asking anyway “but what if I open it just for a second?”. Since then, no manual has ever been read to the end.
Day seven: rest
> deploy --production
Warning: today is the seventh day. Proceed? No.
> logout
Session closed. Operations: six days. Critical errors: none. Warnings: one platypus.
This, in my opinion, is the real great lesson for every sysadmin: even the most ambitious project in history stopped before the weekend. Never release on a Saturday. Never touch anything on a Sunday. It was written in the logs from the very beginning, and we still don't read them.
Loosely based on an old piece from the teneraerbetta.it archive