<story><title>Why enterprise software is bloated</title><url>https://www.mailbox.my/blog/posts/why-enterprise-software-is-bloated/</url></story><parent_chain><item><author>adambyrtek</author><text>I know this is just an anecdote, but a good developer wouldn&amp;#x27;t ask the manager to approve every small refactoring or expect them to understand the importance of &amp;quot;one method in SuperFactory&amp;quot;. They would have instead made a judgement call and taken the responsibility of doing the quick fix.</text></item><item><author>ihateolives</author><text>&lt;i&gt;In a lot of companies, feature development trumps optimizing, refactoring or removal of legacy code.&lt;/i&gt;&lt;p&gt;Dev: Hey Steve, I&amp;#x27;m working on issue #4546, but it just occured to me that that if I could just refactor that one method in SuperFactory it&amp;#x27;d make code much cleaner and easier to reuse. Just a quick fix!&lt;p&gt;Manager: No. Work on #4546.&lt;p&gt;Dev: Sure, #4546 will be done soon, but it&amp;#x27;d be really easy fix, it just occurred to me yesterday that there&amp;#x27;s a better way to build things with SuperFactory.&lt;p&gt;Manager: No! We already closed that issue!&lt;p&gt;Dev: No problems. But I thought that now that I have some extra time until...&lt;p&gt;Manager: Look, Dave, it&amp;#x27;s working as intended, the solution was reviewed and accepted. I will not create another task. You&amp;#x27;ll take #7839 next!&lt;p&gt;[...]&lt;p&gt;Manager: Hey, Dave, I recall you had some ideas about SuperFactory. It&amp;#x27;s been acting up lately, they keep creating tickets.&lt;p&gt;Dev: Nope. None. All gone now.&lt;p&gt;Manager: But you had, right?&lt;p&gt;Dev: Yes, but I&amp;#x27;d have to start digging in again and I don&amp;#x27;t have time for that.&lt;p&gt;Manager: Oh, ok, you&amp;#x27;re right.</text></item></parent_chain><comment><author>commandlinefan</author><text>&amp;gt; wouldn&amp;#x27;t ask the manager to approve every small refactoring&lt;p&gt;It becomes an issue if it takes more than a day.  Scrum, Kanban, RUP, XP, waterfall - whatever &amp;quot;methodology&amp;quot; they say they&amp;#x27;re following, it boils down to &amp;quot;tell me how long this is going to take and I&amp;#x27;ll check to see how close what you said was to the time it took&amp;quot;.  If you can make a change in an hour, sure.  If it takes a day, it&amp;#x27;s going to break your &amp;quot;commitment&amp;quot;.</text></comment>
<story><title>Why enterprise software is bloated</title><url>https://www.mailbox.my/blog/posts/why-enterprise-software-is-bloated/</url></story><parent_chain><item><author>adambyrtek</author><text>I know this is just an anecdote, but a good developer wouldn&amp;#x27;t ask the manager to approve every small refactoring or expect them to understand the importance of &amp;quot;one method in SuperFactory&amp;quot;. They would have instead made a judgement call and taken the responsibility of doing the quick fix.</text></item><item><author>ihateolives</author><text>&lt;i&gt;In a lot of companies, feature development trumps optimizing, refactoring or removal of legacy code.&lt;/i&gt;&lt;p&gt;Dev: Hey Steve, I&amp;#x27;m working on issue #4546, but it just occured to me that that if I could just refactor that one method in SuperFactory it&amp;#x27;d make code much cleaner and easier to reuse. Just a quick fix!&lt;p&gt;Manager: No. Work on #4546.&lt;p&gt;Dev: Sure, #4546 will be done soon, but it&amp;#x27;d be really easy fix, it just occurred to me yesterday that there&amp;#x27;s a better way to build things with SuperFactory.&lt;p&gt;Manager: No! We already closed that issue!&lt;p&gt;Dev: No problems. But I thought that now that I have some extra time until...&lt;p&gt;Manager: Look, Dave, it&amp;#x27;s working as intended, the solution was reviewed and accepted. I will not create another task. You&amp;#x27;ll take #7839 next!&lt;p&gt;[...]&lt;p&gt;Manager: Hey, Dave, I recall you had some ideas about SuperFactory. It&amp;#x27;s been acting up lately, they keep creating tickets.&lt;p&gt;Dev: Nope. None. All gone now.&lt;p&gt;Manager: But you had, right?&lt;p&gt;Dev: Yes, but I&amp;#x27;d have to start digging in again and I don&amp;#x27;t have time for that.&lt;p&gt;Manager: Oh, ok, you&amp;#x27;re right.</text></item></parent_chain><comment><author>Clubber</author><text>Yes, the general rule for me is if I see something completely whack on the ticket I&amp;#x27;m working on, I&amp;#x27;ll clean it up as long as I know there won&amp;#x27;t be collateral damage. The problem comes when these systems become so complex and so old and the people working on them don&amp;#x27;t really know what changes will affect other systems down the chain.</text></comment>