Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>'How do you go about intentionally using design patterns without going "overboard?"'</p> <p>Easy.</p> <ol> <li><p>Don't conflate an MVC framework development effort with patterns. </p></li> <li><p>Recognize that every single thing you do has been done before (by you or someone else).</p></li> <li><p>When you repeat something -- anything -- you're following a pattern.</p></li> <li><p>When you repeat the design for anything -- no matter how small -- you're following a design pattern.</p></li> <li><p>When you notice yourself repeating something, assign a name to that thing you are repeating. Look, you've discovered and named your first design pattern. No matter how small.</p></li> <li><p>When you've named a design pattern, you can then think about when you use it, why you're using it, what it solves and what the consequences of using it are. No matter how small.</p></li> <li><p>Every piece of learning that involves "repeating design elements" is design patterns. No matter how small.</p></li> </ol> <p>Every loop. Every if-statement. Every dialog box. Every file open. These are all design patterns.</p> <p>Most are part of the language and have obvious language-specific names. "IF", "OPEN", etc.</p> <p>Some design patterns are larger than a single statement but smaller than the entire MVC framework. Those are the interesting ones. Learn those. Buy a book. Read it. MVC will not appear in most design pattern books, because -- well -- it's too complicated and too difficult to apply.</p> <p>Don't start with MVC. Start with ANYTHING else.</p>
    singulars
    1. This table or related slice is empty.
    1. PODesign Patterns - Architecture Astronaut
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USS.Lott
    1. USS.Lott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. CO+1 I lol'd at "no matter how small", nice description of patterns but for a second there I thought I was reading "Horton hears a who"
      singulars
      1. PO
      1. USAndrew Hare
    2. COGood post, but I just have to nitpick: The connotation of design pattern refers to the highlevel layout of your software's architectural pieces, not a generic word for any named software patterns. Case in point, a "bubble sort" is recognizable software pattern with a name, but not a design pattern.
      singulars
      1. PO
      1. USJuliet
    3. COHow can design pattern not refer to ALL patterning at all levels of detail? What are those other patterns that I designed in if they're not design patterns? Bubble sort is a pattern composed of smaller patterns and part of a larger pattern.
      singulars
      1. PO
      1. USS.Lott
 

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