Having been on both sides of the fence, I find that I look at code quality differently as an in-house developer than as a contractor. With contract work there are two kinds of time deadlines. 1) When the client needs the feature. 2) When the money run out. You can exhaust the budgeted labor cost well before the client's deadline. So as a contractor, there is far more pressure to just "get things done" and worry about quality as a secondary concern. But as an in-house developer, I might have to deal with the code for many years to come. So, I tend to take more time to keep quality high. However, this can make in-house development even more expensive than can be quantified by salary+benefits vs contract budget. Whether that is worth it depends on the business goals. Dev availability for in-house might also be a concern.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Having been on both sides of the fence, I find that I look at code quality differently as an in-house developer than as a contractor. With contract work there are two kinds of time deadlines. 1) When the client needs the feature. 2) When the money run out. You can exhaust the budgeted labor cost well before the client's deadline. So as a contractor, there is far more pressure to just "get things done" and worry about quality as a secondary concern. But as an in-house developer, I might have to deal with the code for many years to come. So, I tend to take more time to keep quality high. However, this can make in-house development even more expensive than can be quantified by salary+benefits vs contract budget. Whether that is worth it depends on the business goals. Dev availability for in-house might also be a concern.