> Storing passwords unhashed may 'get the job done', but every programmer should know better.
Not every programmer has to deal with passwords, though, so the generality is it is limited.
A programmer who has spent his whole career writing computational fluid dynamics simulations doesn’t need to know anything about storing passwords, but probably would have an equally idiosyncratic idea of what all programmers should know.
I would argue that storing passwords insecurely is not "getting the job done". Following minimum industry standards can be considered a requirement of knowing how to do your job.
Maybe it should be changed to "know how to do their job well"
No, that’s a different list. What every decent programmer should know.
That's either a non-answer, or it's setting the bar awfully low.
Storing passwords unhashed may 'get the job done', but every programmer should know better.