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.
...After getting a project where you have to do some improvements and add some new functionalities and you realize there is no exception handling in a 400 000 lines of code application, there are no forms - only controls in the application, no inheritance and database operations written directly in controls
Well - if I were an ordinary developer, I'd update my CV (resume) very quickly and look elsewhere. As the boss, I have to take the longer term view and work out whether a fix or rewrite would be in order.
Deja View - the feeling that you've seen this post before.
Discuss your opinions with your superiors.
Discuss resolution options with them.
Yes, but make sure that you pass on the facts and the options in writing. In cases like this, management wants to shoot the messenger because they are the ones who allowed to app to get into this state.
Smith & Wesson: The original point and click interface
Please read this if you don't understand the answer I've given you
"also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
Submit a report to the manager detailing the options for adding the improvements:
1) Add improvements with minimal effort. (Emphasize the good-fast-cheap[^] triangle. Make sure your manager is aware this is the fast option so will not be very good, and will cost more in the long run when everything breaks)
2) Full rework. (The good option in the triangle, so will be slow, but in the long run will cost the same/less because you won't have to deal with everything breaking)
Let your manager choose.
As to which option I would recommend depends on the state of the project. If it's an old version, that's maybe about to be superseded by a replacement, and just needs to last a few months till the replacement is ready, go with 1. If it's going to be around for a while, go with 2, but be prepared for the management to choose 1. If it's a new/flagship product, recommend 2 and if they choose 1, run run run.
Depending on the types of improvements you're being asked to make, consider a 3rd option of just reworking the bits your improving.
Make sure you do a upfront design and allow plenty of time for the rework, so your manager is aware of how long its going to take and understands why.
Judging by the description of his post, I'd say its highly likely the codebase is VB, not that I know, practice or code in VB, from 'what' I've seen the 'on error resume next' is the most memerable line, enough to make me avoid VB.
Judging by the description of his post, it's already in there
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighist
Overlapping controls, textBox/combobox array, button array with common eventhandler for all 30 of them, with 5 pages long of if.then.else, and 3 pages long of insert & update statement that directly use textBox(17).Text. WOOHOO!!
Last Visit: 26-Mar-19 14:12 Last Update: 26-Mar-19 14:12