14

Refactoring! Refactoring! REFACTORING!

This is one of “those desk books” that you gotta have imo. Personally I love giving names to categories of things, helps us better recognize patterns if we can classify them.

Software can always be improved, this book give you a good majority of the most common refactorings it’s like a recipe book almost.. shows you the code smell... give you the detailed recipes to fix it. Great to have in code reviews.

Doesn’t matter that this book is in JavaScript the concepts and ideas are the big pictures in this book.

Classic “one of those” books.

Comments
  • 1
    Subscribes fir #bookOfTheDay!
  • 1
    @rooter I do not complete all the books, some are purely reference only i don’t think I could sit down and read this one front to back, certain sections yes but not all.

    I do have books tho I plan to read thru.. but I’m not one to linearly 1 book to another .. for me it’s like, multiple books started and I choose okay I’ll read a section here from this one then a hour later switch or one day focused on one book and then switch..

    Hard to read for me a full book start to finish without touching another book. I loose focus and get distracted and gotta switch lol
  • 1
    @C0D4 should I change the tag to that for the future?
  • 0
    @rutee07 hahah! So eBay and thriftboosk and a few others have so many of these used for so cheap like less than 10 bucks each sometimes less than 5.. it’s how I get most of my books.. the other way is amazon for the newer books.. OR I use zlibrary or library genisis to get the pdf before I buy and have the pdf sometimes I’ll print it and bind it myself
  • 0
    @QuanticoCEO #bookADay will do.
  • 0
    Like here’s an example of self bound ref man for freeRTOS
  • 0
    Another view
  • 1
    This book was worth the read. It gets dry in some parts. But the concepts are worth carrying over. And considering most of my time is spent refactoring some dumb ass's code that came before me the skill set is useful. The other one I found useful was clean code, but only portions of that book, the writer was a little too fanatical.
  • 1
    @vomitmachine yes yes yes .. LOL happens all the time to me.. and yes I have clean code too, Bob is out there.. I don’t agree with everything .. especially the details .. concepts yes for the most part but many things it’s like whoa to far. Pull it back.. lol clean code .. another book for another day
  • 1
    @QuanticoCEO yeah he had some solid concepts in that book, but others were taken too far. Like singular responsibility is important to uphold, but not the fanatical stance that Bob takes. If you can design a class such that it gets the point across while modularizing functionality with other singular responsible classes then you've done a good enough job. Most of your code will be deprecated less than 10 years anyway.
  • 3
    Refactoring: second edition. Did they... refactor the book?

    I'll see myself out.
  • 2
    I'm late to the game

    But nice keyboard flash
  • 1
  • 0
    @kamen they did! Lmfao
  • 0
  • 1
    @Jilano LMFAOOOOOOO!
  • 2
    @kamen

    Everyone knows you don't buy the book until the second edition. Early adopters get the books that occasionally burst into flames or autodrive themselves into pillars.
  • 1
    @Jilano LOL
  • 2
    @Jilano Hehe what? Nooooo... Would I? 😅
  • 0
    @ScriptCoded Lmfaoo. Sooo FYI mr keyboard stalker ... hahah.. where I live .. there’s no “warning shots” hahah
  • 0
    @kamen Yup, from Java to JavaScript. - Came here to say that there was definitely Java in there, but then I must have had the first edition.
Add Comment