You need to sign in or sign up before continuing.
Take a photo of a barcode or cover
kmariek 's review for:
Refactoring: Improving the Design of Existing Code
by Martin Fowler
Big list of ways you can refactor your code. I read the newest version atm, which uses JavaScript for the examples. I work mostly in Go right now so decent language difference, but I don't think it mattered at all.
Since it's laid out in a reference structure, I wondered a lot if going front-to-back was the right choice, and ended on thinking that reading it through once prepped me for using it as a reference later on. I got the most out of it when I stopped forcing myself to read the Mechanics sections out of blind completionism, since the Example section does a great job of showing the incremental steps in a way that's more engaging if you're not sitting in front of the code right now and changing it.
Took me awhile (can I say a dog's age? the dog would still be a puppy) to get through it, but I got a lot out of it since at multiple points I read about the motivation for a refactoring and got a deeper understanding of why specific past code of mine was bad while learning how to fix it.
Many times "code smell" was used I'd hear "YOU HAVEN'T THOUGHT OF THE SMELL" in my head from Always Sunny. If one person reads this and starts hearing it too I will have fulfilled some purpose in the world.
Since it's laid out in a reference structure, I wondered a lot if going front-to-back was the right choice, and ended on thinking that reading it through once prepped me for using it as a reference later on. I got the most out of it when I stopped forcing myself to read the Mechanics sections out of blind completionism, since the Example section does a great job of showing the incremental steps in a way that's more engaging if you're not sitting in front of the code right now and changing it.
Took me awhile (can I say a dog's age? the dog would still be a puppy) to get through it, but I got a lot out of it since at multiple points I read about the motivation for a refactoring and got a deeper understanding of why specific past code of mine was bad while learning how to fix it.
Many times "code smell" was used I'd hear "YOU HAVEN'T THOUGHT OF THE SMELL" in my head from Always Sunny. If one person reads this and starts hearing it too I will have fulfilled some purpose in the world.