I appreciate the thought behind this post and I wish this mantra could be applied in every situation but I don't think we should all now "Just code to get it out there". It is sound advice for developing the login screen functionality on your website, but when it comes to larger backend systems, a flawed or unoptimised initial design can't just be optimised when it is discovered it isn't working as required. The cost correcting a flawed design, post delivery, could cripple a business. Even in the case where the product is functioning as required, if OOP principles were not applied in initial design, enhancements to that product would most likely be much more difficult to implement. So, as with most things in life, consider the consequences before taking action.
Comments
I appreciate the thought behind this post and I wish this mantra could be applied in every situation but I don't think we should all now "Just code to get it out there". It is sound advice for developing the login screen functionality on your website, but when it comes to larger backend systems, a flawed or unoptimised initial design can't just be optimised when it is discovered it isn't working as required. The cost correcting a flawed design, post delivery, could cripple a business. Even in the case where the product is functioning as required, if OOP principles were not applied in initial design, enhancements to that product would most likely be much more difficult to implement. So, as with most things in life, consider the consequences before taking action.