A Geologist and an engineer are sitting next to each other on a long flight from LA to NY. The Geologist leans over to the Engineer and asks if he would like to play a fun game. The Engineer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks. The Geologist persists and explains that the game is real easy and a lotta fun. He explains, "I ask you a question, and if you don't know the answer, you pay me $5. Then you ask me a question, and if I don't know the answer, I'll pay you $5." Again, the Engineer politely declines and tries to get to sleep. The Geologist now somewhat agitated, says, "OK, if you don't know the answer you pay me $5, and if I don't know the answer, I'll pay you $50!"

This catches the Engineer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Geologist asks the first question. "What's the distance from the Earth to the moon?"

The Engineer doesn't say a word, but reaches into his wallet, pulls out a five dollar bill and hands it to the Geologist.

Now, it's the Engineer's turn. He asks the Geologist, "What goes up a hill with three legs, and comes down on four?" The Geologist looks up at him with a puzzled look. He takes out his laptop computer and searches all of his references. He taps into the Airphone with his modem and searches the net and the Library of Congress. Frustrated, he sends e-mail to his co-workers -- all to no avail.

After about an hour, he wakes the Engineer and hands him $50. The Engineer politely takes the $50 and turns away to try to get back to sleep.

The Geologist is more than a little miffed, shakes the Engineer and asks, "Well, so what's the answer?"

Without a word, the Engineer reaches into his wallet, hands the Geologist $5, and turns away to get back to sleep.

TL;DR, employers are often penny wise and pound foolish.

One morning, my vehicle had a potentially life-threatening condition that I needed fixed before I could drive to work. I was 3 hours late but made a productive day of it. Plus I had stayed late after work, for no pay, a couple of nights because I have the kind of work ethic that compels me to do weird stuff like that occasionally.

When the time clock report came out it showed I was 3 hours short for the pay period. I brought up that I had "paid it forward" a few weeks prior and asked for an exception based on that. I was told that a) all "extra" work had to have been approved prior to doing it and b) that pay period had already passed, so no, I'd need to make up the hours. Being pretty miffed at being so nickled-and-dimed, and for being expected to drive to work in spite of the possibility of losing my life, I just had them take it out of my time off.

Fast forward to my latest monthly review: After another potentially life-threatening vehicle breakdown and fix, I decided to ask whether I could have a couple of telecommute days per week to offset fuel and mileage to recover the repair cost for the wear and tear on my vehicle. The answer was "No, because then everyone will want to work from home and then we'd have no way to know if they're really working."

On that same day I got an offer for doing the same job at another company for 100% telecommute and at nearly twice the salary. I turned in my resignation two days later. Now they're scrambling to try to replace me.

A Geologist and a developer are sitting next to each other on a long flight from LA to NY. The Geologist leans over to the developer and asks if he would like to play a fun game. The Developer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks. The Geologist persists and explains that the game is real easy and a lotta fun. He explains, "I ask you a question, and if you don't know the answer, you pay me $5. Then you ask me a question, and if I don't know the answer, I'll pay you $5." Again, the Developer politely declines and tries to get to sleep. The Geologist now somewhat agitated, says, "OK, if you don't know the answer you pay me $5, and if I don't know the answer, I'll pay you $50!"

This catches the Developer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Geologist asks the first question. "What's the distance from the Earth to the moon?"

The Developer doesn't say a word, but reaches into his wallet, pulls out a five dollar bill and hands it to the Geologist.

Now, it's the developer's turn. He asks the Geologist, "What goes up a hill with three legs, and comes down on four?" The Geologist looks up at him with a puzzled look. He takes out his laptop computer and searches all of his references. He taps into the Airphone with his modem and searches the net and the Library of Congress. Frustrated, he sends e-mail to his co-workers -- all to no avail.

After about an hour, he wakes the Engineer and hands him $50. The developer politely takes the $50 and turns away to try to get back to sleep.

The Geologist is more than a little miffed, shakes the developer and asks, "Well, so what's the answer?"

Without a word, the developer reaches into his wallet, hands the Geologist $5, and turns away to get back to sleep.

So having gotten my hands on the books I need for the next semester I decided to go take a look at what's in them.

Now the first is mostly web stuff and the second is just about software design. It starts off with an introduction to HTML5, where they didn't really teach HTML5, more like they taught HTML3/4 but not in a way that was too dangerous. I can tolerate not having my semantic tags tbh. They also used spaces on both sides of the = for some reason.

Then a CSS chapter which was also surprisingly mediocre. They didn't use a dedicated CSS file, but I can live with that, for starters.

Then there were some surprisingly decent JS chapters. Although they did use newlines before their { kinda miffed me. There has also been a few developments since this books release, but tbh this isn't the worst case of outdatedness. (And at least they didn't use jquery when teaching JS)

Then a chapter on SQL which I ignored.

Then a chapter about PHP, and, uhm, when did this book get released? Well the ISBN is 978-0-13-215100-9 and using the power of Google we can reveal it was published in.. 2011..

I'm quite happy that I already know how to program

I'd been with the company for maybe two weeks, pushed some changes and updates to a client's site on a Friday afternoon as instructed by my boss, checked everything over and it's all fine.

Come Monday morning and this client is seriously miffed, not all of the changes had applied and the site was a mess all weekend. Turns out a bug with the caching plugin meant what we were getting in the office was different to outside.

Meetings were held and a new QA procedure was put in place.