Thoughts from our Developers

Did you know that MySQL initializes with a temporary server, which can make orchestrating a containerized app more complicated? Using a custom health check, we can work around this little quirk.

Duck typing is an effective way of decoupling and future-proofing code (and also settling stupid food debates).

Let's consider a couple common issues where Ruby on Rails applications might inadvertently reveal too much information--posing security risks.

When you're working on a Ruby on Rails application, the Model-View-Controller (MVC) pattern usually captures most of what you want the app does. But not everything fits neatly into MVC. Sometimes, you need to make decisions about where to put logic that doesn't quite belong in a model, view, or controller.

It shouldn't be this hard to write tests for API-connected functionality in a web app.

Dev containers are the cheat code to getting really old Rails apps running on modern hardware.

Most Rails apps don't (or shouldn't) need a full time person to keep them running.

Rails 7.2 introduces a clear maintenance policy with defined support timelines, making it easier for developers to plan upgrades—learn how this change impacts older versions and how Neomind can help keep your app secure and up-to-date.

Dev containers are a great augmentation to Docker containers when trying to get legacy Rails applications to run on modern hardware. This post explores my experiments getting a Rails 4.1 and Ruby 2.3 app running on an M1 Macbook Pro.

Some people don’t think “sustainable software” means what I think it means. What would you call it?

In a groundbreaking shift in digital stewardship, our company is stepping away from the outdated Ruby on Rails framework, embracing a future that aligns with the rapid pace of technological evolution. After meticulous research and introspection, it has become evident that to remain at the forefront of innovation, we must pivot towards methodologies that are not just current but are on the cusp of tomorrow's technologies.

In a world that’s constantly on the move, we often find ourselves caught in the relentless cycle of accumulating tasks, creating invisible queues in various aspects of our lives. A cluttered kitchen sink full of dishes is a perfect embodiment of this problem. It not just occupies space but robs you of the ability to use the sink freely for other needs. Let's venture into the transformative concept of a 'zero queue', a philosophy that promises not only to save time but to unlock unforeseen opportunities and values.

In the world of app development, sustainability means creating software that not only solves today's challenges but is also designed to adapt and evolve, efficiently facing future needs. Whether you’re a developer or a project manager, consider this your friendly guide to building software that lasts—without wearing out your team in the process.

Are you a seasoned Ruby on Rails developer struggling to land your dream job? Or worse, any job at all? Applying to cold jobs across many industries is a nightmare right now. Maybe you’ve fired off rounds of applications each day, with only a few resulting in an interview that ultimately leads to nowhere. Or, you’ve spent hours applying to jobs that you’re qualified for, but you never even hear back.

Ruby on Rails is a sustainable choice for both app development and developers. This open-source web application framework is renowned for its simplicity and flexibility, enabling the swift creation of robust applications.

Sustainability is a concept that has been around for centuries. In modern times, the word sustainability has become synonymous with environmental causes. While that association is valid and important, there are other forms of sustainability that need conscious consideration.

As AI continues to evolve, so too does the concern that we'll be effortlessly swindled out of our personal and financial information by cyber tricksters armed with voice cloning technology.

Conspiracy theorists crow that AI is going to take away all of our jobs and make the human worker obsolete, eventually leading to war and the decline of civilization as we know it. The robots will rule with a heavy mechanized hand, and the average person will be out on the street selling pencils from a cup for scraps of bread. A scary prospect indeed.

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.

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.

A codebase that has been refactored after interacting with the real world is beautiful.

​Developed by a moon-lighter, built by a team that's no longer involved, or stewarding open-source contributions, get confidence in your application.

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.

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. 

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).

One crucial-yet-rare skill needed to prevent a codebase spiraling into “legacy” status is developer empathy.

Neomind Labs does not require onboarding or handoff from your developers to contribute to your codebase in a meaningful way. We have an extensive history of successfully onboarding ourselves.

Sticking to the standards evangelized by the community and adding proper documentation (possibly in the form of useful tests) makes onboarding a breeze, which creates more productive developers, which makes hiring more accessible, which reduces your “bus factor.”