As I passed by, I decided to spend some time to go and get some peanuts to get at least few of those elephants out of there:
- Remove the need to touch three repositories to add one build job
- Add the ability to run a b2g desktop mochitest with mozharness without having to loan a releng machine
- What convention to use for developer-focused mozharness configs?
I know I can't use "the elephant in the room" metaphor like that but I just did and you just know what I meant :)
Well, how do you deal with technical debt?
Do you take a chunk every time you pass by that code?
Do you wait for the storm to pass by (you've shipped your awesome release) before throwing the elephants off the ship?
Let me know; I'm eager to hear about your own de-elephantization stories.
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.