And so but anyway, did I ever tell you about my most humiliating experience as a skilled and successful computer programmer?

Here's the thing. Three devices, innit:

1) The GPS works but is spotty, cuz you're in a constant storm.

2) The speed log is basically a vent on the bottom of the hull, measuring the water passing by. But the ice is rushing under the bottom of the hull, and it jams the vent.

3) The radar tracks the target, but the target is so close it might just as well be the icebreaker itself, and the tracker gradually creeps on to the icebreaker's own ass.

So my display, which is accurately showing the data, is like:

We're going slower than a Toronto pub crawl. No, wait! We're going faster than the speed of light!

We're somewhere in Mexico. No, wait! We are probably in Kansas.

The client ship is going the exact same speed at the exact same location as us! No wait. It *is* us. No wait, it's *ramming* us at full speed!!

Man, I had some fails in my time, but this one wasn't just a fail, it was fucking *embarrassing*.

"Build a special custom icebreaking display using the hardware on the ship, it'll be brilliant!"

The hardware doesn't work in the ice. Any actual icebreaker captain could have told me -- us -- that, had we -- they -- ever actually consulted one.

Not, I repeat, my only great failure as a geek.

But, *damn*, that was humiliating.

I wrote an *excellent* program that *brilliantly* displayed data coming from hardware that didn't work.

It was a gig. I got paid. That's not the point. I was a pro, and pro's deliver *value*.

All I delivered was a good laugh.

Not, I repeat, my only great failure as a geek.

But, *damn*, that was humiliating.

I wrote an *excellent* program that *brilliantly* displayed data coming from hardware that didn't work.

It was a gig. I got paid. That's not the point. I was a pro, and pro's deliver *value*.

All I delivered was a good laugh.

Upside: I saw many many seals, and a polar bear from a distance. The comedy officer was actually the helicopter maintenance guy, and I got a helicopter tour of an iceberg. All of that was rather awesome.

Not, I repeat, my only great failure as a geek.

But, *damn*, that was humiliating.

I wrote an *excellent* program that *brilliantly* displayed data coming from hardware that didn't work.

It was a gig. I got paid. That's not the point. I was a pro, and pro's deliver *value*.

All I delivered was a good laugh.

Upside: I saw many many seals, and a polar bear from a distance. The comedy officer was actually the helicopter maintenance guy, and I got a helicopter tour of an iceberg. All of that was rather awesome.

And I was sub-contracted to do that. It was about a six month long project. I wrote an entire windowing system on top of DOS to use VGA to show the display.

(I'm a good fucking programmer, and that's not the only time I've written a graphical UI from scratch.)

And. A comical note: about six weeks before the project was due, my hard drive died. And. My backup drive died.

All I had were some two-month old printouts.

@GeePawHill That was good to read about your success, congratulations .The bit about emerging with no more than a bent antenna with oil on it struck me so funny my brain will be replaying it for a good while, thanks!

@GeePawHill I’m fairly sure Fred Brooks didn’t mean that when he said “Plan to throw one away”, but whatever floats your boat… ‍️

And, for the record, I have been a successful professional programmer, an independent, for 45 years. I've failed more times than most people have even tried.

Some days you get the bear.

Some days the bear gets you.

Find joy in it. Without joy, why are we even doing this shit?

@GeePawHill Yep. It’s that joy that I love about engineering in general. Which is why I don’t subscribe to the current fad of using random text generators. Altman can pry that joy from my cold, dead fingers.

And so but anyway, did I ever tell you about my most humiliating experience as a skilled and successful computer programmer?

So I fly to Newfoundland, and I get on an actual icebreaker ship.

Oh my people, it was so fucking cool. Icebreakers aren't gigantic, like container ships or tanker ships, but they're *big*, just the same.

And the Canadian Coast Guard is a commercial service, not a military one, so even tho they spend months at sea, they take very good care of their sailors, so, broadly speaking, the place was all modern cons.

(You still have to take navy showers, but other than that.)

And, for the record, I have been a successful professional programmer, an independent, for 45 years. I've failed more times than most people have even tried.

Some days you get the bear.

Some days the bear gets you.

Find joy in it. Without joy, why are we even doing this shit?

@GeePawHill This was a great story.

Moral of the story: talk to the fucking customer.

@mayintoronto Talk to the motherfucking customer.

Not, I repeat, my only great failure as a geek.

But, *damn*, that was humiliating.

I wrote an *excellent* program that *brilliantly* displayed data coming from hardware that didn't work.

It was a gig. I got paid. That's not the point. I was a pro, and pro's deliver *value*.

All I delivered was a good laugh.

Man, I had some fails in my time, but this one wasn't just a fail, it was fucking *embarrassing*.

"Build a special custom icebreaking display using the hardware on the ship, it'll be brilliant!"

The hardware doesn't work in the ice. Any actual icebreaker captain could have told me -- us -- that, had we -- they -- ever actually consulted one.