Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure.
— Martin Fowler, quoted in What Is Refactoring
Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure.
— Martin Fowler, quoted in What Is Refactoring
In the conclusion of a three-part series, we discover the final piece of the "testing private methods" puzzle.
A question that I hear a lot is: "Do you test private methods? And if so, how?" In this, the first of a series, we'll talk about where private methods …
Join guest chef Kerri Miller for a whirlwind tour of three essential utilities for evaluating specific qualities of a Ruby codebase. See how to map out the dependencies in a …
Playfully experiment with potentially redesigns of your Rails code, by temporarily removing ActiveRecord dependencies that would otherwise cramp your creative style. Guest chef Nick Sutterer shows you how!
Programming is hard, but sometimes we can overcomplicate things for ourselves. Join guest Chris Doyle to learn why a problem that feels "TOO HARD" is a code smell, and what …
You've heard of User Experience (UX), but what about DevX? Join Aja Hammerly to learn how to give your APIs a great Developer Experience.
As interview techniques go, whiteboard problems and greenfield apps aren't a very good test of the kinds of skills a developer needs day to day. Join Nicholas Means to learn …
An optimization for your Ruby refactoring sessions. This page is just for members. Sign in or subscribe to gain access! Username Password * Remember Me Forgot Password
Is there such a thing as a method that is too small? Is it worth it to extract a method just to satisfy a guideline like the Law of Demeter?