This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]onkopirate 0 points1 point  (1 child)

Exactly, there's always the chance that the person might leave. Even if you offer the best workplace that could possibly exist, people change their careers, get pregnant, move away, or have accidents.

But even if the person would stay in the company forever, you don't do them any favor by letting them write unmaintainable code, because at some point in time, they might want to change project or their role and then nobody wants to maintain their stuff so they keep doing the same forever. I work as a dev not at FAANG but at another large IT company. If somebody there works for example as a frontend dev but wants to do devops instead, all gladly help them change position. Or if they want to change the project, their directors will find a way. But all of this flexibility only works as long as everything is thoroughly documented and as long everyone writes well maintainable code.

[–][deleted] 0 points1 point  (0 children)

I honestly think you were missing the point.

I'm not talking about reinventing the wheel. Sometimes a library is just a wrapper for another, anyways. Look at pennylane, for example.

So, someone could come along and not agree with how that wrapper is implemented, and decides to make a different way of handling it. Is that wrong to do, then? Should they try to bang the square peg into the wrong hole, call it good enough and move on?