Home » Coding Best Practices Advice From Inexperienced Devs Might Be an Issue

Coding Best Practices Advice From Inexperienced Devs Might Be an Issue

by Jeremy Winterberg
0 comment
Reading Time: 2 minutes

Welcome New Developers!

I’m all for tearing down gatekeeping and being inclusive. Allowing others to join your community is always a good thing. But in recent years, there has been a trend of new devs trying to market themselves by creating content for other devs. They do this through blogs, instagram stories, youtube videos, DEV posts, etc.. I think people wanting to share their knowledge can be a really great thing! The more people try to build each other up the better off the whole community will be.

For example, a friend of mine, who is an engineer at Microsoft, has been posting monthly on Medium with really awesome senior level SRE advice. I gain a lot of valuable insight from him, as he’s doing work I have an interest in doing myself in the future.

However, there is a slight issue with a lot of the posts I’m reading lately. The advice is typically rather bad or misleading, and its told in a way that makes it sound like its coming from an expert. So you end up having developers adopt this into their workflow, copying bad habits, and potentially causing issues down the road in future projects they work on.

What is my advice for those making this content?

If you’re trying to make a guide for others, or intended to teach someone a topic, verify that it actually is an accurate article before posting. Reach out to a more senior level developer (anyone with more industry experience than you) to take a look at your arguments and listen to their feedback. You could also do some research to see if others have written similar content before and if people have posted counter arguments to yours. If there is a counter-argument, see what their points were and the evidence for them.

I did it, now what?

Does your article still make sense after this? Perfect, post away! If you went down the research route you could even cite it as a reference, just please DON’T PLAGIARIZE. But if it doesn’t make sense, you may want to spend some time modifying your idea, or fleshing it out further to back up your argument.

If you’re making a post sharing what you like to do in your workflow, or blog while you’re learning something yourself, don’t worry about being correct! Learning is about figuring out what works best for you.

You may also like

Leave a Comment