Many organizations pressure engineers to ‘complete’ software projects by a committed date, even when that date is unrealistic. Of course, this can happen for valid business reasons; but what is often not well appreciated is the negative effect that this type of pressure has on the code and subsequent adoption of products and services.
In the below linked article, the author points out a number of real world examples of what happens to the code in high-pressured situations. In his opening, he argues that the resulting chaos and bad experiences cause the customer base to resist adoption of version 1.0, and that, therefore, the organizational tendency of driving software engineers to hard dates is value eroding and counterproductive.
The coding examples he cites inline are real, the takeaways ring true, and the article is worth the read:
submitted by /u/UseMyFrameWorkOkay
[link] [comments]