|
|
|
|
|
by cryptica
161 days ago
|
|
> Agreed, it does not necessarily have to be open source. But my opinion is that if the taxpayer's money is used to pay for software, then that software should be open source. Yes. The government has more than enough leverage to demand this. Skill was never the problem. The problem is bureaucracy; too many regulations and massive hidden corruption. The problem with the regulations is that they were designed with the explicit intent to stifle competition. "Nobody got fired for choosing IBM" - This fact is pure corruption. I remember, when I was at university, one of the courses I took had a project management component and we did an assessment researching failed software projects and it turns out that there were a huge number of failed projects running in the hundreds of millions and even billions (and that was a lot of money at the time); always the same companies kept coming up. IMO, this is fraud, of a criminal nature. People should go to jail. |
|
Extremely expensive software projects in government have a common thread in every case I have first-hand experience with. The government has no consistent vision of what they want or who is the final arbiter of these decisions, and no person in the government is accountable for the outcomes. Both the requirements and responsibility are spread across so many people that for all practical purposes there are no clear requirements and no accountability.
The government software programs that run well in my experience have the organizational equivalent of a BDFL. A BDFL doesn't really exist in government; even when someone acts in that role they are often reassigned to other projects at random.