James is a JavaScript Developer, Speaker, and Teacher with a passion for teaching developers through content. He is a full-time Technical Content Creator with years of experience in Software Developme
I mean I'm not going to "redo" the guide for a specific person... if you don't want to use Auth0 and have you have an approach that you prefer, that's totally fine.
Well, you work for Auth0 right? But your byline doesn't mention that, just "James is a Developer, Speaker, and Teacher ..."
I think you should at least retitle it "How to use Auth0 to..." and even disclose this as paid content marketing. There's a free tier and the article is very solid, so why not own it? Otherwise it just feels deceptive.
I'm a JS Subject Matter Expert (SME) that has spent the past few years spearheading curricula and teaching initiatives at colleges and bootcamps, in person and virtually.
Here's a better idea 💡. Say thanks for the great information that he took to write up (probably outside of his working hours), and if you don't appreciate that there are a lot of other articles on here for you to read.
James is a JavaScript Developer, Speaker, and Teacher with a passion for teaching developers through content. He is a full-time Technical Content Creator with years of experience in Software Developme
Ok, point taken. For what it's worth, I've updated my tagline to include my role at Auth0. That said, I only put stuff on my personal brand that I believe in. I didn't post this because I'm an employee at Auth0. I posted it because I truly believe this is the easiest way to handle authentication in Node.js. If I started a Node app tomorrow, this is what I would do. In no way was I trying to deceptively drive people to Auth0. I wrote the article and the title specifically because I believe in what it says.
I'm a JS Subject Matter Expert (SME) that has spent the past few years spearheading curricula and teaching initiatives at colleges and bootcamps, in person and virtually.
James is a JavaScript Developer, Speaker, and Teacher with a passion for teaching developers through content. He is a full-time Technical Content Creator with years of experience in Software Developme
hahah thanks! I want to be fair to people who invest the time to read and leave feedback. I can see why someone would be skeptical of an Auth0 employee writing Auth0 content as his own...but I think the people that know me better know it's because I genuinely believe in what I share on my personal platforms :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I mean I'm not going to "redo" the guide for a specific person... if you don't want to use Auth0 and have you have an approach that you prefer, that's totally fine.
Well, you work for Auth0 right? But your byline doesn't mention that, just "James is a Developer, Speaker, and Teacher ..."
I think you should at least retitle it "How to use Auth0 to..." and even disclose this as paid content marketing. There's a free tier and the article is very solid, so why not own it? Otherwise it just feels deceptive.
Here's a better idea 💡. Say thanks for the great information that he took to write up (probably outside of his working hours), and if you don't appreciate that there are a lot of other articles on here for you to read.
Ok, point taken. For what it's worth, I've updated my tagline to include my role at Auth0. That said, I only put stuff on my personal brand that I believe in. I didn't post this because I'm an employee at Auth0. I posted it because I truly believe this is the easiest way to handle authentication in Node.js. If I started a Node app tomorrow, this is what I would do. In no way was I trying to deceptively drive people to Auth0. I wrote the article and the title specifically because I believe in what it says.
That's 🆒 of you to do. I wouldn't have bothered personally.😼
hahah thanks! I want to be fair to people who invest the time to read and leave feedback. I can see why someone would be skeptical of an Auth0 employee writing Auth0 content as his own...but I think the people that know me better know it's because I genuinely believe in what I share on my personal platforms :)