31 ms·
I worked for city government once. I hated it. I had zero autonomy and thus zero impact. The team I worked for struggled to accomplish the most basic software
by sosodev 3y ago
I worked for city government once. I hated it. I had zero autonomy and thus zero impact.
The team I worked for struggled to accomplish the most basic software tasks. They didn't even use source control. Everybody just zipped project files and emailed them to each other.
- willcipriano 3y agoWhen I worked for government the team I was on lost members every couple of weeks. Eventually I was the last developer on the team joined by 4 managers. I also gave notice and on my last day they held sprint planning talking about the devolpment work they wanted to complete in the next sprint, they shuffled the tickets around asking me how long I think they will take, after a while I asked "As you all know, today is my last day, wouldn't it be better to look at this once you've hired someone?" and the presenter of the meeting got red faced and quiet and started typing rapidly and loudly. After an awkward silence the meeting abruptly ended and I never heard another word.
- sshine 3y agoA friend works with software for the city. Took him a year of part-time work to get a basic web app made and deployed on Azure. He’d always complain that all his colleagues were incompetent save a few. I asked him why he doesn’t get a more ambitious job, but he likes how little results he can get away with delivering. I wish government jobs paid better.
- wombat-man 3y agoYeah that's the tradeoff. I like working with very competent people but it's effort every day to stay on top of things.