4 ms·
Even without being cynical about the motivation of the players: it's the unknown unknowns that eat them alive, even if they have the best of intentions. It's a
by dasil003 13y ago
Even without being cynical about the motivation of the players: it's the unknown unknowns that eat them alive, even if they have the best of intentions.
It's also a tough problem to solve because very competent people don't want to work on a boondoggle, and any large government IT project has boondoggle written all over it before it even goes out for bid.
I wonder if Obama asked for any advice from some of his campaign people. If he didn't before I'm sure he is now.
- lifeisstillgood 13y agothat last paragraph is the most interesting.
- Spearchucker 13y agoI don't buy the unknown unknowns. Big system integration problems follow patterns, and an experienced tech will recognise them. The problem with any half-assed strategy is that people gloss over the knowns, which is fatal. First thing anyone should do on a large (actually any) project is to assess the current situation[1]. When you discover a big nasty piece of legacy you need to integrate with, you look at how it works. The rabbit hole must be followed to it's end, or something will bite you. Blaming unknown unknowns in IT is the same as telling the teacher that the dog ate your homework. https://www.wittenburg.co.uk/Entry.aspx?id=46870dcd-70cb-4ef8-98ed-91c94714fe03 https://www.wittenburg.co.uk/Entry.aspx?id=46870dcd-70cb-4ef...
- dasil003 13y agoIt was a poor choice of words on my part. I meant to suggest that they were knowable unknowns, but just that the people involved didn't have a clue.
- PeterisP 13y agoThe project is full with 'known knowns' that have bitten them very hard; their excuses may be valid if they were harmed by the unkowns while handling the basic stuff at least somewhat appropriately - which they have not.