The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I was hired recently to fix some problems in some old software done using . NET 2. the old version was poorly done by every means no documentation no real naming system, nothing.
I scheduled a REDO for the whole thing but the original software which is running now need some major fixes quickly, the whole system crushed many times, some part are like if they done by a child, they can't wait for long enough for me to complete my work.
I was joking. Don't resign - decide what the best way for you is to tackle the job and go for it. No good asking other people who haven't the slightest notion of the ins and outs of the issue: only you know what's best for you.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum
You haven't been hired to do a redesign/reimplementation. You have been hired to plug the leaks, so to speak. Short term, you do the fixes. The best way to get to the rewrite is to prove that it's more economical to rewrite than it is to patch - and that type of argument takes time to win.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
I'm with Mark, quit and get another job, it seems like really bad management to me.
If that is not an option then you HAVE to do the work, you also must make management aware you are doing it under protest and part of the solution is to rebuild the app. Then try and break it into smaller parts that can be rebuilt and integrated piecemeal.
Never underestimate the power of human stupidity RAH
Sounds like you inherited my old job. For a while it may even be fun to keep the old program running with one hand and writing the new one with the other. The problem is, that they will not stop when they see that you perform those two little miracles. You will discover that they have a whole collection of bad applications and even higher expectations waiting for you and it will seem like fighting against windmills.
Absolutely, especially when I'm experimenting with something. It's hard to follow standards where there are none. And it's the nature of experiments that unexpected things happen, so the design will suffer after enough tweaking. After all, you probably also don't obey the traffic rules when you want to drive offroad. And you don't have to, since traffic cops usually don't lurk in the middle of nowhere.
Australian traffic cops do lurk in the middle of nowhere! Personall, if there aren't standards, I implement them myself, and reengineering is the solution to the suffering through tweaking dilemma. Still, I'm perfect, so I guess I can't expect everyone to live up to my lofty level
Australian traffic cops do lurk in the middle of nowhere!
That's because there is so much nowhere you can be in the middle of in Australia.
Personall, if there aren't standards, I implement them myself, and reengineering is the solution to the suffering through tweaking dilemma. Still, I'm perfect, so I guess I can't expect everyone to live up to my lofty level
Why can't I be applicable like John? - Me, April 2011 ----- Beidh ceol, caint agus craic againn - Seán Bán Breathnach ----- Da mihi sis crustum Etruscum cum omnibus in eo! ----- Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932
If you're being hired to patch up the old version, then do that. Much as it's lovely to rewrite something from a blank slate, it is always longer and often significantly so, and that decision is one that has to be made by people with an eye on the budget as well as the technical cleanness.
You can do significant refactoring on the parts that you have to touch anyway, though, under the umbrella of 'fixing'.