Comments on: Judging architecture by ‘if’ statements required for a new feature https://www.robg3d.com/2012/03/judging-architecture-by-if-statements-required-for-a-new-feature/ Blog of Rob Galanakis (@robgalanakis) Thu, 29 Mar 2012 21:56:38 +0000 hourly 1 https://wordpress.org/?v=5.4.2 By: Piotr Dobrogost https://www.robg3d.com/2012/03/judging-architecture-by-if-statements-required-for-a-new-feature/#comment-13286 Thu, 29 Mar 2012 21:56:38 +0000 http://www.robg3d.com/?p=960#comment-13286 Very nice talk showing how “if” is bad – “The Clean Code Talks — Inheritance, Polymorphism, & Testing” http://www.youtube.com/watch?v=4F72VULWFvc

]]> By: Alexander Morano https://www.robg3d.com/2012/03/judging-architecture-by-if-statements-required-for-a-new-feature/#comment-13249 Thu, 29 Mar 2012 15:41:13 +0000 http://www.robg3d.com/?p=960#comment-13249 Absolutely. We have wrapped this behind a dirty word (hard-coding) at work for all the laymen when explaining how ugly this gets over time.

I keep trying to get them used to iteration as a good thing in the use case of having to update systems and sub-systems rather than hack in more gate switches.

I have a few core, legacy tools I must support that are so large and bloated because of the hard-coded switching for the various special cases it truly makes me sad when I have to touch anything in one of them.

]]>