Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm a big fan of mix-and-match, and an incremental change of the development process. I agree that iterative development should be your first goal, but I think you can approach it in even smaller steps.</p> <p>From my experience, I would recommend the following order - pick the first you don't do already:</p> <ul> <li><p><em>Fix Bugs First.</em> I wish I wouldn't have to say that. This is the call of sanity, and also required to have shorter cycles.</p></li> <li><p><em>Small steps.</em> Train the habit of implementing the smallest change that is a visible step towards the next feature, then compile and test. Break down all your tasks into &lt;1h units before starting to code. Aim for buildable, functional code at least every 15 minutes. This doesn't require much infrastructure change - except maybe fixing the incremental build and having fast machines.</p></li> </ul> <p>Yes! Start with making sure developers have fast machines. How much better advise could get?!</p> <ul> <li><p><em>Build Everything Daily.</em> Set up a double-click full builds from Source Control to installation medium, ideally on a separate PC. This are the first step to the frequent builds, but they help a lot on their own already. For us, it was a crucial step in getting reliable, reproducable build results.</p></li> <li><p><em>Start writing Unit Tests.</em> Don't bother about coverage yet, don't enforce "write tests first", but put the framework in place. Write tests for new code and changes. Then run them with your daily builds. </p></li> <li><p><em>Short Cycles.</em> Now it's the time, you have all tools in place to make weekly or two-weekly in house releases: The codebase is in a deliverable state many times a day, making the build is a double-click away, and at least something is working. </p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POAgile in small bites: most bang for the buck
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USpeterchen
    1. USpeterchen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAgile in small bites: most bang for the buck
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMy take on your advice: 1. First, do no harm. Be sure the day's activity doesn't break yesterday's. If it does, fix it now. 2. Take small bytes. Change only a little at a time. 3. Validate early, validate often. Successful tests help measure progress toward the goal. Very helpful - thanks!
      singulars
      1. PO
      1. USAdam Liss
    2. COYou are right, "fix bugs first" should go first. I fixed that :)
      singulars
      1. PO
      1. USpeterchen
 

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