The EDD Manifesto
Emotion Driven Development (EDD) aims to uncover better ways of developing software by combining the two most common abilities developers are said to possess: systemic thinking and emotional intelligence.
You have a task at hand. How do you feel about the code? Are you excited to start working on it? Then you go ahead and implement it. Are you satisfied with this code? Not yet? Why? Did you get tired or bored? Or, are you disappointed of the results? Worse, you are outright disgusted by your code. If so, keep refactoring it until you feel more pleasant about it. Then don't forget to write some tests to solidify the API. Finally it's time to submit it for a code review and hope someone will have enough energy to spot the unpleasant bugs and smells.
The Algorithm
IF you have high energy AND feel pleasant about the code
THEN implement, create something new
ELSE IF you have low energy AND feel pleasant about the code
THEN write tests for code behavior you would not like to be changed easily, who knows, you may even uncover a bug or two that will make you feel unpleasant about it
ELSE IF you have low energy AND feel unpleasant about the code
THEN you should keep refactoring it until you feel pleasant about it
ELSE IF you have high energy AND feel unpleasant about the code
THEN you should review it, even if it's yours, but don't waste your energy refactoring it, find some other unpleasent code to review or implement something new, keep the momentum going until you're low on fuel, at which point you can start refactoringDeveloper's Note
If this concept excites you, feel free to work it out and start selling Fun Master Certification trainings, I just threw this idea out there in a unique way, IDK, it's probably stupid.