Click here to monitor SSC


Write for us

At Simple-Talk, we are always keen on publishing new and interesting views and ideas. We try to keep coming up with fresh ways of presenting information.

Subject matter for Simple-Talk will generally be chosen because it will interest professional IT people in businesses. Although we like to feature technologies, we are also likely to be interested in issues that affect IT, such as ethical considerations, security, workgroups, management and career development. Our interest in Microsoft-based technologies reflects the ubiquity of such technologies in the workplace, but we’re keen on the broader picture too. Simple-Talk is Red Gate’s website, so we have a great opportunity to pester Red Gate staff into writing about their area of expertise and their work. This has been very useful in increasing our coverage of important topics that are poorly covered on other sites, such as design, testing, technical authoring, and usability.

Our articles come from a whole range of writers. We are delighted to find that many people will submit articles to us for publication: usually, these articles contain ideas and insights from busy IT professionals. Sometimes, our eye is caught by some exceptional writing on a blog or forum, and we ask the author if they’d like to contribute. Quite often, we meet potential authors at one of the conferences. We also use professional writers so as to get a good mix. However,  we believe that the people doing the work with these technologies can explain technical matters precisely and with relevance, in ways impossible to professional trainers. We’d like to encourage them.

To this aim we:

  • Help authors by editing, guiding and mentoring submissions in order to provide articles of consistent quality that people want to read.
  • Pay for articles so as to provide a measure of recompense for the work.
  • Feature finished articles in the newsletter that goes out to over 200,000 recipients.
  • Include the best articles in Simple Talk eBooks.

We want to make absolutely sure that all the articles we publish will be well-received. For this reason, we put all articles through a fairly rigorous process. The articles go through a technical review and a technical edit, and we sometimes ask authors to do substantial revisions for their second draft. When the author submits a second draft we will do a final edit, which includes a copy edit. This allows us to ensure that articles are correct, cover the subject, conform to certain rules that make them easier to read and understand, and are of the highest quality we can achieve. We have a group of volunteer technical reviewers who help out with peer-reviews, and we frequently call on Red Gate staff (more volunteers are always needed!).

The authors submit their articles in Word format, so we can track all the changes and allow authors to accept or reject our revisions. It also allows peer-reviewers and editors to add comments. We then ‘set’ the articles in HTML in one of a range of styles, ready for publication and schedule it. At this stage, we usually check the ‘proofs’ of the article as it will appear, with the author.

In return for the extra demands we place on our authors, our remuneration rate is quite high, and depends on length, technical depth and so on.

In summary: In exchange for your work in writing for us, we can offer you

  1. Remuneration: You get paid
  2. Exposure - your content published on Simple-Talk
  3. Recognition - we include a short bio for each author
  4. Traffic - reciprocal link to your site or blog
  5. Formatting and Editing of the submitted content

Time between first draft submission and publication can vary between 2 weeks and 2 months, depending on the extent of revisions required and the number of articles we currently have in the pipeline.

If you would like to share your programming experiences, or your specialized expertise, with the Simple Talk community, then please contact us - we're always particularly keen to find SQL Server developers and administrators, Exchange or Sharepoint Administrators,  and .NET developers who are willing to share their hard-won knowledge with the Simple-Talk community. Before you submit an article to us, please make sure that it is your original work and has not been published elsewhere. By this we mean that you have not copied code, images, or text from a book or web posting by someone else. We check carefully, and will never use an author who we find has done this on any of Red-Gate's sites.

Simply send an email to editor@simple-talk.com telling us what you would like to write about, and a little about yourself and your experience.


Please note that the editors have used their draconian prerogative in the defence of simple and precise English, and have banned the use of the following words and phrases on Simple-Talk....

  • scenario
  • schema (when used as a synonym for 'thing') 
  • Must-Have (or Must-Anything) - This is a Must-Edit
  • synergy
  • ideation
  • going forward
  • cascade
  • pre-plan
  • low-hanging fruit
  • leverage
  • actionable (unless used in the dictionary legal sense)
  • ecosystem (unless in the ecological sense)
  • Environment (No, that is what is outside) 
  • addressing issues / concerns
    (when used as a euphemism for ' solving problems')
  • newbie (we are all newbies)
  • vibrant
  • Simplexity
  • Swing the pendulum
  • Reach out (meaning contact) 
  • think outside the box
  • FOOBAR (It wasn't really even funny in the 70s)
  • real-world
  • resonate
  • resonance
  • going forward
  • performant
  • pre-emptive (in the non-technical sense) 
  • non-trivial
  • learning curve
  • the big ask (other than a film title)
  • core issue
  • easy to use (Isn't anything?)
  • robust
  • intuitive
  • intelligent
  • a no-brainer
  • state-of-the-art
  • flexible
  • low-cost
  • seamless
  • monetize
  • gaining traction
  • the worst case scenario of ...
  • going pear-shaped
  • global

We'll have no more references to the film 'the Matrix' or 'Star Wars' in Simple-Talk articles. Enough is enough.

Also, it is editorial policy to avoid the over-use of  word such as 'Available', 'capturing', 'migration', 'process',  'performance', and 'multiple'. Soporific eh? In fact, the over-repetition of any word makes the experience of reading articles more tedious. 

For more hints on writing for Simple-Talk see the following articles.

The Simple-Talk Author's Style Guide

Simple-Talk Book Reviews

How to Write an Interesting Technical Article.

Tips on Google 'Authorship' and 'Reputation'

Latest articles

Managing Printers with Group Policy, PowerShell, and Print Management
 Just because it is possible to do many configuration jobs 'click by bleeding click', doesn't mean that... Read more...

PowerShell One-Liners: Variables, Parameters, Properties, and Objects
 PowerShell isn't a conventional language, though it draws inspiration widely. Many people learn it, and... Read more...

SQL Server XML Questions You Were Too Shy To Ask
 Sometimes, XML seems a bewildering convention that offers solutions to problems that the average... Read more...

Searching for Strings in SQL Server Databases
 Sometimes, you just want to do a search in a SQL Server database as if you were using a search engine... Read more...

Handling Errors Effectively in ASP.NET MVC
 ASP.NET MVC gives you more options in the way that you handle exceptions. Error handling isn't... Read more...

Why Join

Over 400,000 Microsoft professionals subscribe to the Simple-Talk technical journal. Join today, it's fast, simple, free and secure.