3 ms·
I almost agree with you. But I don't understand how is the programmer (Software Engineer) responsibility to produce code that hit production? This is the respon
by rrgok 4y ago
I almost agree with you. But I don't understand how is the programmer (Software Engineer) responsibility to produce code that hit production? This is the responsibility for project managers, product owners or whatever. Given the Software Engineer is not a one man team doing all other roles. This is like saying the UX/UI role is to decide what iteration of the design (as in visual) should be in production. No way!
- belfalas 4y ago> how is the programmer responsibility to produce code It is about mindset. Of course I do not mean that a programmer should suddenly be responsible for "doing everything." What I mean is, the programmer should have as their personal mission the writing of the highest possible quality code that is ready to go to production as quickly as possible with a minimum of rework. And crucially, you have to be able to provide a realistic and reliable estimate of when your work can be expected to be completed. This ability is gained through experience. Working well with project/product/design/etc. is part of being a good programmer. It is not enough to simply be a "good dev" - you must also be able to explain what your code does, why it does it that way, and any potential tradeoffs or flaws in design/implementation. If you cannot critique your own code in this way you are not a senior engineer. When you work with other people part of being senior is being willing to be held accountable. Hopefully this makes what I mean more clear. It is about mindset.