{"id":1363,"date":"2014-07-12T23:42:43","date_gmt":"2014-07-12T22:42:43","guid":{"rendered":"https:\/\/www.entropywins.wtf\/blog\/?p=1363"},"modified":"2018-08-30T00:12:08","modified_gmt":"2018-08-29T23:12:08","slug":"component-design","status":"publish","type":"post","link":"https:\/\/www.entropywins.wtf\/blog\/2014\/07\/12\/component-design\/","title":{"rendered":"Component design"},"content":{"rendered":"

This week I gave a presentation titled “Component design: Getting cohesion and coupling right<\/a>” at Wikimedia Deutschland<\/a>.<\/p>\n

\"slides-0-first\"<\/a><\/p>\n

Components are a level of organization, in between classes and layers. They are an
\nimportant mechanism in avoiding monolithic designs and big balls of mud. While
\neveryone can recognize a component when they see one, many people are unaware of
\nthe basic principles that guide good component design.<\/p>\n

This presentation is aimed at developers. It is suitable both for people new to the field
\nand those with many years of experience.<\/p>\n

The topics covered include:<\/p>\n