benilov

6 ms·

1.
by benilov 9y ago
It's possible to start agile projects without requirements but with loads of user research and prototyping instead.
2.
Open sourcing Fastly-configure, a script for automating Fastly config(gdstechnology.blog.gov.uk)
1 points by benilov 11y ago|0 comments
3.
The Web Only Sucks If You Are a Sucker(medium.com)
4 points by benilov 11y ago|0 comments
4.
by benilov 12y ago
DbFit ( http://dbfit.github.io/dbfit/ ) provides a more heavy-weight, but much more scalable alternative to raw SQL for testing CTEs.
5.
Migrating GOV.UK to new infrastructure(gdstechnology.blog.gov.uk)
4 points by benilov 12y ago|0 comments
6.
A tool to ensure you get the correct (semantic) version for your project(tombye.github.io)
1 points by benilov 13y ago|0 comments
7.
How the Government Digital Service uses git and github(gdstechnology.blog.gov.uk)
1 points by benilov 13y ago|0 comments
8.
Performance Testing of the Go GOV.UK router with Go(gdstechnology.blog.gov.uk)
4 points by benilov 13y ago|0 comments
9.
Choosing Go to implement the new GOV.UK router(gdstechnology.blog.gov.uk)
75 points by benilov 13y ago|96 comments
10.
by benilov 13y ago
There is monopolistic/market manipulating behaviour going on - it's basically an oligopoly, and the barrier to entry into the mobile telecoms market (ie building your network) is only growing.
11.
by benilov 13y ago
The UK is adopting a similar approach: http://digital.cabinetoffice.gov.uk/2013/01/17/identity-beyo...
12.
by benilov 13y ago
Well ok, the GOV.UK is the 80+% solution for publishing; transactions is another matter, although hopefully when the Digital by Default Service Standard starts kicking in (specifically the open source provision: https://www.gov.u
13.
by benilov 13y ago
Well, the GOV.UK code ( https://www.github.com/alphagov ) is your 80% (or more likely higher) solution. It's based around many micro-services that integrate over HTTP, so it's extremely extensible. However, even wit
14.
by benilov 13y ago
Grassroots sounds nice, but the hard work isn't writing the code - it's convincing those within government that user-centered services and open source are the way to go. I believe that this can only be achieved given a strong mand
15.
Useful GitHub patterns(blog.quickpeople.co.uk)
141 points by benilov 13y ago|19 comments
16.
7 types of feedback that helped make GOV.UK awesome(quickpeople.wordpress.com)
2 points by benilov 13y ago|0 comments
17.
The UK government pays me to write open source all day(quickpeople.wordpress.com)
6 points by benilov 13y ago|0 comments
18.
by benilov 13y ago
What's a 'tittle'?
19.
by benilov 13y ago
> Holding someone else to your own arbitrary standards of acceptability is exactly what I'm referring to when I say these sort of complaints usually ignore the possibility that someone else's life is different than one's own. I agree wi
20.
by benilov 13y ago
> I even considered not submitting this comment, for fear of anyone misunderstanding or taking this the wrong way, and the inevitable "open source is a responsibility" responses. I'm glad that you did, thank you for taking the time to r
21.
by benilov 13y ago
I've taken over the maintenance for a project a few months ago and have tried to stick as closely as I can to what I wrote about. I've also used the pull request hack, it's a really good idea!
22.
by benilov 13y ago
I definitely didn't want to imply that "you should merge any ol' crap". I was commenting more on how maintainers communicate (or don't communicate) their feedback. I see no problem with saying "please add tests", or "don't break the existin
23.
A plea for better open source etiquette(quickpeople.wordpress.com)
103 points by benilov 13y ago|51 comments
24.
Search rankings with Google Spreadsheets(digital.cabinetoffice.gov.uk)
2 points by benilov 13y ago|0 comments