Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>AnthonyWJones's highly-rated answer above is right on, basically</p> <blockquote> <p>Another is put you commercial head on and use some common sense, what is the risk you have introduced another as serious or more serious bug? How will the customer react to that? How will the customer react if you explain your need for more time? Weigh the answers and make a commercial/executive decision</p> </blockquote> <p>But what does it mean to "weigh" the answers? It means that you start assigning weights to things <strong>literally:</strong> you stop, take a break, make a list and think it out. Should you tell the customer that it's impossible? What is the risk that a small bug will be a show-stopper that you've introduced in your week-long frantic rush?</p> <p>Obviously, there are no set answers, but in general, I work as fast as possible but not faster. Some customers just breathe down your neck for fun, but other bugs are so important that <strong>it doesn't matter what else gets broken fixing them.</strong> You cannot determine that without your customer's help. Remember, <strong>you are all working towards the same goal.</strong></p> <p>If the customer is too busy to talk to you, you should explain (in email, or in blood stains, whatever) that you will short circuit QA and perhaps introduce other bugs in the process. You will need to talk, briefly, about the likelihood of those being <strong>more important than the bug in question.</strong> You have experience and know what you're doing (to some extent), so you have to help the customer to understand just how mad (or not) what they're asking for is.</p> <p>Anyway, after rambling a bit, here's my point: <strong>your job is to keep calm and do your job. I doubt that by working many days without breaks you actually found the bug faster</strong>: you were probably trying to go too fast. Your job is also to inform your customer as to what's possible, what is not, and what risks are incurred with each decision. But going faster than your fastest -- as in not taking breaks -- makes no sense and helps no one.</p> <h3> But in all cases, there is nothing to lose your Zen about. Ever. </h3>
    singulars
    1. This table or related slice is empty.
    1. POFixing a bug under severe time constraints
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDan Rosenstark
    1. USDan Rosenstark
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFixing a bug under severe time constraints
      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