← Back to context

Comment by AdieuToLogic

7 hours ago

> As a technical product manager, this 1000%. It's just irrelevant how bad code is unless it impacts the business.

If you are, in fact, "a technical product manager", I would hope you understand that "bad code" is identified as such specifically because it "impacts the business."

5 comments

AdieuToLogic

Reply
Schiendelman  6 hours ago

That is not how most engineers define bad code.

  • AdieuToLogic  6 hours ago

    > That is not how most engineers define bad code.

    The engineers I have worked with most definitely define "bad code" as having intrinsic limitations and/or latent defects which impact successful system functionality/operation. Indicators provided to stakeholders such as yourself which support this assessment are, but not limited to:

      - the system doesn't work that way
  - the system lacks test coverage, so changes take longer
  - adding feature "X" is not feasible
  - there is no repeatable way to onboard team members
  - the backlog grows exponentially
  - that "one point task" is going to take a couple weeks

    All of the above impacts a business.

    It is up to you, the "technical product manager", to understand what your team is trying to tell you.

    • Schiendelman  6 hours ago

      Please stop being rude to me. I'm a human being, I'm a very experienced product manager and engineer (you can google my name, I'm the only one), and the way you are behaving sucks.

      Everything you're saying is true, sometimes. Assume I'm still right, and that you might be able to learn something from someone else.

      2 replies →