Select to expand quoteptsf1111 said..
Haha, writing code didn't cost that much money. I bet it was wasted on consultancy, architecture, and again, and again. Then someone was actually coding whatever what was asked to code after which they realised they meant something else or requirements changed. Then repeat and repeat and the money is wasted quickly.
Government IT projects are deemed to fail and consultants abuse that. Instead of helping clients be successful, they just squeeze every cent out of them. Would think we know better by now.
Something like this ?
Haha, quite accurate sadly!
Your design skills are good enough to apply for a design job at BOM.
Select to expand quotejn1 said..
Probably not a good idea from a cyber threats perspective. But you can look at the client code by right clicking and viewing page source in your browser. But, bear in mind some of the images and script will be generated by their server.
Security wise I'd say debatable. In general Open Source leads to better security, but then again that's Open Source not just openly available code that is going to be improved only on extreme necessity.
Code visible on client side is just a minuscule bit of the whole thing. But indeed full code + project documentation could be open. So everybody could see how many hours went where and what did these hours produce. It could be all very reasonably spent 50M ?, just nobody knows yet ;)
Select to expand quotejn1 said..sboardcrazy said..
They'll be getting sick of me.. I've put in about 4 feedbacks and an email saying the old site wind graphs were better and why,..
Go hard. Make em cry 
Id say with the media and public backlash they'd have to have got the message by now???
ptsf1111: No, that's from an MS power point presentation called "The Race". This file was kicking around the corporate world about the mid 2000's. I saved it, and pull out a screenshot every now and then as a point that nothing has changed
Tanel: Agreed. But, if they're running closed software (precompiled binaries), and BoM then release their source code that reveals their build, library, toolchain versions and configurations, then their service could become a target, at least using old fashioned methods, "Smashing the stack". So, I think it would be a bad idea to do that from their perspective.
