DEV Community

Discussion on: Refactor Rails

Collapse
 
leastbad profile image
leastbad

I'm really impressed by your approach, Chuck. Optimizing for task-based wins is definitely a recipe for success, because it's problem solving instead of hiking to nowhere.

Refactoring can be its own endless sisyphean pursuit (careful!) but it does provide a valuable opportunity to apply what you've learned. Just make sure that your refactoring has a goal. For example, in my applications, sometimes I realize that I'm spending time figuring out how to best cache an action that is taking 0.3ms to complete. Those fractions of a milisecond add up fast, but there's a law of diminishing returns that kicks in.

One thing I strongly recommend is doing some light code review with someone you enjoy working with. You could propose spending an hour a session, half on them and half on you.

You mentioned GoRails and DriftingRuby. Both are great resources. Curious if you've checked out the GoRails videos on StimulusReflex and CableReady? I work on those projects so I'm biased, but I suspect you'll find them pretty exciting. I'm here if you have any questions.