On the first day of the conference, Eelco Rustenburg - an Agile management consultant, writer and visionar will take the stage to tackle the main topic of the Agile Munich 2019. His keynote will focus on the challenges that the supporting functions like project management / planning organization, HR and finance are facing.
I’d like this to be a reasonably detailed overview of how does the upgrade process in Rails look like in general, but with a strong emphasis on Rails 5.2 > 6 upgrade part (RC1 being the latest release). I’ve already seen a number of great posts describing the list of changes that awaits us in Rails 6, so I will skip this entirely and will focus solely on the upgrade.
One-On-One Session (or O3 in short) is a really powerful tool used by many managers all over the world. It is a well-structured meeting in which a manager/team leader spends some time (usually 30 minutes) with each of his/her team member to discuss progress, strengths, weaknesses, goals and other employee-related matters.
Agile Munich is an event created having in mind agile practitioners from Europe enabling them to meet and interact with other Agile visionaries coming from reputable organizations, share experiences, take part in workshops and lightning talks. This year, Agile Munich takes place from May 8th to May 10th and Selleo will be there!
Change is inevitable. With the constant development of programming, new technologies emerge and companies that want to stay on top need to keep up with them. This is why the problem of how to introduce new technologies to the company and encourage developers to start using them appears.
Created by Google this open-sourced system helps manage containerized applications within cluster environments. It gives developers a better way to deal with related and distributed components as well as services in infrastructure. After Docker became a hit thanks to its wide use of containers, Kubernetes was added to the Docker community as an additional orchestration engine and it became the biggest name in Cloud Native.
Companies developing SaaS can grow overnight. In this kind of software, creation success can happen at lightning speed. A good Software as a Service product can transform a startup into a highly recognizable enterprise. With the popularity growing, scaling will eventually become a priority.
The Ruby on Rails framework is powerful in many ways. One of its strong points is that Ruby on Rails is being shipped with ActiveRecord - an Object Relational Mapping system. ActiveRecord comes up with its own DSL, which lets you write Ruby code, which in turn is translated to SQL, allowing you to use database native features, including “locking”.
Today we are going to add specs (again, we will focus only on the happy paths) for GraphQL queries. But there is one thing about the current implementation of the queries that I don’t like. We have everything defined in one file: `app/graphql/types/query_type.rb`
In the last article we added a few GraphQL mutations to our test application. It is time to create automated tests for each of them. But first things first, we need to set up `RSpec` in order to write better specs.
In this article, I would like to focus on adding GraphQL mutations. We will be working on the test application we created previously in this article. It might be helpful for you to know the structure, models, and types we are using so I encourage you to take a look.
