Author Archives: Anton Shemerey
It’s easy to worry about the costs of updating one’s services, but truly innovative companies consider the risks of modernizing legacy technology too late.
For companies not sure what migration approach will work best for them, we’ve created a comprehensive list of alternative legacy modernization strategies.
Does your company need to modernize legacy software? Here we describe not only what the issues with legacy software are, but how to fix them effectively.
Out with the old, in with the new – that’s how the saying goes. There comes a time in any program’s lifecycle when even the most up-to-date operating system, platform or data management software starts showing signs of age, and it can be tempting to swap everything out for the Next Big Thing.
Metrics mean accountability. They hold the team accountable for the work they’re putting in. This doesn’t mean the metrics are just for managers to hold over everyone’s heads. Their main purpose is to improve the results of the team by pointing out areas of excellence as well as shortcomings. Without metrics software teams might start missing deadlines and produce low-quality work. How long do you think such a situation is sustainable?
But what about being “agile?” Don’t metrics fly in the face of an agile team because they represent corporate structure and bureaucracy? While you don’t want to overanalyze the team, you must have metrics because it shows your clients that you care about the details.
When it comes to technical debt, it’s vital to understand that the debts found in your software code represent more than just lost hard costs. There’s also the “softer” costs that come when the debt affects your team’s ability to get things done. Whether these “things” are bringing new services to market or properly engaging the customer, technical debt often means dire consequences that slow or stop productive everyday work. Addressing technical debt is challenging, and requires a committed approach. Left unchecked, technical debt becomes a cycle, where poor code leads to increased time and costs, decreased agility, less revenue, and therefore less available money for better development. Thankfully, it’s possible for companies to break this cycle by proactively meeting the core technical debt challenges head on.
Smart apps designed to make our lives easier are becoming increasing popular. These range from fitness trackers to lightbulb controls. When designing these apps, you may find you need to improve the user experience. Or you need to access the raw data, but setting up a full stack project would be overkill for this purpose. That is when Electron comes into play.
Electron is a new way to develop modern desktop apps with all the power of Node.js, HTML, and CSS. You can easily complete a functional app in a short time frame, which could solve 80% of your day-to-day needs.
In this example, we are going to explore the Electron universe by creating a simple app that will give us access to the IoT world. Integrating scales from Xiaomi, we will build a “Smart Scale” app that will show the user’s weight in real time. With Electron, the data will be collected and presented in a nice, clean format. Read More
As the Ruby on Rails community becomes increasingly mature, additional time is spent optimizing different aspects of the program rather than creating a completely new web application. This means performance and memory consumption start to play a significant role in its day-to-day development. So now we have much more instantaneous communication, lots of API calls and open connections needs to be processed. This evolution is apparent from the way Rails 5 was developed. ActionCable and API mode for Rails are selling features of Rails 5 due to the program’s advances over time. But what happens if you still encounter problems with performance and concurrency? Luckily, Golang has the capacity to address some of these issues in certain circumstances.
To be clear, however, this article isn’t designed as a complete guide to explain Golang’s most complex facets. Instead, it presents similarities between the two major frameworks of Golang and Ruby. Therefore, the purpose is to compare Ruby on Rails versus Beego. In the process, the objective is to discover familiar ways to perform functions in Go if you already have some experience using Ruby. Read More