@alst4817

I, too, rolled my own. Then smoked it and watched cartoons for the rest of the day instead of coding 😂

@felipesharkao

I really don't like all the "you shouldn't roll your own X". They make it seem that there are these programming wizards that deal with the hard stuff and you should do it because your not one of them

But I like your argument better. It just takes a lot of time that you could be building your actual project.

@adeptusnoobus

This was basically an ad disguised as an informational video.

@gpawru

When it came to implementing SSO... it unexpectedly turned into me finishing work on my own reverse proxy 🤣

@sm5172

Well done, I hope your course goes well and becomes popular. You have a very pleasant teaching style.

@amansahani2001

I've implemented my own auth, from basic to sso and rbac, which isn't painful. It' save your lot of cost, avoids compliancy issues or conflicts with big players or clients. We always try to get less dependent on third party.

@devchthonic

I really wish there was more content on how to roll your own auth. Even for your own private projects or an open source auth. Whatever content is available is always telling you not to do it but not really getting into the crux of why not to by showing you why. Would love a freecodecamp style tutorial for this.

@vivsh.1999

This video seems like a rollercoaster ride in the mind of overthinking engineer

@deefdragon

6:06 IMO You weren't wrong on the podcast. A simple email and password system is not complicated. The thing is, you aren't building a simple email and password system. You are building a full authentication and user management suite that has strong protections in place for the host, and deals with many of the potential edge cases that exist.

@qwerasdfhjkio

honestly... laravel having it built in, and not having to paying for anything (and many other stuff built in for FREE) is the reason why I went away from go.

But I still love golang man... wish I could code on it every day and be just as productive

Laravel really does allow me to just focus on the actual features I want to build (most of the time*)

@Kumest183

I would Like to See you Test out keycloak for auth. Great videos, thank you!

@Rundik

3:40 intro ends here

@ZÏ̇̃

I love you for adding vim keybinds in the course! Can't wait for when it releases, really looking forward to it!

@skylark.kraken

Interesting, I would always recommend to people to try out rolling your own auth - don’t necessarily use it, but learn how it works. Time constraint is a totally valid reason to not bother

I’m a backend dev and I’ve rolled my own auth in every form, I personally really enjoy the process and could implement it to a project with ease - however, I would personally always go with an auth provider if the website is expected to make money, if not I’d just stick with third party logins

There’s no use case where rolling your own auth is worthwhile other than as a learning experience - but if you need to just ship it, learn it later

@skidkadda

I think people should have a separate page on their site explaining how they secure data. Like we: "We store your password as easy to read plain text"

@joshuadawson8237

I think this is a great example of the challenge in prioritizing what truly matters when building software. There are countless directions you could take, but the real question is: will this actually bring meaningful value to the end user? And sometimes, that answer isn’t so clear. You might not even fully understand what the user really needs. It's a tough reality to face—especially when you're building your own software without a product manager or business team guiding you toward the “right” path. Good Luck!

@dannyvcf

Man, I am using the same stack and it is quite funny to see you hitting the same walls I did. I also chose to roll out my own auth, because it was crucial for a very unique checkout flow I am building. It took not long to regret it.

@amine7

"rolling your own auth is hard" videos are just a disguise for shilling clerk at this point. If you're unable to roll your own auth with all the resources available today, you should probably stick to frontend. Yes, it would take two or three days, but it's part of building an app, and owning everything is worth every hour of it.

@Dan-pz5ro

Agree with what you're saying, compromise is sometimes the right answer. I'm currently rolling my own auth however in the same stack, but using JWT since I want to have the possibility to authenticate via cookies in my own htmx ui, but also have the capability to switch the auth type to Bearer for other projects that might use React for example. I think there's great benefit in rolling your own since you do it once and then you can reuse in whatever projects you require, apart from the endless customization you can do as you've pointed out. So, in the long run, don't throw out the idea completely! :) 

Oh, and can't wait to see some of the code of the platform you're building!

@kirstypollock6811

Been one of my sayings for 20 years. "Never roll your own auth" (or encryption).