Finding bugs can be a draining experience, especially with limited resources and a small QA team. Increasingly, however, development teams are turning to the bug bash as a solution for streamlining this process, and as a means for gaining more confidence in the quality of their products.
In fact, even big corporations such as Microsoft regularly employ bug bashes throughout their product development lifecycles.
But let's get serious. As the IT industry's high-speed rate of expansion continues apace, so the demand for software developers that increases accordingly results in a growing shortage of programmers looking for work.
How to hire, then? Good question. Although any given company looking to hire a programmer will do what it can to attract the best talent, how can it verify whether or not a particular candidate will be a good fit for the organisation itself?
I’ve spent a comparable amount of time on both sides of the mirror working as a front-end developer and IT recruiter, so in this article, I’ll try to answer this fundamental question and share any relevant opinions.
Setting up a project with Ruby on Rails, PostgreSQL and GraphQL is actually pretty straightforward.
But first, some prerequisites. For this tutorial (tested on versions 2.7.3, 18.104.22.168 and 11.0 respectively), you must have all three, Ruby on Rails, PostgreSQL and GraphQL installed on your development machine.
Some general knowledge of Ruby and Rails is also recommended.
Before we begin, however, you might be wondering why anyone would want to replace the perfectly fine experience provided by the traditional REST API with one offered by GraphQL. Well, one obvious reason is that GraphQL deals quite elegantly with resources over- and under-fetching. With GraphQL you are given the exact information you request - nothing more, nothing less. Moreover, it is almost self-documenting, making that one less item on your list of things to worry about. And there are other pros to GraphQL, such as it being both strongly typed and language and database independent. But in the meantime, I'll leave those for you to explore on your own.
So, without further ado, let’s set up our first GraphQL API on Ruby on Rails.