Best practices articles by our experts
While writing your app, you’ll likely need to delete old, merged code branches. It’s important to maintain a healthy, clean codebase, which will boost your development team’s productivity. They won’t need to wade through obsolete branches in search of the right one, and they’ll be much less likely to make costly mistakes.
Here’s a short tip for all programmers out there: do not push by force to gem repo. Why?
Stakeholders - and, as some would claim - Project Managers in particular, are often dismissive of the quality of the code produced by a software development team. They care about fast results, about delivering on a project and quickly moving on to the next one. This topic came up in a recent discussion in which iRonin’s CEO, Cyprian, participated - and he has some strong opinions on the subject. One of them is that spaghetti code is not at all as tasty as it sounds, and that the developers who produce it are solely responsible for it.
Often improving performance means saving money, and vice versa - when looking into how to save money, we can find ways to optimize the performance of Ruby on Rails apps. We care deeply about efficient and economic work, so we often come up with solutions to save money, development time and make our jobs easier.
Apr 21, 2017
Today I wanted to have a closer look at the different ways for passing boolean arguments and assigning default values to them.
Mar 31, 2017
When you work on a project that’s been around for quite a while, you’re probably going to - sooner or later - encounter a few skeletons in the closet. These skeletons might be sections of code or design patterns that people know about, know they are bad, and yet no one is addressing them for various reasons. Probably because nobody wants to do the redesign if the code just “works” - even if it’s terrible. What’s worse is when these same structures or patterns are being repeated, because people are blindly following them!