Re:The saddest "Just Ship It" story ever (2020)
by vouwfietsman on Thursday July 04, 2024 @02:02PM
(#40876835)
Depends on what you mean with great software of course, but a developer should work together with the product team to come to a specific realization of the product vision. That vision may not always require great software, and it may actually specifically call for hacky software, but the product people cannot make that judgement call (and if you are in a healthy company, they don't).
This is different from always making great software but shifting priorities.
>It really isn't, your job is to make a great product. Making a great product often, but not always, requires great software.
I believe that depends on the role you have. If you're a software engineer I think you should try to create great software. If you're responsible for the product you can decide it might be better for the product to ship earlier or with the current state of software but I think you should not keep your software engineers from trying to make the software great. You can try to shift their focus on a different (software) topic that you think is more important if you don't like what they are currently trying to improve.