An easy breakdown of understanding Ruby on Rails.
An overview of special projects, upgrades, and quality-of-life enhancements that keep your application secure and your clients happy!
Have you heard the news? There's a new version of Ruby! A version release is exciting, but when is the right time to upgrade your software? And who should do it? Are there any risks? Find these answers and more in this upgrade guide.
"Done" still requires attention.
A codebase that has been refactored after interacting with the real world is beautiful.
People are increasingly choosing not to start from a blank slate, but to start from something good (or, in some cases, something just okay, or even bad) and make it into something great.
In my experience, most consultancies grow to a specific size and realize that long-term part-time customers distract and slow them down on their primary goal of building and shipping new software as quickly and efficiently as possible.
Please do not hesitate to reach out to me directly if you have any questions, concerns, or ideas for how to make this sudden and unexpected transition to remote work go more smoothly for your team.
Developed by a moon-lighter, built by a team that's no longer involved, or stewarding open-source contributions, get confidence in your application.
Failing to consider the lifespan and maintenance needs of the project when choosing a framework would be nothing short of unprofessional (and as someone who uses Zoolander memes in his blogposts, I know a thing or two about professionalism).