From the limited context of the article, Clemans sounds very talented and helpful but "blowing up, yelling, and cursing" when someone dismisses the helpfulness of a project is not an ideal way to change a culture.
It's a power play, and Clemans' disdain for rigid power structures clearly contributed to the friction between him and the SPD administration.
EDIT: the captain's response is not unwarranted at all. Emergency response call centers are a critical public resource and he is ultimately in charge of them.
If Clemans screwed up, he had the potential to have 911 calls be routed to /dev/null. If he succeeded, the department became more efficient. However the 911 system is already working "well enough". Therefore in terms of outside perception any win will be small, and disasters could be huge.
He is not the one who has been give the authority to make this kind of risk decision. The captain is. If Clemans screwed up, the captain would be the one getting fired. Keeping the captain out of the loop is irresponsible. It doesn't matter that it worked. It doesn't matter how good the system is. You need to work with stakeholders, and not behind their backs.
However Clemans seems like the kind of person who can never understand this point.
You are absolutely correct that he had no authority to perform modifications to a critical public service, and that his actions bordered on reckless and negligent and that his response to the captain's accusations was cringe-worthy as well as indicative of the ignorance of his actions, but I think it stands to reason that the captain could have handled the situation more diplomatically.
Granted, I would probably get into a shouting match with Clemans for what he did (and I'm just another developer), but that hardly justifies barring him from entering the premises until further notice.
Clemans' actions can be chalked up to youthful ignorance and exuberance, whereas the captain has no excuse. He is the central source of truth and the ultimate arbiter in the situation, he should know better than to react so aggressively to one of his own staff members.
Touching mission critical things always has risk and those risks have to be mitigated at a political level. If the programmer is this bad at respecting political ownership of responsibility, he has no business touching production this way.
And you want to say the PD could have handled that better? Go into your boss right now and do the same thing. Let us know how he handled that from the unemployment line.
That said - I work for a private firm, not even remotely as crucial as the police dept. cops are trained to deal with all kinds of situations/personalities (my boss is not). The captain could've banned him for a month, instead of permanently. After both of them have cooled down, he could've sat him down and explained that shouting isn't going to help. He could've given him warnings etc. Instead, he seems to have gone on a power trip. Clemans is not some destructive guy, or some criminal. He is just a frustrated over enthusiastic young man. The real losers in this are the people of Seattle.
I hope some other police dept hires him and also he learns to control himself better.
The first time someone isn't as impressed with this guy as himself, he goes red.
I don't think he changed how they operated at all.
He gave them a program which highlighted the most critical calls for most urgent attention.
That's EXACTLY how 911 operators are SUPPOSED to operate.
CAD systems are supposed to do that but it can be difficult to properly do that when lots of calls come in - and when a really critical calls does come in, it frequently is reported multiple times leading to duplicates as other operators key it simultaneously. Many CAD systems will not automatically connect them and require intervention. It sounds like metrics like this and others were being used to automatically suggest critical calls.
He helped them do their job, in the way they should do their job, but in a way which was efficient and directly led to better, and possibly life-saving, outcomes to residents of Seattle.
But you are suggesting he should have been fired ?
[edit:spelling]
Can you imagine the PR nightmare the captain would have had to deal with if someone died or was severely injured because one of the calls wasn't highlighted when it should have been? I think the captain was right here.
There are so many questions that need to be answered and thought out. I'm sure it was a good idea and probably should have been pursued.
As for firing him, it's not because of this program. It's because of the unprofessional way he reacted to criticism. The article says he actually had to be escorted out of the building. I would completely expect someone to be fired for that, especially if the SPD really where such a hostile environment to new ideas.
I'm not saying he HAD to be fired, but the article seems to take the tone that the SPD was being unreasonable. It would seem they where being very accommodating even in light of his childish behavior.
- Caller has indicated a situation wherein a delay in the arrival
of emergency responders may contribute to more serious harm
being done in the caller's vicinity
- Caller has indicated a situation wherein a delay in the arrival
of emergency responders may result in them being unable to
render any meaningful assistance
- Caller has described a situation that may require multiple
units of responders or multiple types of responder to bring
under control
- Caller is unable to respond to the dispatcher
But I don't know any of the details. It may well be that the 911 dispatch software is so badly written that business logic is present in the view layer. I have seen it before in software used by government entities. The code is so brittle that everyone is deathly afraid of doing anything to it unless something is already clearly broken.
When you work on governmental projects, a lot of requirement are legislated in. 10 years ago there might have been some incident that caused the city of Seattle to enact an ordinance stating that all escalations had to be logged. Perhaps that came through the state legislature. That's not some requirement that you can 'get to later' or 'iterate' in. It's technically 'against the law' to deploy code without that requirement satisfied.
I'm not sure if the outcome of his meeting with the captain would have resulted in his banishment from working with the 911 operators if he didn't blow up at them. But, had one of my developers coded a small web app and deployed it without telling anyone, I'd be miffed, if he did it to another group without telling that group's manager, I'm sure I'd get talked to by that manager.
If that developer had gone in and changed a mission critical piece of code without telling anyone, or getting the code reviewed, if it worked, they'd get a stern talking to, if it broke the system, they'd be on a PIP.
But having worked on government software projects before, I am aware that some fraction of them are dominated by office politics and contractor ass-covering rather than any desire to provide some benefit to the public in exchange for its tax dollars.
Absent any additional facts that would contradict, my default assumption is that peon employee was reamed for making his superiors look bad, rather than any genuine technical or legal limitation.
Here's what I saw in my head.
Dev: Mind if I watch how you use this program for a bit?
911: Nah. Slow today.
Dev: Hey, what's that mean there?
911: That's a priority call.
Dev: What's the difference.
911: Real emergencies, instead of cat stuck up a tree type calls.
Dev: People actually call 911 for that?
911: You have no idea. People call when their drive-through order is wrong.
Dev: Wouldn't it help if those were, like, highlighted, or something?
911: Yeah, but they told us it couldn't be done on this system.
Dev: I bet I could do it.
(30 minutes later)
Dev: See, look. I knew I could do it.
911: That's great! Go show this to Mgr!
Dev: Hello Mgr, look what I did! The dispatchers love it!
Mgr: You're a loose cannon, Dev! Turn in your badge and gun right now!
Dev: Wait... what?
Mgr: You have to follow the rules in this department, Maverick. Lives are at stake!
Dev: I literally feel like you are speaking a different language right now.
Mgr: If you so much as pick your own nose without approval, your ass is mine.
Dev: I'll just be going now, thanks.
And it interferes with that deal where management enters the feature request on behalf of the end-users, the crony-packed development contractor quotes eight weeks and $50000 for it, and some punk kid still does it in one day, but with a bunch of other people skimming off the top at taxpayer expense. That gets rolled into a periodic upgrade package that the end-users are conditioned to fear, because it always interferes with their work for at least a week.
That's just the stuff I make up in my head when I don't know the whole story, because that's what matches up with my anecdotal life experience.
How did it determine call priority?
How did it order priority?
How was the ordering presented?
Was the computer system itself modified, or was it running on a parallel, out-of-band system?
Did the call system computer need to run new, untested and unverified processes?
Did the call system computer need new untested dependencies installed?
Was the deployment procedure for the new system worked through with IT? Could IT restore a system with the new call prioritization display on it?
What are the security boundaries for the new call system with the prioritization display? Is the threat model the same? Has he assembled a threat model? Does he care? Does he know what a threat model is?
But you are suggesting he should have been fired ?
On the spot.
Just based on the post, I don't expect its author to even know enough to ask any of the questions you have. Why are you assuming the worst? Is there anything specific that makes you think Clemans was irresponsible?
If any of those answers were any different than what I expect they are, it would have required the participation of the larger IT apparatus at the SPD. In which case, his boss probably would have been suspended as well.
Would it matter that, as badly as Clemans may have behaved, he was significantly better than the other IT staff that worked in the centre?
better? That is positively dripping in thoughtless elitism.
But for the sake of argument, better than the other IT staff who worked with their superiors to define solutions to requirements rather than railroading their pet ideas through? Better than the other IT staff who understand the extraordinary intolerance the public has for acute and sudden failure in public agencies? If this clueless cowboy had brought the 911 dispatch system down, heads would have rolled. Clemens can waddle off and get a new private sector job, but what about everyone else caught up in the mess?
Just based on the post, I don't expect its author to even know enough to ask any of the questions you have. Why are you assuming the worst? Is there anything specific that makes you think Clemans was irresponsible?
The hissy-fit he threw when he didn't get his way? Why, based on this article, would you ever give Clemens the benefit of the doubt? Especially when he's pitted against a public servant who has most likely risked his life on more than one occasion in the line of duty?
Sounds like he changed how they operated to me
One PSAP in particular was very upset with our service. He insisted that we do not connect "Internet calls" to his PSAP, as "there might be viruses or something". Note that this was simply dialing the 10-digit number that's part of the public network - anyone can dial it.
Though it's hard to tell from the article if this was really just a procedural issue ("great software, but you must clear it and run through this checklist") or territorial/political.