If you’re a product owner and want to work with a team from bespoke software development company that will develop your product, imagine the following situation. You’re a sport team coach and your task is to draft a team of players that will guarantee a victory in the championship. Who you need is a star that will lead your whole team and a ball handler guy who will turn your idea for the game into a game plan. You will also need a glue guy who will pass the ball smoothly and dominating centers who will score points. A dirty job guy may also come in handy to check whether you are turning your strategy into life. “OK, but what does sport have in common with software development”? you may ask. Not much. But it was a fun way to start this blogpost. ;)

Quality Assurance Specialists are inseparable members of agile development teams. Yet, for many, their role is quite vague. It is usually associated only with testing developers’ code. While this is true to a large extent, there is also much more to what QAs can bring to your project team. Realizing this will allow you to better understand how development teams in Netguru work and see the role of quality assurance more clearly. Here are some not so obvious benefits of having a Quality Assurance Specialist in your project.

A lot of businesses decide to start a collaboration with an external Ruby on Rails development team. As using remote support is becoming more and more popular in different businesses, it is crucial for stakeholders to understand both the opportunities and the potential risks of such an approach, and to be able to verify the skill and experience level of a software development agency.

Elixir is a language based on Erlang VM, which means that there are more than 30 years of experience in building good virtual machines under the hood. This and the beauty of Elixir  programming have convinced many companies to migrate some or all of their services using this language. Here are some of them:

When creating a product, many clients have concerns about the work of professionals who will be implementing their idea. This is accompanied by many questions: whether it is better to choose less experienced programmers for less money or more experienced but more expensive. Naturally, the latter may incur higher costs for the project, but only in the short term. In the long term, an experienced developer will prove to be a much better – and eventually cheaper – option than you expect.

Can a single mistake of a software developer ruin an entire company? The answer is yes, but only if the company doesn’t know how to learn from its past mistakes and grow as an organisation.

GraphQL has grown a lot as a technology since it was released in 2015, and at the moment of writing this article, it has been adapted in 20 different programming languages and has been used in production by many companies across the world. If you want to know why this has happened, you can read a short explanation why Github decided to move to GraphQL and read our in-depth article on the topic here.

The article was originally published on ITProPortal. When you build a great product, sooner or later, it will be attracting more and more users who will expect a performant, irreproachable app. As the app grows in time it handles more requests per minute. If you’re not prepared for this the app performance will drop and you will potentially lose your audience. In this blog post we explain what you should pay attention to when building a scalable app.

Put simply, abstraction in programming organises system functionalities in a way that allows us to build apps efficiently. It gives the code base structure that is easy to understand and maintain. Sounds cool, right? However, if you don’t use abstraction correctly, it may do more harm than good.

This week Facebook has officially announced React Fiber, a new version of its popular JavaScript library for building user interfaces. The news from F8 2017 - Facebook Developers Conference that took place on 18-19th April - raised many questions and concerns among founders who developed their apps using React. Is there anything to worry about? Does this mean that they will have to rewrite their apps?