Disclaimer: My blogs are not a reflection of my employer's opinions, but are my own, and often unfiltered. Also, some links on this site may be part of an Amazon Associates program, so by clicking on them you help me pay for my independence.
[[{"type":"media","view_mode":"media_preview","fid":"25","link_text":null,"attributes":{"alt":"Acquia Certified Developer","title":"I am an Acquia Certified Developer","height":147,"width":147,"style":"width: 60px; height: 60px;","class":"media-image media-element file-media-preview"}}]] [[{"type":"media","view_mode":"media_preview","fid":"15","link_text":null,"attributes":{"height":180,"width":180,"style":"width: 60px; height: 60px;","class":"media-image media-element file-media-preview"}}]] 
[[{"type":"media","view_mode":"media_original","fid":"13","link_text":null,"attributes":{"height":68,"width":310,"style":"width: 190px; height: 42px;","class":"media-image media-element file-media-original"}}]] 
Traits: Just gimme the codez Enter traits. Traits don't imply a relationship. They're purely code reuse. At runtime, traits no longer exist. They say nothing about an object that uses them, how they behave, what you can do with them, or anything else. They are purely code reuse. In that sense, they are completely orthogonal to interfaces; whereas an interface is purely interface reuse, a trait is purely code reuse.