Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The answer, I'm afraid, is it depends. It depends on the kind of application and the kind of users you have. Without knowing what the system is and the scope of the changes in the version, it is difficult to offer an answer. </p> <p>That said, there are some rules of thumb.</p> <p>Firstly, avoid the big bang launch. Any launch of a system is going to have problems. The industry is littered with projects where people thought the bang-bang launch was a great idea, only for teething problems to bring the launch to its knees. <a href="http://en.wikipedia.org/wiki/Anna_Patterson" rel="nofollow noreferrer">Cuil</a> was a recent high-profile causality of the big-bang launch.</p> <p>In order to make the teething problems manageable, you need to work with small numbers of users initially, then slowly ratchet up the number of users. </p> <p>Secondly, the thing that you must absolutely must positively do is <em>put the user first</em>. The user should have to do the least amount of work possible to use V2 of the system. The ideal amount of work would be zero. </p> <p>This means that if you pick to slowly migrate users from one system to the other, <em>you</em> are responsible for making sure all their data and settings are migrated. For example, don't do anything stupid like telling the user they must use V1 for all records before 12/09/2008 and V2 for all records after.</p> <p>The point of releasing V2 should be making the users' life easier, not making it needlessly more difficult. </p> <p>Thirdly, have a beta program. This applies even for Intranet applications. Developing an application is much like Newton-Raphson's method for finding the root of a polynomial. You make a guess of what the user wants, you deliver it to the user, the user provides feedback and slowly but surely each iteration takes you closer to the solution to the problem.</p> <p>A beta program will help you find the root much faster than just foisting new versions on to people without time for them to comment on the changes. Betas help get your users on-board earlier and make them feel included in the process; the importance of which I can not stress enough.</p>
    singulars
    1. This table or related slice is empty.
    1. POImplementing large system changes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSimon Johnson
    1. USSimon Johnson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POImplementing large system changes
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload