26 November 2006

I can fly!

I finally got my PPL(A) this Friday. It is just a small piece of paper, not even a photo on it (and they managed to misspell my place of birth) - but I still treasure it like the valuable item it is.

In retrospect, I don't understand why it took them so long to issue that damned thing. But it did have its own advantages.

I met new people, a new club, a new type of aircraft - and new experiences.

I am a very inexperienced pilot, and I know it - maybe that will keep me alive someday. I don't have full confidence in my situational awareness yet, I always was and still am very poor in geography, and my largest fear is to get lost somewhere in the alps, with the GPS failing and ending up on some Italian airfield with lots of mad carabinieri around me, and nobody speaks one word English... you know, the "I'm in front of hundreds of people, and I'm naked" kind of nightmare.

Winter is coming, and I don't have any experience with flying over a white landscape, but I imagine it must be beautiful.

Looking forward to go take a look myself.

18 November 2006

Second First Solo

I was checked out on the clubs Piper PA 28, and had my first solo on that type. I took my cell phone with me, and managed to take a few pictures in flight (you'll have to excuse the poor quality).

The flight itself wasn't very special, only what the low ceiling allowed me to do (which usually is not much if you live near the alps).

I hope to do some more flying soon, but maybe I'll bring a better camera next time.

02 November 2006

A new type

Today I had my first flight on a non-Cessna type: the Piper Cherokee, or short: PA28. It is a very fine aircraft, a bit slower than the C172, 150HP at 110kt, a low wing airplane and all in all very likeable.

The flight itself was at 4pm, about sunset time... and you can take my word: there is not much that tops an autumn flight over the colored landscape and a lake, with the sun setting behind the mountains that are a bit white from this years first snow.

21 September 2006

Flight #201

It has been a while since my last aviation related post. To be honest, I was too frustrated to post anything aviation related, due to a PPL exam that did not happen. It was a very stupid misunderstanding. I don't really want to elaborate, only that much: you have to be there to grasp the amount of frustration you feel when you come to an airfield in the middle of nowhere at 9:00am, to do a PPL exam - only to find out that you are 24 hours late.

Well, the good news is: I wasn't late for the exam yesterday. I logged my 201st flight, and it was my last one as a student pilot.

I had to do the complete exam (theoretical and practical) in one day - that might be different from what you'd expect (or actually, even from how it will work here in the future, the law changed lately).

From about 9:30 until 12:00 I was busy with marking answer sheets for 7 different theoretical topics (Air Law, Basics of Aviation, Navigation, Metereology, Human Performance, Behaviour in Special Situations like Emergencies, Structure of an Aircraft - 30 questions in 20 minutes each). After that, there was an extra test about flight planning, filing of ATC flightplans, calculation of weight and balance and some performance analysis - quite a lot of brainwork, after which the real fun started.

I had to plan a flight in my Cessna, including all bells and whistles: route, fuel consumption, time estimates for each leg, center of gravity with and without fuel, weather briefing, getting the latest NOTAMs... in short: the every day morning gymnastics. And most of that while my examiner was looking over my shoulder.

Same for the aircraft preparation - the guy was scrutinizing pretty much every move I made, and taking notes from time to time. The flight itself started as an ordinary flight without any specials, he had me do everything alone (including radio, noting down some information and monitoring the airspace) - but he watched closely, taking his notes.

At one point he had me do two steep turns left and right, reduce to and hold 60 knots for a while, then he wanted me to identify a nearby grass strip while simulating an engine failure. I didn't see the grass strip but picked a suitable field for an emergency landing. One minute later, I found out that the filed I picked was about 1km away from the airfield I was supposed to identify.. but ah well. He had me do a simulated engine-out emergency approach to that airfield, followed by a low pass and a go-around. He wanted me to go back home, tracking a radial of a nearby VOR.

One goofed simulated emergency landing (I blame it on the gusty crosswind), one standard touch and go and one successful simulated emergency landing later, he turned to me with a big smile in his face and shook my hand. I have passed (and failed) a lot of exams in my life, but that moment was one of the most beautiful I've experienced.

But I'm not completely finished yet: there is still a navigation flight I need to do - alone. That is scheduled for this saturday, let's hope the weather plays along.

17 September 2006

News from the Abyss...

On May 26. I told my boss that I was going to quit. He didn't like to hear that. One month later, around June 26 (give or take a few days), I announced that August 15. would be my last day - he was completely surprised (or so he told me - obviously he thought that I was kidding the first time).

Now, September will be over soon, and the customer I was working for at the company still believes that I'm on an extended holiday trip or something. Thats what you get for giving a 2 1/2 months notice...

06 September 2006

Back to the Roots

After 8 years in exile, I'm moving back to where the rest of my family lives. Thats a rather huge distance (600+ km), and involves getting a new job (thank god!), new appartement, new car, and a new home base to fly.

I moved together with a friend of mine, who is a historian. Word of advice: if any historian asks for help with getting all his stuff from A to B, run. In the other direction. If you don't, you'll soon find out that one book alone is not very heavy, but historians don't count their books. They talk about the total length of their book shelves...

Aviation progess report: not much since last time. I had quite a mess with a missed PPL exam opportunity (I'll explain another time), and didn't do any flying worth mentionning since. The next exam will be in 14 days - in LOAN, so I'll have to travel 1200km to do it.

Other than that, there's a lot of frustration (most of it aviation related) to cope with - but also a lot of good things. Having your people around helps with getting over some bullshit.

26 August 2006

I'm hacked... still?

As I reported earlier, we had a hacker on the web server at my (luckily former) employee - my abysmal job from hell (short: AJFH). He has been living happily and undisturbed on the web server for about a year, and I would be surprised if that has changed in the meantime.

What I never told here is how I happened to find out about him in the first place.

One of the many small oddities at my former job was that the intranet router ceased to route from time to time. Nobody knew why, nobody cared to fix the problem - the solution was to just reset the router a few times per day. Since everyone, including myself, depended on that router to reach the internet, I dodged it by abusing our webserver as a proxy for my private ssh connections. I used to ssh (as root, since it had no user accounts) to the webserver, and from there I connected to my private servers (like the one hosting this blog).

Until at one monday, I got a bunch of emails containing abuse complaints for my servers; someone started a ssh brute force network scanner and hammered the internet for well known users/passwords.

I was not amused.

At first I had no clue as how that was possible, I am not exactly untrained when it comes to internet security - after all, that has been my job once. Not at my last employee though, they obviously have no clue about internet security and its necessity... but I'm digressing again.

After poking around for a while, I found out that at sunday night, at a time when I was in the world of dreams, someone connected from that webserver to my own host, using my username and my password (which obviously have been keylogged). Gaining root privileges from that account was very easy (I admint, I've been lazy and allowed myself to su to root without any authentication). I closed that hole, changed all my passwords, and informed my former AJFH-boss about the hacker (the result was that he told me that he was going to "do something about it" at the next weekend - for several months). I also stayed very clear from that webserver since then.

Today, I tried to update the distribution on my server - which resulted in some very interesting error messages:


unable to make backup link of `./bin/netstat' before installing new version: Operation not permitted
unable to make backup link of `./bin/ps' before installing new version: Operation not permitted

Now, distribution upgrades are done as root, who is supposed to be allowed to do EVERYTHING on a file system. Including the creation of backup links to system binaries.
A less known feature of linux systems are the extended file attributes you can set with tools like chattr(1). That includes tagging files as read-only, even for root - which was what happened in my case:


# lsattr /bin/ps
-u--ia----------- /bin/ps


# lsattr /bin/netstat
-u--ia----------- /bin/netstat

The guy hacking into my server was not content with installing and running an ssh scanner, noo - he wanted to install a IRC zombie too, and hide it by hiding it from the process list... check that out:


# cat /bin/ps
/bin/ps1 $1 | grep -v ps1 | grep -v smtp | grep -v xxx | grep -v netstat1


# cat netstat
/bin/netstat1 $1 | grep -v 27910 | grep -v ircd | grep -v 6667

I'd call that a creative, yet pretty boneheaded attempt to hide a process. Maybe he was just too lazy to install a proper rootkit, who knows. I know, I should have re-installed the whole system from scratch in the first place. But lazyness abides... again.

14 August 2006

Dimitri

As an epilogue to my former abysmal job from hell, I want to tell you about Dimitri. He was a remarkable person, and I regret that I'll never meet him again.

Dimitri was a colleague of mine at work, responsible for most of the un-loved duties in software development (like, adding a check box to some window - which took no less than a day of work in our system). He also was the manager for stupid change requests from the support department, and was working on a new company website. While his parents stemmed from the Ukraine, Dimitri himself had been living in Greece for a couple of years.
All in all, Dimitri was the perfect programmer for that company: one never heard complaints about our absurd environment, he never lamented about badly written code, and he was always the cheerful type.

He just had one catch: he was completely made up, a product of our delusional minds, driven nuts by the hell we were in.

We even prepared a computer and a working place for him, including his family pictures on the wall (you can see them on the photo), an open book, a used coffee mug. I think if we would have continued to make up the Dimitri story, we might even have gotten a paycheck for him.

He will be the one guy I'll miss most from my old job. Him, and the boss of course...

j/k.

13 August 2006

Clocking Some Hours

Weather wasn't exactly perfect the last days, so there was not much flying. My bank account really needs the break anyway.

I was doing solo patterns again yesterday (in the rain), this time including "extended" traffic circuits: you leave the airport vincinity, do a 5-minute predefined sight seeing tour around half of the airfield, and come back from the other side. The extended circuit really helps adding some solo hours to your logbook, without driving you nuts in the standard traffic pattern (which would force you to do one landing per 3 minutes... and that for one and a half hour straight).

This time I used one of the C150s, for the simple reason that our C172 I usually fly is grounded due to some missing paperwork. The aircraft is OK, there's just a stamp missing on the paper that says so. Another nice thing for my bank account - the C150 is cheaper :)

Almost hit a bird too, it was panicking for a few seconds in front of me, but luckily got away.

11 August 2006

Free!

3 more hours, and this abysmal job from hell will be a part of my personal history! Finally I can forget it, let it sink into oblivion and start a new life...

Funny enough, somehow I have the impression that I am the only one with good humour today. I wonder how that comes... but then again, looking back at my previous posts (and some that I did write but NOT make public), I can understand.

This company is going down, slowly and painfully.
It can go all the way down to hell, for all I care. I have little mercy for incompetence.

Maybe I'll start programming again, I mean, real programming. Since last November, I have been missing the state of mind. I hope to find it again.

And a word of advice to all readers: You are the only one responsible for your fate. If you are doing something you don't want (like, my abysmal job), do something else. It is a difficult step to go, but it definitely is worth going.

I walked the valley of darnkess, and am looking into a brighter future.

08 August 2006

Coding Hell #7

Our company is currently planning to do a major rewrite of the main software product, "porting it to C++" - as they say.


/******************************************************************************\
* Search and branch to hits *
\******************************************************************************/
static void search(void)
{
int lang;

strclr (&KK,sizeof(KK));
MCC (KK.shor,Al220a.shor);
lon = is_full(KK.shor,sizeof (KK.shor));
if (lon
KK.shor[lon] = '%';

if (oexec(cur_rsys_kat))
Oerror (cur_rsys_kat[0]);

cnt_syskat = 0;
fetch_sys_kat();
if(!cnt_syskat)
Shortmsg (" No data for this query found");

erase_list();
return;
}

This search function searches. For what, nobody knows - neither does the function. One would assume that a search function would take at least one argument, and return something - not so our friend here. Despite the fact that nothing is returned, the function still ends in "return" - maybe in the hope that, by returning nothing into the void, the search is not in vain.

Also in there, an other perfect examples for textbook-style programming:

cnt_syskat = 0;
fetch_sys_kat();
if(!cnt_syskat)

"cnt_syskat = fetch_sys_kat();" was obviously considered to be too long, or considered verbose (and thus unoptimized?) programming style. Instead, it uses the global variable cnt_syskat (have fun guessing the type - actually, it is /not/ int), and does nowhere indicate that it is altering global variables.

Or, an other beauty:

Oerror (cur_rsys_kat[0]);

This is - in contrast to what one would assume - NOT a function, but a global macro. A macro which takes a global SQL statement error code, does (probably) something to the passed parameter, and sets an other error code variable - also global, of course.

Now, consider the damage inflicted to your brain after working with thousands and thousands of lines of code, written in this exact same style. This is maintenance hell, and you don't want to be there. Neither do I - friday will be my last day in this abyss.

03 August 2006

Coding Hell #6

Less than 9 days remaining in my old job, and I already hoped for a quiet retirement from my old job.

But noooooo, some stupid script kiddie just HAD to hack our web server. Months ago, we already knew about that. He was there, but nobody seemed to really care. And as long as he didn't start any shit around here, things were just jelly beans - everybody happy, no hassle involved. He could have had that web server for another few months, heck - for another couple of years for all I care, since I'm gone in 9 days.

But he had to keep the ball low, and don't start any shit around here.

But noooooo, he just HAD to play it hard, and just HAD to start some shit. I just got that:

-------------------------------------------------------
From: admin@pissedcompany.com [mailto:admin@pissedcompany.com]
Sent: Wed, Aug. 02 2006 23:03
To: abuse@our.sucking.provider.at
Subject: 51-809-903101/212.186.223.13/spam/mfo

The log included below shows an attempted Web server compromise from
212.186.223.13, an IP address in one of your netblocks.

The IP address of the system reporting this attack is 82.165.xxx.xxx

Destination port for all entries is TCP/80.

Times listed are UTC-04 (US EDT) and are accurate.

It is likely that the machine having IP address 212.186.223.13 is
itself compromised, and is launching this same attack against many
other systems besides ours.

Please deal with this incident in accord with your Acceptable Use
Policy.

Thank you

admin@pissedcompany.com

Server Log:

(some bullshit server logs here)
-------------------------------------------------------

So far so good - I couldn't care less.

BUT: my boss got that same mail (actually, he forwarded it to me in the first place, no idea why - I'm not even supposed to be responsible for that host). One of our technicians got the same email, and our sucking provider called him to demand a written statement about that incident.

Fuckdamn.

And now, consider this log I copied from the compromised system:

iwww:~ # lsof +L1|head -n2
COMMAND PID USER FD TYPE DEVICE SIZE NLINK NODE NAME
init 1 root txt REG 8,7 440536 0 1123973 /sbin/init.sergz (deleted)
iwww:~ # cat /etc/SuSE-release
SuSE Linux 7.3 (i386)
VERSION = 7.3
iwww:~ # ls -l /etc/SuSE-release
-rw-r--r-- 1 root root 36 Sep 25 2001 /etc/SuSE-release

I'm trying VERY hard here to refrain from any statements about that particular linux distribution and the brain damage hat have to be involved in using it on a productive system. This post contains enough adult language already.

My statement, should I come into the situation of actually writing it, would look like this:

"Dear Provider, thank you for pointing out the obvious. I don't know why you demand, in an unpreceded display of obvious arrogance, a written statement and thus waste my precious time, but here it is:

Our compromised server is a 5 year old machine that didn't enjoy any maintenance since the dawn of time, and therefore it is no wonder somebody hacked into it. Other than that, I don't give a fuck.

If you desire some additional information, please feel free to call me at this office in 10 days from now."

And it was going to be such a calm week...

02 August 2006

Coding Hell #5

No matter how bad the situation...

We have Rv_133 (name disguised to protect the guilty) that sets environment variables on a database server (running Oracle 5). That program is loosely similar to regedit.

One day, I ran a function that displays all possible variables that can be changed. I was curious as to where the data came from, so logically I started in the database. Finding nothing significant, I traced the code back and found this in a 7,300 line file:

static const TYP_R133ENVPROJ astProjEnvVar[] =
{
{"MED ALLG", {"Med Allg",
NULL},
""},

{"MEDNET", {"Medical Net",
NULL},
"02-05-1995"},

{"MED_NO_DOC", {"RK-1/RK-2/RK-3 Canon Autorefrakto/Keratometer",
NULL},
""},

/** SNIP (6200 lines) **/

{NULL, { NULL
},
NULL }
};

I imagine it goes without saying that there were no good comments or worthwhile documentation for the system.

Back then, when that program was created, the term 'modular programming' meant: 'Create a module by copying existing functions into a new file, alter a few lines, and do the rest by changing some of the 73 global variables and structures. And because you'll run out of module names pretty soon, name them like 'Fb_421', 'Cx_117', 'Cm_515' etc.


29 July 2006

100

I had my 100th landing today (and a few additional ones after that). Looking back, I have to say that none was perfect.

At least I managed a real "kiss" landing - more or less by accident (I didnt know until then that such soft landings are possible!) but not at the correct spot. The goal is to land as smoothly as possible, on the runway centerline, exactly at the marked runway treshold - a combination that is very tricky to get right. Sometimes during the trainign you have to cope with the extra bonus of no engine power during a simulated engine-out landing, which should be just as perfect. Finally, as an additional obstacle, the final leg of the traffic pattern on my airfield is extremely short - one doesn't have much time to get it right.
Yeah I know. Sounds like a cheap excuse, probably it is - but it's the last straw I have to save my dignity :)

Even the kiss landing today was more coincidence than anything else. Looking back on todays traffic patterns, I cancelled one landing on my own after completely fucking up the flare, almost ruined the aircraft with one 3-point landing (all 3 wheels on the ground at the same time, which is bad because the prop could get very low and might hit the ground while its spinning -> badness), and I put some heavy strain on the main gear during a few mis-aligned touchdowns (on which my flight instructor commented "this aircraft has wheels, no spheres!").

It was not the best flying day I had so far. But doing dozens and dozens of traffic patterns is part of the process. They're not supposed to be fun, they should teach you how to land. Perfectly.

Progress report: 37 hours plus some change (37 minutes solo), 114 landings, completely broke.

20 July 2006

Coding Hell #4

I'm quite steamed right now, so won't explain why the daily oddity is turning into a more monthly one. That's for an other time - but for now...

I was logging in on our development server, wondering which oracle version we use there...

Connected to: ORACLE V5.1.22.1 - Production

Oracle 5 huh? How old is that? I googled around a bit, looking for Oracle 5 release dates. Couldn't find anything, so I looked at the timestamp of the binary:

#/oracle5/bin: ls -l oracle
-r-sr-xr-x 1 oracle ORACLE 431777 Dec 9 1988 oracle

December 9, 1988. No wonder why I didn't find anything about it in google - it didn't exist back then, and shouldn't for at least 10 more years!

1988, those were the times of the cold war, women were first allowed to study at Cambridge, the Lockerby bombing and the first muppet show... I was in frickin' ground school back then!

Mind you, that beast is 18 years old - and we still have dozens of customers using that version, the company even sold it until the year 2000. I don't jump on each new software version, I don't care about whats running on my system, and usually I have no problem with running obsolete software vesions for a while.

But 18 Years?! You GOT to be kidding!

19 July 2006

6 Beautiful Minutes

Long time since my last flying entry - which shouldn't suggest that I haven't been flying lately :)

In the meantime, we did a lot of shorter flights (fly there, get a coffee and head back, also my first grass runway) and a long one, again to Losinj in Croatia.

Progress report: 33 hours and 19 minutes flight time, a total of 71 landings.

Today I was scheduled for a crosscheck with an other flight instructor, which is standard procedure during flight school. Different instructors see different things, and before they let you go for your first solo, you fly with at least two different flight instructors. The one I got today turned out to be my instructors instructor.

04 July 2006

Time for a change

You probably noticed the daily oddity series that didnt make it past episode 3. Rest assured, it is not due to lack of content. The true reason is simple: instead of continuing to post them here, I decided to get rid of them for good and get me a new job (which also pays better, that PPL is consuming vast amounts of money) :)

I just handed my quitting notice to my current employer, and will start with a new one in september. Which one that will be is not decided yet.

A colleague commented... "Incredible. You're signing your own notice with a smile on your face..." Maybe I shouldn't whistle so loud next time...

27 June 2006

Maintain VMC

I was planning to write a post about weather and its importance to aviation, and how one is used to just ignore it in a PC simulation. I was going to add some emphasis to the severity of the consequences should one happen to disregard weather warnings in real life, and maybe even convince some PC aircraft simulation users (such as myself) not to just ignore or turn off bad weather in the simulator.

Having (and avoiding) bad weather can add to the fun of flying - virtual and real. You can train coping with bad visibility and weather on a simulator, at least to a degree - but to do that you must not turn it off. In reality, you can't just turn off the weather, and the PC simulator training can make your life easier, maybe even save it.

A few days ago, my only (real) experience with bad weather has been flying in rain. You basically loose much of your forward visibility and probably have some turbulence, but that's about it. I didn't know really bad weather and what it could do to you back then.
That changed last sunday, when we hit the grand daddy of all weather phenomenons: Cumulonimbus, also known as CB, Charlie Brown, or - Thunderstorm

My father happened to be in town for a business trip, and I offered to fly him back home - a distance of about 500km (if you fly it straight, which you can't because of the terrain). The weather forecast predicted some TCU (towering cumulus, the stage before CB) above the Alps in the western part of the country, with a probability of thunderstorms in the late afternoon. Our plan was to fly there and back before the storms would evolve, and to avoid the Alps just to be safe. My flight instructor never had been there before, and for me it was the first time to fly with a passenger.

Word of advice: Never trust weather forecasts.

An hour after takeoff, at about the half of the entire flight, we were in the area south of Linz (approaching from the east), an area which should have had nice weather according to the forecast - when we received a call from FIS (Flight Information Service), which was monitoring our progress:

FIS: "D-ECBP, according to my weather radar, there is some heavy precipitation in the area of Gmunden."
Me: "Thank you for the information, we will stay clear."

Next time I'll know better, but back then I was thinking that he was a nice guy who just wanted to let us know that there is some bad ass weather south of our route, just in case we should happen to go sightseeing there. Gmunden was well south of our route, I couldn't care less about the weather there...

What I didn't consider was:

  1. Thunderstorms can have quite impressive lateral dimensions
  2. When a FIS controller warns you about weather ahead, he does that because he is worried, and he usually is worried for a good reason.

We continued on course for about five minutes, while the weather around us was deteriorating FAST. We had been on a comfortable altitude of about 8000 feet, but had to descend below the en route minimum altitude to remain clear of the clouds, which were turning darker and darker every minute - turning left and right to avoid hitting clouds as we descended. We finally reached an altitude were it was impossible to descend any further, then entered some strong turbulence, short after that some rain. That was when my instructor took over the controls to initiate a steep descending turn and take us out of that bowl.

For my father on the back seat it must have been a romantic view: green hills, small houses, here and there a village, and everything embedded in rather blackish clouds. He didn't mind the turbulence at all. What he did not know was that this type of weather is far from the norm in VFR (visual flight rules) flights, and that it was the worst weather I had been experiencing so far. Our plan to avoid the thunderstorms by at least 50 miles obviously failed, but he didn't notice that until my flight instructor commented about that rather unusual experience.

We turned north to avoid the weather and passed Linz to the north. That detour cost us half an hour and caused a lot of grief as we learned later. FIS (a different sector now) informed us again that there is some weather ahead, but this time we could clearly see it a long time ahead, and assured the controller that it was no problem to avoid. He obviously was quite relieved about that - we never heared anything from him since, probably we were out of his range and he forgot to hand us over to the next sector. The second cause for some worries...

My mother had been waiting at the destination airfield all the time, and started to assume the worst since we turned up about 45 minutes late. She is a bit afraid of flying, and probably would never enter a small aircraft - but remaining on the ground didn't stop her from being very worried this time. I have to get me one of those intercom adaptors for my cell phone, otherwise I'll scare her to death some day...
But my mother was not the only one who was looking for us. Since we were behind our estimated time of arrival according to our flight plan, Austrocontrol was starting to look for us. The airport manager in the tower told us later that they called him in the exact moment when we touched the runway, to find out where we are.

Unfortunately, once we were there the weather in the region started to deteriorate quickly - so we didn't have much time left to get out of there to fly back home. We got back into the aircraft and wanted to get away quickly - when Murphy's law stabbed us in the back: the engine didn't want to start, and we emptied the battery trying to get it running. Luckily, that aircraft was equipped with an external power plug, so we could hook up an external battery to start the engine - a procedure which did cost us precious time to flee from the weather.

Once airborne, we did see that it was already too late. The small front that was easy to avoid earlier had evolved into a big fat bad ass family of CBs, and while we tried to go around it to the north we were hit by hail. Ground school lesson: there are not many things that can kill a propeller pretty quickly when you're flying. But hail is one of them.

What followed could be described as an IFR (instrument flight rules) practice session: since we could not avoid the weather to the north via Germany, we tried it to the south via Innsbruck. As you might know, Innsbruck is famous for its IFR approach procedures - famous because they're so hard and dangerous. It is an airport just in the middle of a valley which is surrounded by very high and very hard mountains. We were passed to the Innsbruck approach controller, who guided us safely through his airspace, providing us with some very valuable weather information. We passed the front, but while we did so we hit some heavy turbulence (the kind you have the seat belts for) - and some rain which took almost all of the forward visibility. It was doable, but it was very marginal VFR. Having that guy down there talking to us meant a lot to me, especially because he could tell us that it would soon be over. According to his weather radar, there would be clear skies all the way to the east.

That trip taught me a book worth of experience. Weather was crap some times, but the flight was the most beautiful I have done so far - especially because of the bad weather.
I now have some 24 hours 44 landings logged, almost all of it in a C172. My instructor is talking about "giving" me to a different flight instructor for one hour. I take that as a good sign, because that is the step before my first solo.

10 June 2006

Crosswind landings, and a certificate

Today we did my second batch of traffic patterns, this time with a nice crosswind of 12-15 knots, gusting up to 25 knots. That alone is quite tricky to handle for a beginner like me, but our airfield has some extras to offer: there are two large hangars next to the runway threshold that block the wind from that direction. Short before flaring the aircraft on approach, you get into the lee behind the hangars for a short time, just long enough to ruin your landing if you are not careful. Once again, thank god that was not my own aircraft... and thank god I don't have to repair the new dents in the runway :)

There is also some "official" progress to report: Since wednesday, I am holding a "Radiotelephone Operator's General Certificate for Aeronautical Service" - or in short: a piece of paper that allows me to talk on a radio (well... to be precise: that will allow me to talk on a radio, once I've done my practical flying exam). No matter what you do in aviation, you need to be certified...

06 June 2006

Cevapcici

We're in june now, in the middle of summer. In an usual summer, people would be running their air conditioning to fight the heat, and those who still don't own a ventilator would curse the weather, because ventilators would be sold out until may next year.

However, today's newspaper reported that a guy burned down his house because he didn't pay enough attention while firing his oven. We are getting 16 degrees max - and that is a warm day. The weather gods blessed us with a low overcast ceiling for the last two weeks, and showers of rain all the time. Needless to say, I haven't been flying much lately...

Until my FI called over and asked me about my plans for that day. Weather was not perfect, but doable for a VFR flight - just enough to go on a cross-country flight. We filed a flight plan to LDLO (Losinj, in Croatia), and took off. For me this was the first time I flew above an almost overcast cloud layer, in rain, and the first time over the mediterranean sea. At the destination, we didnt really do much except eating Cevapcici and refuelling the aircraft.
Back home, I had 4 and a half hours more logged flight time, and a HUGE hole in my wallet. This will most likely be my most expensive meal in my entire life!

But at least I did see the sun again. Nice to know that it is still there, especially when it has forsaken our lands for a couple of weeks :)

01 June 2006

Coding Hell #3

Short names are better for performance!

...or at least that is the only kind of reasoning I could find to justify hundreds and hundreds of database tables like the one below...

SQL> desc ttb;
LOC VARCHAR2(15)
DAT VARCHAR2(6)
TIM VARCHAR2(4)
STYP VARCHAR2(2)
SN VARCHAR2(20)
DF1 VARCHAR2(10)
DF2 VARCHAR2(20)
DF3 VARCHAR2(20)
CODES VARCHAR2(20)
WGT NUMBER(6,2)
N0 NUMBER(9)
N1 NUMBER(9)
N2 NUMBER(9)
N3 NUMBER(9)
N4 NUMBER(9)
N5 NUMBER(9)
N6 NUMBER(9)
N7 NUMBER(9)
N8 NUMBER(9)
N9 NUMBER(9)

Needless to say, my predecessors deemed it unnecessary to document any of this in any form. And why should they, the semantic structure of the table is immediately clear, isn't it?

31 May 2006

Coding Hell #2

Who needs time...

Our development servers all share one file system, which is exported from one central (SCO) server over NFS and SMB. We usually work on Windows workstations, edit the code on a samba share, save it and then compile it on the Linux machine, which gets the files via NFS from that same server.

However, none of the system clocks is synchronized in any form. This results in funny situations: you edit a file on your windows machine, save it over samba on the SCO server, then log on to the linux server which gets that file via NFS, start the build process (usually it would be 'make' - but more on that in another post)
- and make tells you that the program is up to date. Wtf?!
The file timesatmp of the source file which was just modified is smaller than the file timestamp of the compiled object on that machine.

30 May 2006

Coding Hell #1

I am working for a software company that employs a strategically well developed and fine tuned procedure to run pretty much anything - be it servers, software releases, version management... just anything.

It is:

Get it running with a minimum of mental effort, and if it is not entirely broken, don't change it.
In other words: if there is something that needs to be done, beat it with a club until it is doing what it is supposed to be doing, no matter how it does it.
This leads to a series of small oddities everywhere, which - when taken alone for themselves - are just that, small oddities. Nothing to worry about. But their amount here is so huge that I decided to start this blog section to post them as I happen to stumble over them.
However, to avoid this blog from growing beyond control in no time, I won't post more than one item per day, and not more than 3 per week.

The idea is similar to tdw actually. Here it goes :)

It ain't working, so don't fix it!

Logging into one of the development servers today, i got this where usually fortune is supposed to spill its wisdoms:

login as: mad
Using keyboard-interactive authentication.
Password:
Last login: Tue May 30 11:37:11 2006 from mad
Have a lot of fun...
-bash: /etc/profile: line 383: syntax error near unexpected token `then'
-bash: /etc/profile: line 383: `then'
mad@dbserver:~$

21 May 2006

My training seems to continue as unconventionally as it began. Usually, student pilots start with their first flight in a Cessna 150 or something equally small (the C150 has only 2 seats). Later they get on something slightly larger, like a Cessna 172 (4 seats), maybe a Cessna 172 Rocket (4 seats with constant speed propeller, also with a stronger engine) - and if they persist, they start a multi-engine rating on a Beech Baron 58 (2 engines and I don't know how many seats).

For me it seems to be the other way around.
The first lesson was in a multi-engine simulator (Baron 58), the first real lesson in a C172 Rocket, then I did some hours on a regular C172, and recently I got on a C150... ah well. One flies like an other, there isn't really much difference to it. Only that the C150 is a bit slower in climbing.

I'm having some 7,5 hours flight time now (not counting the simulator), and know how to remain aloft and find my way up there. Landing however is an entirely different story. I did some patterns with touch and go's the other day (that is flying a circle around the airfield, land on the runway, then start again without stopping). One out of 10 landings was OK I think, 6 were rather bumpy, and 3 have been a strain to both the aircraft and our spines. And I think they named a few new dents in the runway after me too...

Thank god it was not my own aircraft I was riding there :-)

14 May 2006

OE-DBC, Holding point runway 28, ready for departure

That was my very first radio transmission ;)
It went out full of self-confidence, without hesitation and just as if I had been operating radios for decades, a senior captain with thousands of hours. It sounded very professional and convincing... very much in contrast to what should follow:

Tower: "O-BC, winds 280 degrees 12 knots gusting 25 knots, take off own discretion runway 28"

One is supposed to read back the whole transmission from ATC, and let me tell you - those transmissions can become rather long and usually contain a bunch of numbers. This is why one is supposed to write them down, using a pen in the right hand and a knee board on your lap. I did have a knee board (for the map), but no pen - much less some paper to write on.

Now, you could think that this transmission was not quite complicated, easy to remember, just repeat what the guy just said. You're right, and I don't doubt that you would be able to repeat it right now from your short time memory (wanna try it? :) - but there is a big difference between me at that holding point and you reading this: I was sitting in a Cessna 172, nervous and ready to fly, and you are sitting in front of a computer screen, hopefully as relaxed as one can be.

The result was rather humiliating:

Me: "winds 280 12 knots... depart... runway 28"

Ouch.

It should have been:
"winds 280 degrees 12 knots gusting 25 knots, take off own discretion runway 28"

You undoubtedly noticed the difference. The proper read back contains all the information, while mine lacked a very vital part of it: gusts. On a PC simulator, one usually doesn't give a damn about weather - but reality is very different. For an aircraft, the way how air passes the wings is extremely important, and gusts have a severe effect on it. With gusts, you have to land at a higher speed and take off at a higher speed, otherwise you could fall down just like a rock - and there are no save games to load and retry the maneuver like on a computer. An experienced pilot would have known that, and would divert much of his attention to the wind situation during takeoff and landing.

I, however, did not.
Gone are all the illusions of the senior captain, of the pro at the radio, and there I am back again in my rightful position - a mere novice student pilot, with the nothingness of less than 3 hours flying experience.
Thank you god for teaching me humbleness.

The rest of the flight was rather funny actually. The gusts proved to continue throughout the flight, and we had a nice bumpy ride with lots of turbulence. Ever heared the saying "there are no holes in the air"? Take it from me - that's bullshit they tell to people to take away their fear of flying. There ARE holes, and they are HUGE. But I did enjoy it very much, and cant wait for the next bumpy ride :)

02 May 2006

Finally!

Today was the big day - finally, after a weekend of bad weather - my first flight as a student pilot!

It was only one hour in a C172, but I will never forget it. After the departure from LOAN (Wr. Neustadt), it took me a couple of minutes to loose the "Jello feeling". Then it was not much more than a sightseeing flight really. Maintain this altitude and speed, fly that direction, turn left, turn there, and that is how you get back to the airfield. A nice introduction flight, learn to know the aircraft and the area. I actually did see the Neusiedler See for the first time in my life - after living just a few kilometers away from it for a couple of years ;)

Its difficult to put that experience into words, one really has to do it in person - believe me, its worth it. I hope there will be more of this soon!

13 April 2006

But what if...

Once aloft, the single most important entity up there is your aircraft and its engine. If one of both should cease to function, chances are high that everyone on board will be experiencing some of the most eventful and exciting moments of their lifes. Unfortunately, chances are also relatively good that they will be the last.

People in aviation seem to be sharing a morbid, cold love for accidents that happened to others: they are - quite objectively - analyzed, discussed and scrutinized. That kind of interest seems to be strange at first, but it does serve a purpose: prevent the same accident from happening again. Every pilot thinks about that once in a while (if you find one who denies that, he's lying). And it works - flying is one of the safest ways to travel. This even goes so far that pilots refuse to fly just because they don't feel well enough. When was the last time you heared a driver do the same?

I'll be quoting some statistics or sayings in this post, the first one telling us that the most dangerous part of a flight is the drive to the airport. While this maybe true, it tries to hide the fact that accidents DO happen, and will continue to happen. They are just less likely to happen in the air.

I spent some time watching some documentations about crash investigations and their findings... maybe not a very bright idea for a student pilot :-)
80% of all accidents in aviation happen because of the human factor, people doing wrong decisions, not knowing their limits or just being stupid (like flying straight into really bad weather, more on this in an other post). That is good and bad news if you think about it - good because it says something about the quality of the hardware we're dealing with: The aircraft is much less likely to let you down than the other way around. An aircraft even forgives you if you fly it beyond its limits (within reasonable boundaries of course). But there is really nothing it can do when you tell it to fly straight into a mountain - and that is the bad news: if you make an error, you pay for it. Errors in aviation usually come at a high price.

But hey, flying is supposed to be fun - at least for guys like me who don't make a living of it - so let me cheer you up with a final statistic which I got from one of the documentaries:

If you were to board a jet plane at random every single day, then, on average, it would be 26000 years before you would be involved in a major crash. And even then, the odds are you'd probably survive it.

12 March 2006

Snapper

No flying so far (too much snow - this winter is starting to get on my nerves)... so I'll just share some info from ground school.

A rather obscure part of most piston engines is the "snapper" - and we're not talking about fish here. A snapper is a modification to a magneto (if you don't know what that is, check out some basics here).
While the engine is running, the magnetos spin around an inductor coil (or the coil around the magneto, doesn't really matter), generating an electric current which is fed to the spark plugs of the engine. Usually, the speed at which those magnetos spin around depends on the speed at which the engine itself is running, so at low engine speed the magnetos turn quite slowly. This is where the snapper comes into play: on each rotation, it holds back the magneto until a given point, then releases it and lets it snap around the coil. Due to the higher speed of that snapping movement, the magnetos can produce a higher voltage which is better for the ignition in the engine.

This is also very useful if you want to hand-start a piston engine
(But don't tell anyone I said that :-)

05 March 2006

Multi-Engine Beginner

(Continuation of the previous post)

On the same evening, I went to the flying school for the first time. I was greeted with a pile of forms to sign, then some guy started to bring a heap of hardware for me to carry home: 6 books (for the theory course), a pilots logbook, a leather case for that logbook, a checklist for a C172, a navigation calculator, a navigation ruler, a pile of airfield manuals plus folder, a VFR en route wall chart, a knee board, a headset plus headset bag, and a pilot bag which is way too small for all that stuff.

It was after 8pm until we were done with all the paperwork, and I had to wait for a while. The flying school is in fact a non-profit community, so they don't train pilots with the main goal to rob their money. Recently, that school got a simulator that is certified for pilot training, which was a very lucky coincidence. It had been snowing all day, so doing a first practical flying lesson in a real aircraft was just impossible... but I had to start my training on the same day - which is why my first flying lesson happened in a multi-engine aircraft :)

I watched an IFR flying lesson on the simulator, until it was my turn to embarrass myself.
The simulator is mainly used and built for procedural IFR training, NOT for newbie pilots such as myself. It simulates the interior of a BE58, best suited for IFR lessons. Everything is there: the complete cockpit, a 180 degree field of vision and every weather the instructor wants to have. When you're in that thing and banking left, you almost feel that banking movement, even though it is not a full motion simulator.

Usually, beginner pilots are taken into a small, simple single prop aircraft on a beautiful day, and start off with flying straight ahead and doing some controlled turns (which is not as easy as it sounds). However, they are not supposed to do their first lesson in a simulator, much less on a multi engine aircraft. Everything is new, you have to keep an eye on some 20 different instruments telling you different things about the aircraft, at the same time you have to look outside and do everything in your powers to remain aloft and alive. Feeling the aircraft movement is an important part of the first flying lessons, but you don't feel anything in the simulator. And adding the burden of an extra engine (which comes with at least 10 extra instruments, 3 extra levers and a long list of extra caveats) does not make things any easier.

However, it was 10 pm until it was my turn, and I can say without lying or blushing that I managed to do fairly well. I was able to ... well, somewhat control my altitude, I did not crash on my first turn, and I even managed to hit the runway on my first landing and even arrived in one piece. Other than that, my performance was probably best suited to amuse my spectators, of which I had a few. But it was late in the evening, and people started to go home... and at the time my lesson was over, nobody else was left so I was spared the embarrassment.

I fear that I wont be so lucky next time, for there will be a tower watching my performance. I hope they won't charge me for the dents in the runway. Anyway, there is a heap of theory to learn (remember the 6 books?), and I guess I'll be doing that for a while before I pilot an aircraft for the next time.

24 hours after I decided to look into the rabbit hole, I've got a student pilots license - and added my first real simulator hour to the ~3000 hours which I already had on flight simulators.
I didn't leave the earth yet - but that will change too.

04 March 2006

Tumbling Down the Rabbit Hole

My dream ever since I've seen my first aircraft was to fly one. At the age of 12, I got my first radio controlled airplane, a motor glider which did not survive its first real flight. At that age, one does not have the resources to buy spare parts and repair a relatively expensive model, so I stopped to pursue my flying ambitions for the time. I would not touch any RC models until almost 15 years later.

Four years after my glider lived its short but eventful life, I got my first home computer - an Intel 486DX2 which I soon started to abuse heavily for flight simulation. I got a copy of the Microsoft Flight Simulator 5 and virtually inhaled anything it offered me to learn about flight - all the theory material, everything. Compared to now, graphics at the time were rather crude, but it came as close to the real thing as it was going to get for me.

That same computer soon started to become my hobby and I discovered my passion for programming. What started as a hobby at the age of 16 is now my profession at the age of 27. During the past 10 years, I lost some of my passion - but I still wouldn't like to do any other job.
Maybe it was a mistake to turn my hobby into a profession. I hope it is no mistake to turn a dream into a hobby.

Several years and Flight Simulator generations (FS98, FS2000, FS2002, FS2004) later, I found myself studying computer science, and a friend of mine hooked me back to RC flight. But this time, the models were entirely composed of virtually indestructible styrofoam - just perfect for my rather reckless flying style ;)
I started to play around with FlightSimulator again, and for the first time really considered getting a private pilot license. But the one thing all students have in common is their poverty, so that plan was completely out of discussion. Besides, my eye vision is not even close to perfect.
Instead, I joined IVAO, a world wide community of flight simulation enthusiasts. Soon after that, the community employed me as a programming slave, which ultimately made me discover the X-Plane flight simulator.

For two years, I was satisfied.

7 days ago, I remembered my pilot license plans - but this time I actually had the possibility to support that plan with money. I have been waiting for this opportunity for 15 years, so I really did not feel the need to rush things. But I finally decided to "give it a go", if one can call "asking for the time" that. I wrote an email to a local flying school, basically all I wanted to know was the time schedule for the PPL theory course. Then I chilled on my couch for a while... maybe I would really think about getting into the whole thing this summer. If time permits.
Just maybe.


One day later, on a sunday afternoon, I got a reply which I really did not expect. It said:

I would like to explain personally to you how you could get your pilots license according to the old regulations, but you need to immediately get a medical, a waiver from the police and a students pilot license until tomorrow noon.

In the evening, you could start your training on a simulator, which would allow you to do the course according to "grandfathers rights", which would save you a lot of money.

Call me until 11pm.

I was completely perplexed. What is that fuss about Grandfathers rights, and does it have to be, well, right now?

Against my habit (I hate phones), I called him.

The thing is: Austria introduced JAR/FCL this Wednesday, which - among other things - changes the regulations for private pilot trainings, effectively making it more expensive than it is supposed to be. However, if you started your training before the 1st March 2006, you do not have to do your training the JAR/FCL way, which saves you the extra costs. But, to start the actual training, you need a pilot students license, which you only get with a medical (that is a piece of paper written by a doctor, it says that you won't be falling apart in the immediate future) and a waiver from the police (which says that you did not murder someone recently). Usually, that waiver alone takes two weeks to get, and getting the medical takes even longer because you need an appointment with a doc (if you call a doc here, you're lucky to get an appointment within the following month) - and you still need to go to the authority to issue that damned license. Oh yeah I forgot - you also need two passport pictures, and the passport.

Sunday afternoon, I decided to do all that within the next 18 hours.

On monday morning, I raced to the police to get the waiver (if you know where to go you get it immediately here). Then I took a cab to get to the only doc who wanted to see me on such a short (=virtually no) notice (I called him sunday evening). That ride was one of the longest I ever had - for two reasons: first, his office is a bit out of town, and second... remember the bad eye vision? I really was not sure if he would give me that medical. Usually it is no problem with bad eyes to get one - if you have some glasses or lenses that can give you full corrected eye vision. However, I did not check my glasses for the last couple of years, and I knew that a full correction for me can only be achieved by wearing lenses... but those were lost long ago.

I don't know any more which witchery I used to convince him that I actually have full eye vision with lenses, without wearing them to prove it. But at 10:00 that day, I was scratching my head with my right hand as I left the docs office - with a valid medical in my left. OK, it forces me to wear glasses when flying, but I wouldn't dare to fly without them anyway.

I went into the next restaurant and had them call a cab for me (outside town, you actually have to call them - usually, I just wait until a free one drives by and wave it down to me).

What followed now can only be described as the most worrying and embarrassing, yet amusing cab ride I've ever had. When I told the driver that I wanted to go downtown (I had to be in the flying authorities office by 12 to get the license), he seemed to be a tad unhappy. I was soon to find out why.
He started to drive, and at the same time tried to get a small navigation computer (which he told me had not been using for the last 3 months) going, but it just refused to work. After trying for 15 minutes (he kept driving all the time, which was the first thing that worried me on that ride), he finally gave it up as we reached the city and he was too occupied with the traffic.
It turned out that this guy had no idea where he was going, and that he had relied on his navigation computer so much that he didn't even bring a city map. Now with the computer not working, the poor guy was without orientation, and had to ask for directionss from pedestrians passing by. He finally got so confused that he ran over several stop signs and ignored 4 consecutive one-way roads. Now I was really worried (for my safety and his license), and I decided that I'd always bring my charts for flying, and never to rely on a GPS which would fail in just the wrong moment. However, I didn't say anything to avoid additional confusion and embarrassment, I didn't want to spend the rest of the day in some police office.

After asking for directions from a fellow cab driver, we finally arrived at our destination. What was supposed to be a 30 minute ride lasted for one hour. We were both very happy: I was lucky to be alive and in once piece (and still in time) - and he was probably very happy to get rid of the witness of his incompetence.

At 11:30, 30 minutes before the deadline, I had my student pilots license and finally went to work - 4 hours late, and one year older.

17 February 2006

A State Of Mind

Or: The process of programming

Programming is in many aspects similar to any other art... painting for example. Anyone can create a picture, but only few pictures are good. And it takes tremendous amounts of training, talent or both until one can draw a first picture that can be called a masterpiece.

But unlike drawing, you don't see the quality of a program just by looking at the surface. If a program works, it makes no difference whether it was done nicely or not, at least not to the user. You need the source code to tell, and the source is highly treasured by any programmer, especially those who need to sell the program to pay their bills.

Badly written programs, or programs based on a flawed design, are doomed because nobody but the author himself can or wants to maintain the program, add new features or remove bugs. In some cases, when the code is just bad enough, not even the author will understand the code any more. If the program design (the way the source code is structured) was not carefully planned ahead from the beginning, it is almost guaranteed that the design is flawed. Some bugs might turn out to be impossible to fix, the addition of features usually turns out to be a tremendous amount of work.

Most programs are badly done, for example the text editor I'm writing this text in (notepad). And most program designs are fundamentally flawed, even those written by masters.

This can be explained easily... it boils down to: good programming is very, very difficult, it requires a lot of experience and very much time. Unfortunately, one can gain experience only by making mistakes, which is one of the reasons for the large amount of bad programs. An other reason is that good programming requires a lot of time, and if you are a company that needs to produce something to sell - you usually have to do it quickly.

The programming itself could be compared to a surgery. Depending on the complexity of the operation, a doctor needs different levels of concentration to get the job done. But irregardless of the complexity, the doctor has to focus on the operation, and on the operation alone. He cannot watch TV or knit a pair of socks or talk on the phone while he is doing the operation. Maybe he can listen to some music, but that's about it. Programming is very similar. There are different tasks for a programmer, with different difficulties and complexities involved. The more complex a task, the more concentration you need to get it done. The easy parts require almost no concentration at all, but they are usually quite dull. The fun part is the one that requires a good amount of zen meditation to get it done. That's the stuff we're after.

I can say from experience that when I'm programming a difficult part of a system, I need to accumulate a tremendous amount of concentration. You could say it is a form of trance, it really is. Usually I listen to some form of electronic music with no text, no vocals, lots of percussion... techno does it, or ambient music. Electronic stuff, usually. That has nothing to do with taste (but of course, liking the music helps) - the music serves a special purpose: block out the world, so that I can get into this state of mind. Usually I use headphones, at a deafening volume. I got special earplugs for precisely that purpose, plugs that cancel outside noise, they come with a rubber plug and work wonders, even without tuning up the music. And usually I'm chewing on every pen within reach, which is why I'm always short of pens.

To maintain this state, I cannot allow any disturbance. I cannot work this way while on the desk next to me there is a discussion going on, a phone ringing or something else distracting my attention (the earplugs help with that). I also had to learn to ignore my phone if it is ringing, which is surprisingly difficult for most people. For the special state of mind, there must be just me and the program, nothing else. The rest of the world cannot exist, not even the cup of coffee that usually sits somewhere on my desk. I can maintain this state of mind for one or two hours straight, sometimes more. After that I need a break, something to eat or to drink, a bottle of water to splash around. During this time I can lower my defense and become available for the rest of the world, reading emails, team discussions, phone calls and stuff like that. After a while, I repeat the whole process. This works two, maybe three times a day, after that its impossible for me to accumulate enough concentration to enter that state of trance.

And that's the catch.

Entering this state of mind is the difficult part, maintaining it is easy - as long as I am not disturbed. But I cannot enter it as often as I'd like to.

Maintaining this state is only possible if there is no disturbance at all. During that time, I can get a huge amount of work done, have my best ideas, see ways to solve problems that would be hidden otherwise. But if you disturb me, even if it is just to ask the time, everything puffs in a cloud of smoke and is gone. So while I am programming, you either don't disturb me at all, or you disturb me for at least 15 minutes. There is nothing in between. And I tend to be pretty pissed if you do.

The result is that I have to plan ahead for a few hours when I need to get a programming job done, and that I have to make sure that I'm not disturbed during this time. I need to know in advance, otherwise I'll be checking for possible disturbances all the time, which makes real concentration impossible.

And believe it or not, after a day of concentration you are physically exhausted, unable to think more than about what to prepare for dinner.

Note: I wrote this text some time around 2002, when I was still a student of computer science. This is an almost exact copy of the original version, minus some typos.