3 ms·
Working in government is not always like this. I spent about 9 months contracting in the UK's Ministry of Justice > You force developers to use tools designed
by sjtgraham 11y ago
Working in government is not always like this. I spent about 9 months contracting in the UK's Ministry of Justice
> You force developers to use tools designed for lawyers
Nope, we used whatever we wanted to.
> You distrust your employees
Nope, most people used OS X and had full control over their machine
> You tether developers to their desk
Nope, there is wifi throughout the building. I actually worked from home a lot, eventually only coming in for sprint planning and retros
> You prefer government-specific service providers
Nope, we deploy on AWS in prod, and spin up Heroku apps for sharing prototypes
> Temporary integration
Nope, we run CI on every branch, pull requests are not merged until green.
> Sparse delivery
Nope, Continuous delivery. Master is always deployable. We deploy whenever we want.
> You still see waterfall as a viable option
Nope
> You don’t place process on a pedestal
Nope, use all best practise you'd expect in any modern software shop
> You erect a moat between developers and servers
Nope, our releases our deployed by CI but we can SSH into any box (via VPN and jump boxes)
> New technologies are guilty until proven innocent
Nope, use what you want as long as you can justify it, i.e. building a service in brainfuck won't fly
> You use open source as a verb
Nope, all development done in the open and service source code licensed under MIT
> Working in the open is a novelty, not a best practice
Nope, see above. We're spending taxpayer money, the software belongs to the taxpayer and we want to be fully accountable.
> Speaking at conferences is tightly controlled
Nope
> Geeks are the bottom of your food chain
Nope. Quite frankly the opposite. We have the best equipment in the department, are amongst the best paid, and wear whatever we want to the office where all other stuff seem to be required to wear business dress.
> Culture only happens outside of your working hours
Nope. As we are spending public money we can hardly have an open bar but we do our best
> You measure your hiring process in months
Nope, the slowest part of the hiring process is having a background check, which takes a couple of weeks
> Onboarding is an afterthought
Nope, you're up and running with all your brand new kit and logins on day 1
> Recruitment is unheard of
Nope, but the department has largely grown through referrals
> You block half the internet
Nope, nothing is blocked whatsoever
- pigscantfly 11y agoJudging by the author's resume, which includes university and work in DC, he's criticizing US gov't tech culture. It's nice to hear that things are better in the UK, though.
- alexbilbie 11y agoI worked in Higher Education for 4.5 years in the UK and this article was very much a blast from the past. Some universities really got it but I distinctly remember being told by the head of IT at a top London university that developers had no place in his opinion. Unfortunately the funding to JISC was heavily cut a few years back and the Dev8D community that had developed (made up of developers at many institutions) lost its momentum to budget cuts and bureaucracy.