See hidden discussions | Win great prizes | Get free support
Ever noticed how close you are sitting to the door?
I sit next to the window, right on the other side of the room from where the door is. It is much harder to try and figure out where the action adventure sports devs screwed up while you have clients that are annoyed and then it is not just a case of finding the problem and fixing it - you need to fix the unit tests, create a hotfix, push the changes into all relevant code bases and update the required documentation.
So no, it is not as glamorous as fancy adventure camp action sport devs playing around with new ways of getting things done and screwing the rest up, but it keeps things running and customers happy.
I have gone through exercises like that at two companies in my career so far, the problem is not the developers, it is when a completely rewritten system is rolled out and users are moved onto it. As the solution matures it becomes more stable, thanks to maintenance developers.
The point I am trying to make is that while you need to use modern tools and processes, you should allow what is created to mature and not constantly try out funky new things.
And?So you're a maintenance developer ? :erm:
So you're a maintenance developer ? :erm:
Being maintenance developer can be one of most frustrating and rewarding jobs.
Actually maintenance is bad expression since in most cases you are adding new functionality and you are trying to extend life and ROI of application that is out there.
Personally one of most frustrating bits is when people do not understand legacy systems and technologies used and simply decide that using latest XYZ technology and RTY language will somehow magically solve all the problems.
This is usually followed with "We need to rewrite all this and it will be done in a 3/6/12 months".
Well it does not work like that.
Regarding mine is bigger than yours, well use one that suits most for the given job and you are comfortable with it (still assuming that it is suitable tool).
Look at c\c++, its death was predicted for years now however with new language features added in c++[11,14,17] and advancement of standard libraries it will die slow and painful death for the next 50 years
I think I took this thread bit too seriously....
Why on earth would you want to learn anything else?