Merciless Refactoring- this is incredibly rewarding, try it!
Note that EL is EviL(runtime exceptions, Refactoring).
Refactoring, KAddressBook/ Kontact integration.
Code Refactoring and SVG support. Current maintainer.
Getting married is the opposite of a Refactoring.
Bugfixes and Refactoring.
Visual Studio includes a code editor supporting IntelliSense(the code completion component)
as well as code Refactoring.
To anyone following the Nexus Github repository,
you can see there have been major updates(Refactoring and designing) of the Nexus codebase.
If you're mostly concerned with data layer testing, you might want to check out this book:
xUnit Test Patterns: Refactoring Test Code.
If Refactoring is inappropriate or infeasible,
can you use the strategy pattern to replace access to these private member functions/ member classes when under unit test?
Scott Ambler produces a great series of articles(and co-authored a book)
on database Refactoring, with the idea that you should essentially apply TDD principles
and practices to maintaining your schema.
Another approach to improve performance(if indexes don't help) is reducing number of tables- or to put it another way: To redesign your database to use
less tables(some may call this step: Refactoring).
The technical term for this technique is called Refactoring, as described by Martin Fowler in his book of the same name,
and it is a linchpin of the adoption of Agile software development methods.
I have become quite accustomed to writing unit tests in Java using JUnit but was at a loss as to the best way to write
unit tests for existing code(which needed Refactoring) as well as new code added to the system.
You know how you sometimes start tweaking a few lines of code here and there,
then realize a couple functions could use some Refactoring, and then one things leading to another you find
yourself a few days later in the process of setting up a brand new stack complete with a database and GraphQL API?