Everyday Rails

Start with what you know

August 24, 2020
This post isn't directly or exclusively about Rails. It's from a writing idea I had a few months ago, to share more general thoughts on being a good software developer, teammate, and communicator. I abandoned the project, but liked this piece, and wanted to share it. Expect a few more similar to this in the future. I hope you find it useful!

The next time you need to learn something new, start with what you know. Then apply that to learning the new thing.

Let’s take the approach I took to learn test-driven development on Rails. At the time, TDD was still a new concept to me, but I’d written and released a handful of Rails apps, and manually tested each one through the browser. More importantly, these were real apps with real users. If something was broken, I’d hear about it fast!

But manual testing and releasing software into the wild without a safety net don’t scale, and I knew that. So I took what I had—reasonably sound software that I trusted—and applied it to what I needed to learn.

Starting small, I focused on simple, tiny tests that covered functionality that obviously worked in my applications: data entry validations, relations across different classes of objects, string manipulations. If the tests failed, I could be reasonably certain that it wasn’t the application’s fault; it was the test. And if I wasn’t so certain, double-checking my work was as simple as loading an object into the Rails console and experimenting with it.

Once I’d mastered these simple tests, I gradually moved to more complex examples that took inputs from different sources, requiring several objects to play nice together, and eventually full-stack tests interacting not just with Rails, but with front-end code, external APIs, and the rest of what’s considered a full web stack.

As an added bonus, as I mastered each layer of testing, I improved my apps’ test coverage. Again, these were real, production apps, not toys never intended for public consumption. I delivered value as I learned.

It’s not just for testing–I’m using this approach now, as I need to get more comfortable with modern front-end development after a few years focusing more on the back-end. Tools like Webpack and Tailwind CSS are new to me, but they’re just different, more efficient ways to accomplish things I already know how to do.

Technology moves quickly, but don’t discount what you already know. Look for ways to apply that knowledge to what you need to learn next, and build new skills on top of it, deliberately.

What do you think? Follow along on on Twitter or Facebook to let me know what you think and catch my latest posts. Better yet, subscribe to my newsletter for updates from Everyday Rails, book picks, and other thoughts and ideas that didn't quite fit here.

Black lives matter.

I stand with the Black community against systemic racism, police violence and brutality, intolerance, and hate in the United States and worldwide. We must all demand better from our leaders, and ourselves. Stop tolerating intolerance.

While you're here, please consider making a donation to Black Girls CODE, who do great, important work to provide opportunity to underprivileged girls interested in tech, or any organization working toward equity and safety for all, not just the privileged. Thank you.

Test with confidence!

If you liked my series on practical advice for adding reliable tests to your Rails apps, check out the expanded ebook version. Lots of additional, exclusive content and a complete sample Rails application.

Newsletter

Ruby on Rails news and tips, and other ideas and surprises from Aaron at Everyday Rails. Delivered to your inbox on no particular set schedule.