If you build government tech, there's some serious wisdom in here: https://adhocteam.us/2018/05/24/the-ad-hoc-government-digital-services-playbook/ … Especially about - avoiding big-bang launches - don't develop requirements and then throw them over a wall - don't launch, then shift to maintenance mode; keep systems evergreen
-
-
The idea sounds good, but have you ever seen it being executed?
-
Absolutely, at CMS we've been assisting with API-first development to great results. And even before that at Google, the http://goo.gl URL shortener team used API-first development as they developed their product as well.
- Show replies
New conversation -
-
-
Also, bulk data. So if they don’t like your api they can build another one.
-
"Just give me CSV" is the lowest form of API-first user requirement. It just means that you didn't manage to design a UI better than Excel...
- Show replies
New conversation -
-
-
If you can keep an engineering team that loves the product near it, that’s pure gold, but most government processes don’t encourage that at all.
-
Totally agree, but I see this starting to change in pockets of UK gov. Think the authors recognise this too: "Government needs to continue to be mindful of the internal changes it may need to make to accommodate new means of delivery."

- Show replies
New conversation -
-
-
@tomskitomski I like the idea of youngsters taking a GaaP Year to improve digital government before starting a career...Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.