The difference is, in the job interview you’re writing it from scratch yourself. On the job you have to take over from the guy who left 10 years ago and that button was designed in such a way that resizing it will add garbage data to all tables in the database and also send an email to all your customers telling them to switch providers.
It’s really not that hard. Authentication is about proving the identity of the subject e.g. logging in using information only known / in possession by the subject (password, mfa etc). Authorization is about establishing what permissions that identity has in a given context. E.g. is this identity allowed to create/read/update/delete these resources. Authorization is typically done through roles (RBAC) or more granulary through attributes (ABAC).
That wasn’t the dumb part of that submersible. Game controllers are actually really good at what they do. The dumb part is that it was built like an airplane.
Nevertheless, there is the one hidden advantage of this approach: You learn new things while trying to automate everything. Remember, that it is the journey that is important, not the destination ;)
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.