Skip to content

Comment on The dangers of letting algorithms make decisions in law enforcementparent

Comments

I agree. It seems like it's a design problem, for her at least. When I read this I couldn't help but think of AKO (Army Knowledge Online), which, ostensibly, is supposed to be the Army "one source" for soldier information. It's basically a website made in like 2001 or something, before mobile internet was a thing. No one building/managing the site is paying attention to how people actually interact with it, otherwise they'd notice that the links people most often click on are at the least accessible point. And that it's just a hideous website, to start with.

It seems to be a recurring theme here that when citizens interact with government technology they are met with a UI that doesn't make sense or that doesn't work for them. I think that's sad. I really want to change that...not sure how yet, I guess.

Edit: I'm for sure not trying to downplay the global implications of this post. Especially since I've seen how drone decisions actually play out. Basically, we all need to pay attention. That's all I'm saying.

That's because most government agencies don't know how to run a software project. From experience, they don't understand the requirements, don't pay attention to conflicting requirements, and often times have no choice in who they hire as a contractor (must submit 3 bids, take the lowest cost.) So what you end up with are a bunch of under paid, under qualified and under staffed people building things.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.