Je cherche à vous aider à atteindre vos objectifs #code en #français . My goal is to help you work faster by sharing what I know about #SQL, #Python, and #Salesforce in #English and #French
Je cherche à vous aider à atteindre vos objectifs #code en #français . My goal is to help you work faster by sharing what I know about #SQL, #Python, and #Salesforce in #English and #French
In general, it's best practice to write the author's name down when sharing their work, even w/o a fancy link like these, so that people don't think you're spamming trying to get "clicks" for yourself using other people's writing.
It's also great for those authors' careers to give them a signal boost as people you think do quality work!
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.
Okay, so this post is just surfacing a link to a long tutorial that Katie Silverio wrote, without crediting her, so not thrilled about that.
But it's exactly the tutorial I'd been looking for to flesh out a "further reading" footnote, so thanks for bringing it to my attention. :) :P
Katie Silverio
Hi! I'm new to dev.to, how did you add someone's profile to your message like that? Will do it in the future!
Hi, Brendan! Welcome to DEV!
{% user brendanmcd96 %}From dev.to/p/editor_guide
In general, it's best practice to write the author's name down when sharing their work, even w/o a fancy link like these, so that people don't think you're spamming trying to get "clicks" for yourself using other people's writing.
It's also great for those authors' careers to give them a signal boost as people you think do quality work!