I feel that in the rush to get things done, in some cases quality code takes a back seat to timely deliveries.  

To an extent this is fine and quite understandable.  Missing a deadline is just as likely, if not more so, to cause a project to fail, and moreover the term "quality code" can easily mean different things to different people.

  • Unless explicitly directed otherwise, I will deliver code that is as simple and as maintainable as I can make it.  Early in my career I learned that maintainability is key and many experiences have reinforced this lesson.
  • If I see something is broken in the project, I will tell you about it.  If it is in an area of the code that I am tasked with changing, unless explicitly directed to leave it alone, I will feel obligated to fix the problem.

If these opinions seem obvious to you, good: that means we think alike!