Auth Is Auth

The eternal comedy of our industry: Manager wants a feature for "authorized paying users" but tells dev to "implement authentication." Dev with actual security knowledge asks the critical question – authentication or authorization? – only to be met with blank stares and "There's a difference?"

For the uninitiated (and apparently the manager): Authentication is proving you are who you say you are (login/password). Authorization is determining what you're allowed to do once identified.

The final panel showing the desperate Google search is the universal developer coping mechanism after 10 years of explaining this distinction to people who'll forget it by the next sprint planning.