OK, thanks for correcting on Priya. However, I don't say that a prof in CS necessarily knows a thing about application development just because they hold a CS credential, and in this case, that really proved out. You're saying that she didn't do well managing the project because it was difficult and "not worth the trouble"...boy, I don't think that's a shining endorsement, and I think it's an admission of why the thing failed, really.

My characterization of a student with an access DB in his dorm room - truthfully, literally - was how Priya described your side of things when things didn't move along as they should have. So, thanks for correcting, but...

I think you probably had some difficulty working through networking and firewall stuff. I can back you up there - the city at the time was embarrassingly deficient in Network Admins, but...I'm not even sure why they had the role they did in the plan. There was no reason for user-submitted data to even enter the city firewall, I remember making that point. At very least, on your side you could have stood up a prototype that proved out your concept and feature development. Getting hung up on networking...not something that should have happened.

Maybe you know better now - building software can be difficult, and when you face issues, you have to take ownership, stay focused, keep pressing and finding creative solutions. What you can't do is just recede, talk crap about your own team behind their backs, shift blame to others. But, maybe not...