Protip:

When planning a meeting, it's good practice to give the meeting a title or description, so the attendees know ahead of time what's going to be discussed and can prepare deliverables, questions, or whatever else is appropriate.

Sending out an invite with a title of "Mandatory Meeting" and no explanation makes you look like a power-crazed douchebag.

Yep.

IG is advocating the Rakuten Meeting Method, LOL/Sigh'

At the high school where I spent roughly 19 years as department head, in my first year there, the principal held weekly "mandatory" faculty meetings.

At the very first one all he did was read from the agenda/handout that we were given at the door on the way into the meeting.

Not one word more - or less - than was in the printed handout.

I told him, going into the next "mandatory meeting" that I would stand up and leave the instant he started reading from the handout.

I guess he didn't believe me.

He started reading.

I stood up and left; I never heard a word about it.

He never did it again.

I couldn't get The Girl From Ipenima out of my head this morning, but I couldn't quite get my mouth to work correctly, so I blurted out:

"I have The Girl From Iwa Jima on my mind."

Which caused the female intern to gain a new nickname, if only for today.

be careful... nicknames can become permanent.

As can interns. She's pretty good, too.

I'm guessing that the Girl from Iwo Jima has a habit of raising flags all the time. Interns can do that.

In this lady's case, the nickname is ironic.

She looks frail and dainty, as if she couldn't hurt a fly.

*grumble* if you don't know that ServletRequest.getParameter() returns url-decoded results, after 7-10 years of professional java dev experience, wtf?

So far, I have not found the number of years that someone has done something to correlate strongly to a facility for doing that something.

I feel that a large number of people lack the skill to figure out how to do something better... once they find a single way to do something, they bang on that for the rest of their career.

I know I'm in the minority: I've been known to read RFCs for fun, not just when I need them for the task at hand. I take network-protocol design issues fairly seriously, since the're the atomic units on which everything else we do is built.

I know what "idempotent" means, and I try to apply it to request-processing flows in practice, where applicable.

So I know my expectations are a little out of whack with the typical hacker bozo who works in this industry. But still...

Learn what "+" means in a URL, and don't get confused by it. Get confused about whether somebody forgot to call encode(), sure. But don't get confused about whether your container does the decode() for you.

Seriously...

You are in the minority but certainly not alone. I'm fascinated by RFC's and will read them just to learn about stuff, even if it's historical.

Historical, and occasionally hysterical.

Our PM was laid off.

So that's fun.

Rejoicing.

The Incompetent One has finally decided to move on.

So I'm thinking, if I die during my middle age years, I'd like it to be in a bus accident.

That way, all the people who say "Well what happens if [IG] gets hit by a bus" can have their way.