There is an article that was written during September 11, 2018. The article "Developers, despair: Half your time is wasted on bad code" by Liam Tung from
https://www.zdnet.com/article/developers-despair-half-your-time-is-wasted-on-bad-code/ talks about how developers spend half of their time fixing code that they have built. The article cites that, "But according to Stripe's survey of 1,000 developers and 1,000 C-level execs, on average about half of the developer's working week is spent on maintenance, such as debugging, modifying code, and fixing bad code." Now with all these time consuming tasks, it is understandable why there is a problem in efficiency. Efficiency was a key goal in the company because they want to cut down costs of maintenance. In the article "Developers, despair: Half your time is wasted on bad code" it says, "Conversely, the company argues that if developer time was used more efficiently, developers could raise global GDP by $3 trillion over the next decade." Cutting down on developer time could make more profits by spending less money on maintenance and the same amount of money on other projects which is an increase in profit.
I think that it is necessary to spend time on maintenance, modifying code, and debugging because programs need to be fixed for the users. Cutting down on developer time on maintenance and ect. could negatively impact the program that has been built and increase the chances of losing consumer trust in the product. A better way that might be it could be to hire more developers, have a team dedicated to fixing code, and have the rest of developers do other stuff for the project(s). That way you can develop and fix code at the same time making it more efficient for the company. Also, I think that it could cut down developer increase revenue just a bit by higher productivity which leads into higher quality that turns into more buyers for the program that in turn leads to more profit.
No comments:
Post a Comment