#legacy code variables are badly named
Explore tagged Tumblr posts
Visit Tumblr Blog
Explore Tumblr blogs with no restrictions, modern design and the best experience.
Last Seen Tumblr Blogs
Fun Fact
Forty percent of Tumblr users are between the ages of 18 to 25.
Text
Learning programming would be so much easier if programmers actually learned how to name variables
#like library functions are badly named#legacy code variables are badly named#teaching examples are badly named#even standardised variables like the call names for libraries and data analytic variables are badly named#no wonder people look at this shit and nope out#coding#programming#python#code#NOTHING SHOULD BE CALLED XXX2#r_ should not be a function 😭
1 note
·
View note
Text
7 techniques to regain control of your Legacy codebase
"Your legacy codebase is a jungle, full of badly named variables, non-standard structures, useless indirections, bad abstractions. When you fix something, you find three more problems hidden behind it."
If you recognize your codebase in this description, then here are 7 techniques that can help you get back to a saner state:
The Brain Dump. Get things out of your head to keep focus. Use a simple piece of paper for that, no need for fancy tooling.
The Mikado Method. It's a more structured approach, especially useful when you have a clear goal in mind.
Over-committing. Do small, frequent commits. Much more than you're used to. This is a handy behavior to adopt when things are really messy and the risk of breaking things is high.
Write ADRs. The good news is that you can start now, regardless of the state of your codebase. It will pay off in the next months.
Approval Testing. It's a specific approach for covering existing code with tests. It's very useful when you don't really know what the code is doing, you need to change it and you want to build a safety net quickly before you can clean up the code.
Hotspot Analysis. Many things are bad in a legacy codebase, but some matter more than others. Prioritize what's complex and that changes often.
Refactoring katas. Practicing these techniques in a safer environment will help you feel more comfortable when you need to do it for real. This is important training for any developer, and companies usually need to spend some budget in training their employees. Think about it.
These are taken from this more detailed article: https://understandlegacycode.com/blog/7-techniques-to-regain-control-of-legacy/
Did you knew these? Do you have other techniques that have helped you with Legacy codebases? Let me know =)
submitted by /u/nicoespeon [link] [comments] from Software Development - methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/32wiSwP via IFTTT
0 notes