This post is indeed heavily inspired by Akshay Saini's Namaste JS series - examples, flow of concepts etc. It would have been great if the author had included a line in the post instead of sharing link to the playlist in the comments section.
Still, can't call him the 'content owner' as the first commenter did though. This poster has taken common knowledge about javascript and taken the time to visually express it in a unique way. He also linked to his source of knowledge in the comments as you say, which he didn't need to do.
Does that mean every time I create a website and put my name/logo in the footer, I also need to mention the 300+ resources that have taught me something or inspired me....no.
Namaste js, most likely learnt it from somewhere too, maybe one of the many books he has on his desk in the bg, does he give them credit? He often is reading something in his video, probably words of others, does he give credit?
Yes, I agree that Namaste JS is not the content owner - and the first commenter is not right to phrase it that way. And I totally agree on the great efforts in creating engaging visuals.
However, when almost the whole content of your post is this particular video in the playlist - it doesn't really hurt to mention it in the Reference section in the post.
There's clearly a difference between writing tech tutorials inspired by a lecture series, and developing a website.
When writing tech tutorials, it's often a good practice to mention the references.
It's totally fine if you don't quite feel the need to acknowledge. I only wanted to get across my message.
You can submit posts here for a wider reach to the JS devs. And there's a Medium publication JS in Plain English - that'd be a great place to share as well. And then, include the canonical url in the dev.to posts so that we can read it here too.
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.
This post is indeed heavily inspired by Akshay Saini's Namaste JS series - examples, flow of concepts etc. It would have been great if the author had included a line in the post instead of sharing link to the playlist in the comments section.
Still, can't call him the 'content owner' as the first commenter did though. This poster has taken common knowledge about javascript and taken the time to visually express it in a unique way. He also linked to his source of knowledge in the comments as you say, which he didn't need to do.
Does that mean every time I create a website and put my name/logo in the footer, I also need to mention the 300+ resources that have taught me something or inspired me....no.
Namaste js, most likely learnt it from somewhere too, maybe one of the many books he has on his desk in the bg, does he give them credit? He often is reading something in his video, probably words of others, does he give credit?
Yes, I agree that Namaste JS is not the content owner - and the first commenter is not right to phrase it that way. And I totally agree on the great efforts in creating engaging visuals.
However, when almost the whole content of your post is this particular video in the playlist - it doesn't really hurt to mention it in the
Referencesection in the post.There's clearly a difference between writing tech tutorials inspired by a lecture series, and developing a website.
When writing tech tutorials, it's often a good practice to mention the references.
It's totally fine if you don't quite feel the need to acknowledge. I only wanted to get across my message.
Noted and rectified my mistake😄! I thought adding references on the comments section will be sufficient.
Thank you for accepting the suggestion positively. ☺️ You're doing an amazing work. Have you considered submitting your posts to javascriptkicks.com?
I didn't knew about this website, I will consider looking into it, Thanks😄
You can submit posts here for a wider reach to the JS devs. And there's a Medium publication JS in Plain English - that'd be a great place to share as well. And then, include the canonical url in the dev.to posts so that we can read it here too.