Watching the number of lines decrease, then the lines, scattered with ands and ors, get shorter was wonderful.
Accu rip audio code#
This made it possible to massage the code into a state where you could add a new feature. However, it did write lots of log messages, so you could tell if it still was functionally identical after making changes. The code was a snaky mess of ifs and elses, with no tests. Emily Bache ran a 90-minute workshop at the ACCU conference in 2013 on refactoring. Sometimes the best you can do is produce some output in a file and use that as a ground truth to ensure any changes introduced don’t cause regressions. There might not be conventional unit tests. In order to refactor, a code base requires some tests, otherwise you are reworking or changing the code instead and potentially changing its behaviour. A complete rewrite might be the way to go. Take a previous talk or an old code base: sometimes you can refactor it slightly, sometimes you can’t. Other times, the best thing to do is rip it up and start again. Restoring or reviving something old is one way to go. I should throw all my old notes out to give myself a fresh start for a new year. I decided to tidy the house, starting with making a new TODO list, subsequently running out of paper because I remembered several other things that needed to get done. Now, if I listened to my own musings in our last Overload (‘Revolution, Restoration and Revival’, ), I could try to revive some of these. Several are so old now, I’ve visited the topics from a different angle in previous excuses for not writing an editorial. I have notes dotted all around the house, with potential titles or ideas scribbled down.
0 kommentar(er)
