Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's some tips some loosely based on agile methods, which should be pretty good for one man teams, as they don't have much overhead compared to usefulness.</p> <ul> <li><strong>Make a deployment script</strong> - a single command you can run to deploy the app. This way you can easily repeat the steps you do to deploy the app. This reduces chances of making a small mistake or forgetting a step when deploying to production or staging</li> <li>I've found developing on my own PC is usually fastest for me. No network delays when working, familiarity with the OS and tools. In the end what matters is personal preference.</li> <li>It would be a good idea to <strong>have a staging environment</strong>, preferably on same hardware/software as the final production environment. This will allow you to confirm everything works OK there, and can allow clients to test drive the changes.</li> <li>Try doing <strong>periodical releases</strong>, similar to Scrum sprints. Choose what features you want to complete for the next release. This makes it easier to concentrate on the most important features as you know what you need to do, and also makes it easier to display progress (Ok this release features A, B and C). Only choose new features for the current release if you finish the ones you chose. Tag each release in source control.</li> <li>For the above, you may wish to <strong>use Trac to keep track of features</strong>, as you said. What tool or approach you use doesn't matter, as long as you have some kind of map or document about what you're doing.</li> <li>If you are familiar with unit testing, you may want to consider using <strong>Test Driven Development</strong>. If not, it might be a good idea to start learning about unit tests</li> </ul> <p>And last but not least, <strong>make a schedule and stick to it</strong>. Otherwise your project may end up taking considerably longer than expected.</p> <p>I hope at least some of these help you avoid some mistakes I've made earlier in my career =)</p>
    singulars
    1. This table or related slice is empty.
    1. POnewbie to 'proper' php project management
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJani Hartikainen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POnewbie to 'proper' php project management
      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