We all now those devs who fly from project to project without never following any product into later phases of their lifecycles.
I call these drive-by developers. They usually leave a mess.
The core of the problem is in how you run your software development process. If you run it like a series of projects with a fixed goal (i.e. the delivery of a feature), then you get unmaintainable code. If you run it as a product, you have the chance of getting maintainable code.
It is well documented that writing maintainable code is slower at first, but it will pay back big time in the future. Maintenance is easier but so it extending the product. Where with project based development you will often find yourself applying more and more ducttape and other MacGyver style tricks to keep the thing from not collapsing.
Starting with maintenance work is a good way of learning how the system is set up. You need to get an understanding of the system to know how to change it.
you have the chance of getting maintainable code
Love this, shows how hard it is to make good software. Aiming for maintainable code still only gives you a chance that you will get it
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.
I call these drive-by developers. They usually leave a mess.
The core of the problem is in how you run your software development process. If you run it like a series of projects with a fixed goal (i.e. the delivery of a feature), then you get unmaintainable code. If you run it as a product, you have the chance of getting maintainable code.
It is well documented that writing maintainable code is slower at first, but it will pay back big time in the future. Maintenance is easier but so it extending the product. Where with project based development you will often find yourself applying more and more ducttape and other MacGyver style tricks to keep the thing from not collapsing.
Starting with maintenance work is a good way of learning how the system is set up. You need to get an understanding of the system to know how to change it.