Ranter
Join devRant
Do all the things like
				++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
				Sign Up
			Pipeless API
 
				From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
				Learn More
			Comments
		
- 
				
				 castarco1456yAlthough it's a "slow approach", it's usually good to start adding tests to the undocumented legacy code base, so you can be sure that the new code is relatively compatible with it's behavior. castarco1456yAlthough it's a "slow approach", it's usually good to start adding tests to the undocumented legacy code base, so you can be sure that the new code is relatively compatible with it's behavior.
- 
				
				Im always amazed by the fact that foreign keys are ancient but their spike in usage is very recent.
- 
				
				This reminds me of that time I worked for a guy whose code base was variable names like:
 
 EntitySet MASHRS = db.fetch(khoos, vhees, apnars);
 
 I had to ask him about each and every variable. It turned out that all his variables were abbreviations, for example MASHRS meant "Main Shareholders".
 
 Seriously..






Currently, I am going through a legacy application built in microsoft access back in 90s.
* No Comments
* No Relationships between tables
* Random code that does nothing
* Weird form layouts
* Weird naming conventions
I need to copy this functionality into modern version using SQL Server Management studio and asp.net core, I also need to kill myself because none of this fucking shit fucking fuck makes sense.
I do my best to write clean and concise code along with comments but after this ordeal I am going to up my game because nobody should need to suffer through spaghetti code and stupid logic that is uncommented.
😶
rant