Create templates to quickly answer FAQs or store snippets for re-use.
Hi Brian! This article is great and I absolutely needed it seeing as I just completed editing a technical article I wrote. I was really conscious of a few things.
I had a few concerns and I'll like to know what you think.
When writing a post that has heavy technical content i.e code blocks. What do you recommend?
Thanks Egwuenu! For the code blocks, if the entire block isn't relevant to the discussion, I'd include only the relevant portion and a link to GitHub for the full source. Sometimes I even replace irrelevant portions, like inner code on functions or elements, with a ..., though this should be used carefully as some may find it confusing if it hides a portion of code that would improve their understanding.
Alright Thank you.
I think we should always strive to make it easy to understand besides avoiding technical jargon.
Indeed, if it can be said simply then it should be said simply.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.