How do we do this better? Are our limitations valid? Do we really have to wait?
Tools. I'm happiest when I'm bringing order to chaos (see The Six-Ball Juggle). Some processes are near impossible without tools that simplify them. Engineers can work wonders with a spreadsheet, but at some point they themselves get too complex and breakable (without reliable ways to tell if they're broken). If I could make a living programming, I'd do it. My scope is different.
I have freely published some software programs.
- FlowMonster is/was a hydraulic normal depth calculator that the City of San Diego used for over twenty years - saving them hundred(s) of thousands of dollars.
- Ini Manager - I wrote this so to make the InRoads enterprise-wide Standards Management possible. Community Involvement (and Quality Practices in general) require contribution to be easy - or it fails.
I tend not to program anymore, but I do customize XSL/T reports. OpenRoads Configuration/Administration is complex to the point of absurdity - and the primary way to review in bulk (and import/export for mass manipulation) is via Exporting/Importing XML files. XSL/T transforms to and from those standard formats into formats you can actually use.
Innovative Communication. There is nothing really innovative in using websites to communicate. Except in managing civil engineering projects. We tend not to do that. The first project I used a website to educate the stakeholders about the decisions they would be making and the results of our discussion was Oklahoma DOT - MicroStation & InRoads Migration). Amazing results and surprise contributions from across the state (because they had access to all the information). Today I document as I go; I can provide instantaneous access to all project stakeholders: Fast, Lean, Secure Project Websites
Agile Implementations made possible by Constant Communication (Live documentation)