Databases
StackOverflow2013
Postsdbo
POMonkey-patching Vs. S.O.L.I.D. principles?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMonkey-patching Vs. S.O.L.I.D. principles?
    primarykey
    data
    text
    <p>I'm slowly moving from PHP5 to Python on some personal projects, and I'm currently loving the experience. Before choosing to go down the Python route I looked at Ruby. What I did notice from the ruby community was that monkey-patching was both common and highly-regarded. I also came across a <strong>lot</strong> of horror stories regarding the trials of debugging ruby s/w because someone included a relatively harmless library to do a little job but which patched some heavily used core object without telling anyone. </p> <p>I chose Python for (among other reasons) its cleaner syntax and the fact that it could do everything Ruby can. Python is making OO click much better than PHP ever has, and I'm reading more and more on OO principles to enhance this better understanding.</p> <p>This evening I've been reading about <a href="http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod" rel="nofollow noreferrer">Robert Martin's SOLID</a> principles:</p> <ul> <li><strong>S</strong>ingle responsibility principle,</li> <li><strong>O</strong>pen/closed principle,</li> <li><strong>L</strong>iskov substitution principle,</li> <li><strong>I</strong>nterface segregation principle, and</li> <li><strong>D</strong>ependency inversion principle</li> </ul> <p>I'm currently up to <strong>O</strong>: <em>SOFTWARE ENTITIES (CLASSES, MODULES, FUNCTIONS, ETC.) SHOULD BE OPEN FOR EXTENSION, BUT CLOSED FOR MODIFICATION</em>. </p> <p>My head's in a spin over the conflict between ensuring consistency in OO design and the whole monkey-patching thing. I understand that its possible to do monkey-patching in Python. I also understand that being "pythonic" is to follow common, well-tested, oop best-practices &amp; principles.</p> <p><strong>What I'd like to know is the community's opinion on the two opposing subjects;</strong> how they interoperate, when its best to use one over the other, whether the monkey-patching should be done at all... hopefully you can provide a resolution to the matter for me.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPéter Török
    1. USPhillip B Oldham
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMonkey-patching Vs. S.O.L.I.D. principles?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMonkey-patching Vs. S.O.L.I.D. principles?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMonkey-patching Vs. S.O.L.I.D. principles?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan someone edit this question to attribute the SOLID principles to Robert C. Martin?
      singulars
      1. POMonkey-patching Vs. S.O.L.I.D. principles?
      1. USquamrana
 

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