Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I've been putting various nuggets of software live recently. Either directly or handing over to the client. In all cases I've kept to my personal rules about launching or handing over major work and I wondered what rules of thumb people followed here.

This isn't about programming practise per se. At this stage you've built and (hopefully) tested the software.

So, I generally do this:

Never put it live on a Monday or a Friday
There is more to this than the Monday drag or the excitement of the impending weekend
Where I work changes to systems occur over the weekend, should they affect your work you'll need Monday to check. Also, people may be ill and you'll need that day to recommunicate to the intended management/audience.
No one likes working late on a Friday. Ideal world aside, if something goes wrong with your deployment you need help around to help diagnose and fix it. You have an extra working day where most people will be in the office.
Avoid going live at a specific time
Picking a time of day is fraught with danger. If you can, make the system 'pre-live' where only the most minor of changes are required at this point in time. Like switching internal ip addresses (etc). DNS changes always take time to propagate so a fixed time launch for a site would need a launch page (hence the minor change rule).
Don't put things live first thing in the morning
Well for a start you don't know if anyone is going to be late for work. Traffic (etc).
If you can, have the existing system still in place
Sometimes, the best contingency is to be able to fall back to the existing system while you fix any problems. Back out any minor changes and you are back where you started. Diagnose, fix and try again.

So for me, currently, Tuesday to Thursdays from 11:00 to 4:00 are the ideal times to put things live. I am lucky, though, that I do have a major say in how these things proceed.

In reply to OT: When to put things live by simon.proctor

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others about the Monastery: (7)
    As of 2018-06-20 13:09 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (116 votes). Check out past polls.