Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 2
    The suggestion of simply ignoring quality of work because your ownership of the codebase may not be permanent is laughable. It would severely undercut the work ethic of any contractor or limited-contract employee. Secondly, even if OP leaves, their successor will be dealing with the same issues, and if OP's points are valid, will be making the same points anyway. This is not an answer, it's the shirking of responsibility for no reason other than "because I can get away with it". The question is not related to being a contractor, so the answer shouldn't be related to it either. Commented Sep 25, 2019 at 13:41
  • We had another FE dev when I arrived here, who seemed to be involved in the exact same conflict, but I wasn't really aware of what it was about until he left for his home country for family reasons and I inherited the responsibility. They had actually reached a sort of compromise, where the components would be published as packages, but now that he's left I think the lead dev sees it as an opportunity to "try again" with me to implement his preferred pattern. I thought the package model was very strange, and now see how it was conceived as a midpoint between the 2 patterns. Commented Sep 25, 2019 at 15:24