Gotta be the RegEx classic: xkcd.com/208

Working from home for so many reasons. I love being able to spend extra time with my dogs and my wife, cook more, workout more, etc.

Auth0's philosophy of "Work is a thing you do, not a place you go" has a bunch of amazing ramifications, so I'd agree with James that really the big perk is working from home.

• VS Code + Prettier
• OmniFocus (not a dev tool but keeps me sane)
• Ulysses (writing app)
• iTerm
• Using Bash with aliases: github.com/samjulien/dotfiles

Chrome - browser VS Code - editor for EVERYTHING (extensions - Cobalt 2 theme, Git lens, React snippets, live server, live share, prettier, settings sync) Postman - sending API requests Hyper - terminal Figma - design Grammarly - grammar checking Notion - notes

jamesqquick.com/uses

The best way to learn is to build stuff! Hands down, my biggest piece of advice. Build continuously. I also spent lots of time watching videos, reading articles, etc. I'm always learning. I use YouTube and Udemy as two of my two most used resources.

If you have any projects that you build and want to share, please do!

Find yourself a community whether it's in person, online, etc. Find people who you can talk to to ask questions, have conversations, etc. Also, find people that you can learn from! I personally use Twitter as my tie in to the online developer communities.

• Like James said, focusing on building things
• Think small -- try to solve little problems for yourself and celebrate those wins
• Don't overthink it -- when you're starting out, the language/framework doesn't actually make that big of a difference other than whether you're using types and a compiler. Just focus on enjoying what you're learning, not doing something out of obligation or because it's "what the cool kids are doing."
• Find someone to hold you accountable and encourage you!

Okta, Ping, AWS, Cognito, Firebase, Netlify Identity

Sometimes during talks, people can be a little abrasive with asking questions so those can be intimidating at times. I started as an Evangelist at Microsoft fresh out of college, so it was really difficult at times to give technical talks/presentations to developers who had been writing code as long as I had been alive :) I don't have too much of a problem with that anymore. I'm comfortable saying "I don't know" lol

A big challenge for me is just prioritizing projects and time management. I feel like I'm just now starting to get the hang of it thanks to things like block scheduling and apps like Focus (heyfocus.com).

What makes a good dev advocate and the necessary skills are somewhat the same:

• Loves to teach
• Loves to help others
• Good at public speaking (very much a skill you can learn though)
• Constantly learning

If that's you, find some positions and apply. Dev Rel is a rapidly growing field.

Specific things I wanted

• younger culture
• startup feel
• surrounded by smart and passionate people
• trust in employees to do the right thing
• transparency

I found them all :)

I really value when companies trust their employees to do the right thing and respect them as adults. Auth0 has a really collaborative, trusting, and transparent culture. I could hardly believe it when I started. I was really worried about being micromanaged at my first remote job and it was very far from that. If anything, people will warn you you're not taking enough time off.

I was really looking to get back into speaking, creating content, etc. A friend of mine knew a few people at Auth0 and told me how great they were. This helped me feel confident I was making the right decision!

I don't think I can address this one specifically, unfortunately :( I can say that 60% of our employees work remotely so office footprint isn't as big as you might think.

This is probably the most detailed source I could find.

auth0.com/blog/auth0-architecture-running-in-mult…

This is probably the most detailed source I could find.

auth0.com/blog/auth0-architecture-running-in-mult…

This is probably a much better read vs me talking about it

auth0.com/blog/the-developer-first-identity-platf…

I lucked into a position at Microsoft as a Developer Evangelist. I had no idea what Evangelism before joining there. I realized I love the things that came along with it: talking to people, teaching, speaking, creating content, etc.

There's not really a specific day to day. It varies every day, especially now with everything going on in the world. Here's a few of the things we do.

• teaching, speaking, creating content, talking to developers, learning about Identity, building demos, collaborating with other developers

Growing Auth0

• Jwt.io
• Starting to do live streams
• Speaking at and sponsoring conferences
• Many libraries and sdks

I'm a self-taught developer, got my first full-stack job about 5 and a half years ago and mostly focused C# and JavaScript (especially Angular). I launched a video course in 2018 called upgradingangularjs.com and started writing guest posts about it a bunch of places, including Auth0. They reached out to me about a full-time content job and I jumped at the chance and joined in August 2018. Then about August 2019 Auth0 re-organized the Marketing department, and it made sense for me to move over to Developer Relations since I was doing a lot of speaking at conferences as a Google Developer Expert.

Our day-to-day is usually focused on applying at and speaking at conferences and meetups, but these days we've shifted to mostly remote: remote conferences and meetups, podcasts, Twitch streaming, etc. We also build programs like Auth0 Ambassadors (auth0.com/ambassador-program).

Building the community happens through a number of ways:

• Teaching through conferences/meetups/etc (whether identity or otherwise)
• Our community forum (community.auth0.com)
• Open source libraries
• Tools like jwt.io
• The Auth0 blog (auth0.com/blog)

I'm sure I'm forgetting something in there, too. Hope that helps, feel free to ask me whatever on Twitter (twitter.com/samjulien).

Working from home has been a part of our culture from the beginning so it's relatively natural for us. Here's a few things we do

• use video calls often (especially after a few minutes in chat)
• use a lot of slack (much better than I ever thought it would be)
• reimburse for home office equipment
• flexible schedule - we have the ability to take care of errands during the day, pick up kids, etc.
• we just started doing weekly calls for fun activities like trivia night

Thanks for sharing these tips, I really like the frequent video calls and trivia nights :). James Q Quick

The problem Users have to remember passwords across many apps, so they reuse password Companies are requiring more complex passwords which are hard for users to remember Having to change passwords every x # of days is tough IT is getting tons of password reset requests

The solution Passwordless logins gets rid of the need to remember multiple different complex passwords Allowed to login with magic email link, biometric, physical device, token from app, etc Something I have, something I know

Thanks a lot, this is really a great innovation in terms of authentication James Q Quick

Just clarifying whether you mean Auth0 is hard to understand or OAuth is hard to understand specifically? If Auth0, have you follows any quick starts, docs, etc. that you have feedback on?

OAuth and other workflows can really be difficult to understand. One of the benefits of an identity provider like Auth0 is that they have the expertise and deep technical knowledge so that you don't have to understand it all. The quickstarts and sdks are created to make your process as a developer when implementing Auth0 as easy as possible.

The free tier is meant to be pretty generous. Ideally, it should last you for a while. Then, as you scale to the point where you need a paid service, hopefully you're generating money by that point. I had this same question about using Headless CMS options, and the overwhelming response was that free tiers are generous enough to get you where you need to be.