3 ms·
Anecdotal, I know, but the saddest interview I’ve ever done was a state government web developer. I was writing a js on the whiteboard, setting up a problem tha
by wincy 5y ago
Anecdotal, I know, but the saddest interview I’ve ever done was a state government web developer. I was writing a js on the whiteboard, setting up a problem that started something like
var a = 1;
a = 2;
Before I got any further they blurted out “that’s false! The second line is false” and this was someone who had been writing production code for the government for the last five years.
I honestly just felt really bad for them, more than anything.
- bumby 5y agoI wonder how much of this is due to being forced to select lowest bid contractors. I’ve seen some orgs rely on rely bad programmers because they were relatively cheap. Programmers who make changes on the fly in meetings to live production systems or say their test plan is to push it to production and just wait for customers to send in work tickets when they encounter a bug. Or blatantly lie about feasibility because they would prefer to work in an antiquated framework rather than learn a new one. The govt owns some responsibility for lack of technical oversight but I can’t help but think a lot of it is due to business contracting incentives.