21
sudocode
52d

Sins of a goddamn tech author:

1, Writting with NO ABSOLUTE FUCKING ADDITION TO WHAT IS ALREADY WRITTEN A THOUSAND FUCKING TIMES!!

2, Articles with no date of publishing! Not an author issue but fuck you for writting here!

3, Using Screenshot of code instead of text. The only thing keeping you alive is the fact that I dont know where you live. I will, eventually.

4, Reaction GIFs. Lol? Haha? FUCK YOU!

Comments
  • 6
    5, Hero banners. A tech article isn't a picture-book. Fuck you for forcing me to scroll past a mile-long image so I can actually read the goddamn article.
  • 6
    6. Clickbait titles.

    Just tell me what you're talking about in the title - "New features in Java 15", "Using git branch effectively", etc.

    This isn't BuzzFeed, and we don't need "OMG!! 99% of people don't know about this killer Git feature!!!!". If you want to write titles like that, piss off and write for a celebrity mag instead.
  • 7
    0. Missing sources or references

    Simply turning the whole post into an unverifiable piece of biased shit.

    (this is a must, hence 0. This _should_ point to a specific version If necessary, so it's obvious to which version your article applies.)

    7. Abbreviations. Explain them.

    Do not assume that someone can deduct which specific abbreviation you had in mind.

    8. Structure. There are things like paragraphs, sections, italic / bold font style... A wall of text is unpleasant.
  • 5
    Can we just go back to calling them bloggers? Calling them tech authors is giving them far too much credit.
Add Comment