Welcome to the Monastery | |
PerlMonks |
Re: Code Structure Changesby wjw (Priest) |
on Oct 27, 2017 at 20:05 UTC ( [id://1202191]=note: print w/replies, xml ) | Need Help?? |
This breaks down into two problems as I understand it.
When it boils down to it, from a contractual standpoint, making the code better outside the currently contracted specification is not your problem. Your problem is that you are diligent and wish to save the customer future expense. A laudable trait. So the best you can do in my opinion is to offer up the additional service and let the customer choose whether they want to take on that expense. And then live with their decision and 'let it go' if they choose not to take you up on it. Should they hire you in the future, you can always say no if it bothers you much. But I am thinking that you will increase your chances of being contracted again if you make the effort, even if you are turned down. As long as you stay positive, and do not criticize the existing code base. There is a lot of difference between criticism and 'presenting opportunities" though communicating that way is pretty nuanced. This is not so much what you "should" do as it is what you "can" do which positive for you in that you have addressed what bothers you in a positive, diligent and professional way. You end up respecting yourself for having addressed that which might benefit the customer, and respecting them either way that they decide(though that might be quantitatively and/or qualitatively less if they reject your proposal, regardless - you have shown them respect). ...the majority is always wrong, and always the last to know about it... A solution is nothing more than a clearly stated problem...
In Section
Meditations
|
|