Hey CJ, I'm an AA alum from like ten years ago. Crazy to bump into your channel while looking at how to roll auth in brand new apps. Glad to see you're still killing it!
Hey CJ - Thanks for the video! I am, however, having a bit of an issue here. I followed all instructions and end up with this rails error : 'No route matches [POST] "/auth/auth0"' I found some stuff online that wasn't very helpful. Have you had any experience with this issue? Thanks in advance!
Couple of constructive suggestions: 1. dark mode videos like this are almost unwatchable for viewers in high ambient light environments (such as outside). The contrast between syntax highlighted colors and the background is much lower for dark mode, so it doesn't work well when viewed in bright environments. Conversely, light mode is more viewable by anyone anywhere... and people watching in a dark room can always turn their screen brightness way down. 2. using copilot while doing tutorials is probably not ideal as it presents unnecessary or even wrong information to your viewers - if only briefly. Keep in mind that viewers may be observing the video slightly less than 100% of the time as you do live coding, meaning they will see snapshots in time. Some of those snapshots will simply be wrong because of copilot. It then becomes necessary for the viewer to watch carefully to catch the "final" version of your code snippet so they see what's correct rather than what was close but wrong.
My god, can you use an understandable editor like vscode? I don't see the point of using a mac if you're gonna use a shit text based editor made for wannabes.
Haha. You realize VSCode is also a text-based editor. The fact that it has GUI elements outside of the text area does not mean it is also not a text editor. Text is text. VI (vim) makes it possible for us to write and edit that text faster than a simple text editor. Most of the foundations of the Mac you use were written by developers using VI. Lastly, VI (modernly known as vim) is the opposite of "made for wannabes". It's made for high performers, and it has a moderately steep learning curve. But once you know it pretty well, you can be a much faster developer and type a lot fewer keystrokes to be productive compared to a normal beginner using a single-mode editor (like default VSCode). Incidentally, there's a good vim plugin for VSCode which allows you to get most of the benefits of vim while using the VSCode framework.
@@ThePazuzu Hehehe. Unless you're going to argue that Emacs is better than VI... which is a worthy debate and one I could take both sides on personally, you should just stop. People can and should use whatever tools and IDEs suit them best. But without a doubt, the more experience you have with more tools, the better informed choices you can make to be productive. In this video, he's clearly got his vim well tuned for his needs. There was nothing he was doing which was lacking because of no extra UI around it. In fact, if you have a good memory of your project structure and filenames, I promise you that you can move faster and get more work done in pure vim than with any gui tool. It's just a super powerful, succinct editor which also happens to be able to do tons of other things... even before you use addons. Likewise, the same can be said of Emacs. And to a lesser degree, VSCode. Arguing with people on the internet is stupid, so I'll end my side now. There's nothing else to talk about anyway, because you're just plainly wrong.
@@zed9zed Sigh... It looks like shit. Graphical interfaces make it so that I don't need to remember exactly how I named a file or where I saved it. The only use cases for text-based editors are 1.- when SSHing into a headless terminal. 2.- When you're old school and grew up with them and can't get used to anything new. 3.- When you're an insufferable wannabe that can't ever shut up about it.
![[Vowel]물고기는 물에서 살아야 해🐟🤣Fish have to live in the water #funny](http://i.ytimg.com/vi/3G9MH063Cx4/mqdefault.jpg)
Hey CJ, I'm an AA alum from like ten years ago. Crazy to bump into your channel while looking at how to roll auth in brand new apps. Glad to see you're still killing it!
haha. glad to hear from you, Seth! 🙌
This is great! Thank you
You're very welcome! Thanks for watching.
Second! 💖
1st here, thanks CJ
How do we implement Auth0 social login for Rails api only app?
Hey CJ - Thanks for the video! I am, however, having a bit of an issue here. I followed all instructions and end up with this rails error : 'No route matches [POST] "/auth/auth0"' I found some stuff online that wasn't very helpful. Have you had any experience with this issue? Thanks in advance!
Sounds like omniauth might not be installed? That error means there isn’t a route defined. Could also be some missing mount in routes.rb
Couple of constructive suggestions: 1. dark mode videos like this are almost unwatchable for viewers in high ambient light environments (such as outside). The contrast between syntax highlighted colors and the background is much lower for dark mode, so it doesn't work well when viewed in bright environments. Conversely, light mode is more viewable by anyone anywhere... and people watching in a dark room can always turn their screen brightness way down. 2. using copilot while doing tutorials is probably not ideal as it presents unnecessary or even wrong information to your viewers - if only briefly. Keep in mind that viewers may be observing the video slightly less than 100% of the time as you do live coding, meaning they will see snapshots in time. Some of those snapshots will simply be wrong because of copilot. It then becomes necessary for the viewer to watch carefully to catch the "final" version of your code snippet so they see what's correct rather than what was close but wrong.
Thanks for the suggestions! Really appreciate the feedback.
Nice
Hey CJ I am using active scaffold gem and I dont want login button for login how can I acheive that functionality ?
Haven’t heard of the active scaffold gem.
lol i am late, third 🙌
My god, can you use an understandable editor like vscode? I don't see the point of using a mac if you're gonna use a shit text based editor made for wannabes.
Haha. You realize VSCode is also a text-based editor. The fact that it has GUI elements outside of the text area does not mean it is also not a text editor. Text is text. VI (vim) makes it possible for us to write and edit that text faster than a simple text editor. Most of the foundations of the Mac you use were written by developers using VI. Lastly, VI (modernly known as vim) is the opposite of "made for wannabes". It's made for high performers, and it has a moderately steep learning curve. But once you know it pretty well, you can be a much faster developer and type a lot fewer keystrokes to be productive compared to a normal beginner using a single-mode editor (like default VSCode). Incidentally, there's a good vim plugin for VSCode which allows you to get most of the benefits of vim while using the VSCode framework.
@@zed9zed Found the wannabe.
@@ThePazuzu Hehehe. Unless you're going to argue that Emacs is better than VI... which is a worthy debate and one I could take both sides on personally, you should just stop. People can and should use whatever tools and IDEs suit them best. But without a doubt, the more experience you have with more tools, the better informed choices you can make to be productive.
In this video, he's clearly got his vim well tuned for his needs. There was nothing he was doing which was lacking because of no extra UI around it. In fact, if you have a good memory of your project structure and filenames, I promise you that you can move faster and get more work done in pure vim than with any gui tool. It's just a super powerful, succinct editor which also happens to be able to do tons of other things... even before you use addons. Likewise, the same can be said of Emacs. And to a lesser degree, VSCode.
Arguing with people on the internet is stupid, so I'll end my side now. There's nothing else to talk about anyway, because you're just plainly wrong.
@@zed9zed Sigh... It looks like shit. Graphical interfaces make it so that I don't need to remember exactly how I named a file or where I saved it. The only use cases for text-based editors are 1.- when SSHing into a headless terminal. 2.- When you're old school and grew up with them and can't get used to anything new. 3.- When you're an insufferable wannabe that can't ever shut up about it.