Authentication, Authorization, and Football

BK — Sun, 14 Nov 2021 17:18:38 +0000

It’s Sunday fun day, let’s take a casual look at authentication vs authorization. More importantly, what's the difference? Since it’s Sunday and is football season, I’m going to give you a loose analogy. I think that we need to nail down our idea of both authentication and authorization. So let’s break this down: Authentication verifies who the user is while Authorization determines what resources a user can access. I’m a Las Vegas Raiders fan. Let’s say I’m going to a Raiders home game. I’m at the Allegiant Stadium gate, I show them my ticket. I walk in at that point I become authenticated. The next step is I want to go and see where my seat is located. When I sit down in my seat then I become authorized for this seat. I realize that I have some time before the game so I want to walk around. I’m authorized to get concessions, souvenirs, stores, other permitted areas, and even the restrooms. I’m only permitted to the men’s restroom or family bathroom. I’m not authorized to go to the women’s restroom. There are a lot of places that I’m not authorized or permitted to go to. Unfortunately, I don’t have access to the owner’s box. I can’t tell Mark Davis my thoughts about the team and what he should do next. I think though I’ve played enough Madden that I think I would be an amazing general manager or at least an offensive coordinator. There are a lot of places that I can’t go to, locker rooms, sidelines, and various locations. When you think about authentication this verifies who the user is. Think this is my login. I have access to this website. Authorization determines what resources a user can access. I hope everybody's prospective team wins, except the The Chief they are paying the Raiders. It’s Raider Nation For Life over here.

Until the next time #KeepBringingThatFullStackEnergy

A Developer's Willpower

BK — Wed, 03 Nov 2021 23:13:29 +0000

One thing about me is that I love comic books. I’ve been collecting comic books since I was able to read. Since this is “New Comic Book Wednesday”, I started to think about what heroes would be amazing software developers. At first, I have the usual suspects: the heroes that have high IQ. We have characters like Tony Stark, Bruce Wayne, Peter Parker, etc. that technical acumen that they would excel as software developers. I see a lot of lists of traits for the ideal software developer. I’m listing some of those prevalent traits problem solving, passion, creativity, quick learner, honesty, patience, communication skills, open-minded, overly helpful, attention to detail, stress handling, laziness, flexibility, well organized, open for criticism, likes to create, handling failures, embrace trends, a technical mindset, business perspective, self-confidence, and love with technology. I never saw willpower in those lists. If a developer has willpower you can easily handle stress, failures, and setbacks. The hero that has a lot of willpower is Hal Jordan the Green Lantern. I think Hal would be an excellent developer. He could even have his own developer oath "In brightest day, in blackest night, No bug shall escape my sight. Let those who worship evil bugs might. Beware my power--GitHub’s green light!" On your journey don’t forget to develop grit and willpower that help you get through those tough times. For without willpower, I won’t be the developer today.

Until the next time #KeepBringingThatFullStackEnergy

DEV Community: BK

Authentication, Authorization, and Football

A Developer's Willpower