Publishing Schedule

I’m quite excited to have Def-Proc online and have a huge temptation to just post everything I’ve written, as soon as I’ve typed it! However, I’m aware that the internet prefers new material to old, and that posts need time at their top of the list to have a chance of reaching an audience. Too much content, delivered too close together ends up as a jumble, and swamps its self—so then you’d be left with a huge gap while I actually went and did some engineering!

To try and even things out, I’ll be posting to the Def-Proc blog with an article every Thursday. I could post more frequently, but that would leave me rather less time to be an engineer; and I don’t want to post less frequently, i.e. only when I release/complete/update a project, because that undermines the transparency of being open source.

So as not to upset my publishing schedule, and delay any articles unnecessarily, I’ll have a Monday slot at irregular intervals for additional content. Usually these will be shorter form posts or announcements (like this one), or project notices.

If that’s not enough Def-Proc for you, you can follow me on twitter, @DefProc

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>