Clever Geek Handbook

Have you ever worked on "old school code" that makes you die every time?

I feel like I'm dying a little on the inside every time I work to convert this legacy code into a web application. The database is crap. All fields and column are nvarchar and empty (empty string) are supposed to mean Nothing (Null) instead of Null to mean nothing. For something like a percentage instead of using a decimal number. You mark the extra two zeros and store them as a string (nvarchar). How do I dig into the database while working on the code and discovering how an old legacy application works. I'm going to die a little.

0


source to share


4 answers


I sympathize. Dying is a little bad for your health. One way to feel better is to fix it, a little at a time. Do it a little better and you will feel it much better.



+3


source


Yes, always. We have a mixture of utilities that are either really very bad C ++ (MFC) or VB6, which are inherently bad ;-)



I've worked for 5 years as a contractor and some of that work is working on really really bad code. By the time a contractor is introduced, things are usually pretty heavy. My soul died a few years ago!

+2


source


I am doing this right now. I am working on an architectural evaluation of porting to .NET solutions from :

  • old VB6 code that has dozens of forms and only a couple of classes.
  • SQL Server 7 with 60+ DTS packages

Everything is very old and has little or no error handling .

Now I cry ...

0


source


yes, I had it. One of them is that the database consists of Excel tables. With some of the same data in every table.

Then there is a flowchart based program where data is entered ... no naming conventions, useless or no comments, unexplained constants all over the place ... and doesn't even force me to run the flowchart software ...

0


source






More articles:


All Articles