Hacker News Reader

Comment by sleepybrett | Hacker News Reader

Clemens is in the comment thread. It seems like the system he wrote read out of the 911 call database and displayed all the active calls. Then highlighted calls based on keywords so the head dispatcher could more easily see high priority calls ( crimes in progress ? ).

This seems very safe. The captain in question is just protecting his turf. Even if he saw the benefit he would never admit it because it wasn't his idea.

View on HN

Phrased more charitably, "protecting his turf" is actually "doing his job."

With the little information available, I can see the captain's position. The programmer was new and rolled out changes to the surprise of the captain. Programmer hadn't earned captain's trust yet, and was pushing out new procedures which the captain did not (?) agree with. That'd be a no-no in any company, just substitute CEO for captain.

Regardless of whether his system was fantastic, the manager in any org is meant to be a safeguard, even when it feels like a bottleneck.

I wasn't in trouble for doing what I did. The meeting was discussing how to keep the innovation going in a more controlled manner. The Captain believes the only way to implement software in 911 is to take years and millions of dollars to do it.

I'd love to read an 'AMA' style post, or even just an interview done by another programmer, to learn more about what exactly he did, and how he did it.

The code itself might be intrinsically safe, but the process it generates might not be. The argument doesn't have to be "this code will crash the 911 system"; it might just be "people are going to get hurt when operators act on the information it attempts to generate".

And yet if some operator had an idea to keep some notes (license plates from APBs or something) on stickies and pass them around the room - a new procedure - nobody would act like the world would end.

"FULL REVIEW". How FULL exactly? I think a really thorough review should involve the people who defined the language used, and who wrote the compiler. Certainly everyone who ever worked on the code. And the Compliance team. Lets involve them early to speed up the process!

The professionals on the phone seem to have spoken very highly of the benefits from this program. Why are people second-guessing them?

How is that very safe? Presumably were looking at this unreviewed web app instead of what they were looking at before.

The dispatchers I observe use it focused on their primary screens and if something highlighted they saw out of the corner of their eye.

How about all the important calls they let languish because of the bide-shedders interfering? How is that safe?

Can the naysayers be sued by the family of some kid who died because dispatchers weren't allowed to evaluate a new tool because change scares some people? (No, of course not. And that's why there are so many bikeshedders.)

Bikeshedding is when leaders ignore complex & core questions to focus on trivial ones that are easier to understand. The tools that dispatchers use to handle incoming called doesn't sound like a trivial question.

The core of bikeshedding is continued nitpicking at the trivial by those who can't understand or don't know enough to grasp the its actual significance. And it's not just leaders.

Certainly change would be bad if the programmer in question blidnly modified existing systems. But I don't see any of the reactionaries asking that - they just assume the worst and go off on how unsafe it might have been.

But a new webapp bundling data from other systems into a new view? It shouldn't be any problem at all. The professionals on the phones are the very ones who would have to evaluate the information it returned so there's no way around letting them use it.

They hired Clemans as a programmer and already implemented some of his ideas - I don't think jealousy is a motivating factor here.

Reply on news.ycombinator.com