3 ms·

Based on my experience, agreed entirely. I've worked with stellar people at multiple large and small government contractors. The structure of the contract just

by jowiar 13y ago

Based on my experience, agreed entirely. I've worked with stellar people at multiple large and small government contractors. The structure of the contract just doesn't lead to a mentality of "let's make something great", but rather "lets get these boxes checked".

bmelton 13y ago
Let's get these boxes checked... while attending two meetings a day with different groups of stakeholders with entirely different visions for the product, that want to use it completely differently. Let's get these boxes checked... while every stakeholder wants to see our project fail because they'd rather waste a few million dollars and get a proof of concept so that they can then hand the contract off to the vendor they wished had won the bid in the first place. (Note, this happens to ALL vendors, because every group has a different favorite.) Let's get these boxes checked... while having to justify every single change to the environment to the Enterprise Architecture Board ("Why do you need to use Python? Can't you build it in Java?") as well as to the Change Control Board ("Why do you need to open port 80 to this server? Can't we simply proxy that through our dated and oversaturated proxies? Why won't your load balancing work without sticky session support?") Let's get these boxes checked... even though the government has given us three conflicting visions of the project and now refuses to pay us because we're behind schedule because we cannot meet all the new feature requirements that have arisen. Etc., etc. It's a hellish game.
greenyoda 13y ago
The structure of the contract just doesn't lead to a mentality of "let's make something great"... This mentality is probably true for most systems that are built for the internal use of an organization rather than as a product that has to compete on the open market. For example, software built by IT departments for use inside large corporations is notoriously badly designed and hard to use.
- tracker1 13y ago
  I think it depends on the organization and how many hands in the mix... If you have one or two stake holders and one person taking charge of the direction of development, it can come out pretty well. On the flip side it isn't always management.. I've seen developers create forms that should be simple with really weird layouts on screen that make absolutely no sense at all.

by jowiar 13y ago

bmelton 13y ago

Let's get these boxes checked... while attending two meetings a day with different groups of stakeholders with entirely different visions for the product, that want to use it completely differently. Let's get these boxes checked... while every stakeholder wants to see our project fail because they'd rather waste a few million dollars and get a proof of concept so that they can then hand the contract off to the vendor they wished had won the bid in the first place. (Note, this happens to ALL vendors, because every group has a different favorite.) Let's get these boxes checked... while having to justify every single change to the environment to the Enterprise Architecture Board ("Why do you need to use Python? Can't you build it in Java?") as well as to the Change Control Board ("Why do you need to open port 80 to this server? Can't we simply proxy that through our dated and oversaturated proxies? Why won't your load balancing work without sticky session support?") Let's get these boxes checked... even though the government has given us three conflicting visions of the project and now refuses to pay us because we're behind schedule because we cannot meet all the new feature requirements that have arisen. Etc., etc. It's a hellish game.

greenyoda 13y ago

The structure of the contract just doesn't lead to a mentality of "let's make something great"... This mentality is probably true for most systems that are built for the internal use of an organization rather than as a product that has to compete on the open market. For example, software built by IT departments for use inside large corporations is notoriously badly designed and hard to use.

tracker1 13y ago
I think it depends on the organization and how many hands in the mix... If you have one or two stake holders and one person taking charge of the direction of development, it can come out pretty well. On the flip side it isn't always management.. I've seen developers create forms that should be simple with really weird layouts on screen that make absolutely no sense at all.