3 ms·

I think we need a new name for these type of jobs, then. They're not actual programming positions, since development tends to be about solving problems. Mainte

by sudont 16y ago

I think we need a new name for these type of jobs, then. They're not actual programming positions, since development tends to be about solving problems. Maintenance and production are two lexicographic options that somewhat relay the scope of the position: higher than data-entry, lower than engineering. Much in the same way that a front-end is not necessarily a web developer. Maintenance is what the current discussion is about, but production should be considered as well: it's about interfacing with the existing tools to extend without fixing any of the serious architecture issues. As in a web producer. Or, someone who produces plugins for a given architecture, requiring extensive knowledge of the system but with no access to improve or modify said system.

Periodic 16y ago
I would call it a programming position, at least in my case. Most of my time is dedicated to maintaining a legacy application that is horribly written, but my time is mostly spent either trying to come up with inventive ways to code around the existing design decisions, or trying to come up with a way to improve the design without disrupting service. It's very challenging to do well, but it is definitely not fun.
Florin_Andrei 16y ago
Code Janitor.
Retric 16y ago
I break things down into Developers and Hackers. A Developer tends to create new foundations using existing and documented API's. A Hacker works within a system, and focuses more on existing code and what it actually does than documentation. Hackers tend to be worth more in the short term, Developers tend to be worth more in the long term.
vorg 16y ago
In some countries, programmer time marked "Maintenance" is expensed while that marked "Production" is depreciated over x years for tax purposes, so companies want their programmers to log their activities as "maintenance". If the auditors come, it had better have been maintenance. Perhaps the only real way to develop production code is work for a startup, but the recruiters won't be impressed if you want to go back to a large company later on.

by sudont 16y ago

Periodic 16y ago

I would call it a programming position, at least in my case. Most of my time is dedicated to maintaining a legacy application that is horribly written, but my time is mostly spent either trying to come up with inventive ways to code around the existing design decisions, or trying to come up with a way to improve the design without disrupting service. It's very challenging to do well, but it is definitely not fun.

Florin_Andrei 16y ago

Code Janitor.

Retric 16y ago

I break things down into Developers and Hackers. A Developer tends to create new foundations using existing and documented API's. A Hacker works within a system, and focuses more on existing code and what it actually does than documentation. Hackers tend to be worth more in the short term, Developers tend to be worth more in the long term.

vorg 16y ago

In some countries, programmer time marked "Maintenance" is expensed while that marked "Production" is depreciated over x years for tax purposes, so companies want their programmers to log their activities as "maintenance". If the auditors come, it had better have been maintenance. Perhaps the only real way to develop production code is work for a startup, but the recruiters won't be impressed if you want to go back to a large company later on.