Refactoring is great and most developers should refactor more, but there are times when it is not appropriate. Ironically, if you’re aware of these, you may find yourself refactoring even more often than before.
The Noisy Animals kata is designed to help developers think about the process of improving bad code.
Refactoring is essential for software teams to remain effective, but the concept is often misused in conversation to describe work that is not refactoring. Here are some thoughts on what goes wrong when we do this.
Early in the product lifecycle, there’s no one better placed to gather data for business decisions than a developer. Here are some examples of what (and how) Rails developers can contribute with “hacky answers”.
We can do a lot more than generate one line of code at a time with large language models. Here are some other “LLM for coding” ideas.
What executives need to know about DevOps so they can build a successful, resilient product.
If we want clients to create small controllers and use resources in their routes, it’s a good idea to know why. This is a refresher of Derek Prior’s advice from Railsconf 2017.
I often find myself running into mysterious command line errors as I install different development dependencies over and over. Fortunately many commands have an option for verbose output that gives more insight.
More detail on how the thoughtbot team built one of the first Alexa skills in Arabic, and what we learned about using Ruby on Rails to support the development of Alexa Skills in the process.
RubyConf happened last month! It spurred some reflections on the good and bad of virtual conferences.