I don't want to defend the idiocy discussed in this article, but it's useful to try and understand where Cox is coming from.
Traffic engineering is one of those fields where there probably haven't been a lot of hobbyists, until recently, when the Internet has allowed geeks to become expert on pretty much any subject with a few weekends of study. I would also imagine that the PE licensing rate among practicing traffic engineers is pretty close to 100%, whereas I have yet to meet a PE-licensed software engineer... I'm sure the half-dozen or so licensed engineers at NCDOT were probably pretty freaked out to see a study like this from an amateur. Who knows, maybe the group did blow a lot of the conclusions -- it's almost certain that Cox's team disagree with the report, since it is counter to their recommendations. Anyway, the last thing the state engineers want to do is to validate the standing of the community group by engaging with them on the issues, even if it's to educate them on where they made mistakes, so they're going to look to discredit them.
As an analogy, practicing medicine without a license is a crime, even if you're really good at it, and even if all of your patients know you're not licensed.
Again, I think this is a terrible way to try to solve the problem, even if it is supported by laws or regulations. Professional fields of all kinds need to cope with the fact that organized groups of laypeople are going to be able to mount credible challenges to their opinions, on their turf and using their tools.
I think this touches on an interesting point: A few weekends worth of study can produce a short term "unlicensed" practical grasp on pretty much any subject.
In the startup world this is almost taken for granted. For example, I needed to learn how to collect money from customers and didn't want to use PayPal. One weekend later I had a basic understanding of payment gateways, merchant accounts, PCI compliance, etc... The next, I had working code processing customer transactions that has been running for years now without a single issue.
I've learned a lot about payment processing since then but I _still_ trust that code and by extension my former self that was able to quickly get up to speed on a specialized topic.
I imagine the NCDOT engineers had ascribed a lot of value to the time spent obtaining their degrees and licenses ...instead of the practical benefits obtained. They anchored that pride and sense of accomplishment to the specialized format of the reports they work in.
It's interesting to see these two world views collide and certainly this won't be the last time it happens.
Traffic engineering is one of those fields where there probably haven't been a lot of hobbyists, until recently, when the Internet has allowed geeks to become expert on pretty much any subject with a few weekends of study. I would also imagine that the PE licensing rate among practicing traffic engineers is pretty close to 100%, whereas I have yet to meet a PE-licensed software engineer... I'm sure the half-dozen or so licensed engineers at NCDOT were probably pretty freaked out to see a study like this from an amateur. Who knows, maybe the group did blow a lot of the conclusions -- it's almost certain that Cox's team disagree with the report, since it is counter to their recommendations. Anyway, the last thing the state engineers want to do is to validate the standing of the community group by engaging with them on the issues, even if it's to educate them on where they made mistakes, so they're going to look to discredit them.
As an analogy, practicing medicine without a license is a crime, even if you're really good at it, and even if all of your patients know you're not licensed.
Again, I think this is a terrible way to try to solve the problem, even if it is supported by laws or regulations. Professional fields of all kinds need to cope with the fact that organized groups of laypeople are going to be able to mount credible challenges to their opinions, on their turf and using their tools.