As an author, it’s a mistake to make wild assumptions about what the reader already knows about the technology, and why it’s useful. Don’t just ‘show the rooms’, but explain why they are interesting and how they might be used.
Beyond these fundamentals, I’ve written before about the simple ‘rules’ for writing a compelling blog post, and of the need to avoid hyperbole, colloquialisms, and acronym-overload, in favour of simple, plain English that can be understood internationally.
I’ll take a moment to talk about what makes you likely to show up on Curated SQL. My expected reader is someone who has a few minutes to kill during the day and is looking for technical content. They might occasionally have more time to dig into interesting topics, but more frequently, I’m imagining somebody on a pre-lunch coffee break. To make things easier for those readers, I’m looking for four things:
With that said, I gladly accept submissions via Twitter (@curatedsql).