By these questions one could estimate the code quality and it doesn't change with time. The only point which might have something to do with time is whether the code is using an antiquated or experimental technology or language.
I believe the problem we're trying to tackle here is: who is responsible for maintaining the code once it has been released? One article on the topic I find worth reading: blog.codinghorror.com/the-noble-ar...
"one could estimate the code quality and it doesn't change with time".
I agree that code does not change with time, but other things change. New tools, languages, techniques, security requirements, performance requirements, scalability requirements, environments its used on, ...
Thank you for your contribution to the discussion.
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.
By these questions one could estimate the code quality and it doesn't change with time. The only point which might have something to do with time is whether the code is using an antiquated or experimental technology or language.
I believe the problem we're trying to tackle here is: who is responsible for maintaining the code once it has been released? One article on the topic I find worth reading: blog.codinghorror.com/the-noble-ar...
"one could estimate the code quality and it doesn't change with time".
I agree that code does not change with time, but other things change. New tools, languages, techniques, security requirements, performance requirements, scalability requirements, environments its used on, ...
Thank you for your contribution to the discussion.