About this episode
Picture this: you’re refactoring code after a long code review. Your team lead keeps repeating themselves saying, “Don’t repeat yourself!”
How much do you need to refactor? Should you just write a method with a big loop? Or should you write a framework? If you’re wondering how deep the rabbit hole goes, this is the talk for you.
By the end of this talk, you’ll learn a couple of tricks that help you figure out how heavily you need to refactor your code.
You’ll also learn a couple of ways you can use big O notation to figure out whether you should be writing a tool to solve your problem or not!
Instructors
