Our Ingimates, especially the members of our integrated digital agency TOTEM, have been able to benefit from this increase in competence in order to stay at the cutting edge of technology.
This training was a learning experience:
To switch from REST mode to Graph QL
The advantages and limitations of this model
Hello Greg, can you introduce yourself and your background?
My name is Greg, I’m 28 years old, I started development in junior high school at the age of 15.
After this experience I had the chance to join the founding team of Doctolib. The whole REACT stack was set up there. I stayed there for 2 years and finally started freelancing to give trainings. It made me want to do more, full-time. I met Jeremy, my current associate, and founded Smooth Code with him.
Awesome! And what does “Smooth Code” mean?
What is today’s agenda?
GraphQL, rather the server part. We will create an API in GraphQL, discover the best practices, how to do it, etc. We will focus more on the server part, which is the creation of the API.
Who is the training for?
Developers who want to train themselves on a technology in order to be able to intervene at a customer’s site, on a project, to be more versatile. But also curious people, who have heard about it and want to discover the technology.
In fact, training is a time saving: one day of training is the equivalent of 7 days of self-training. In addition, saving time on good practices means avoiding mistakes.
What tools do you use to deliver these trainings?
It’s a fairly classic format for presentation: Keynote but also Powerpoint for the support part but there are also exercises in “red thread”: we start from an empty project, and little by little we embellish it until arriving at a nice thing.
What do you like about GraphQL?
First of all, it’s a fairly recent and technical subject, which I already know quite a bit about. But I wanted to go deeper into it. This was an opportunity for the entire ToTEM digital agency to get down to business, because we believe it is important to keep up to date with the latest technologies.
Then, what I like about GraphQL is that it allows more results for much less effort, the dream! It is intended to replace traditional APIs. It’s efficient, it simply works.
How does this training help you or will it help you in the future?
To sum up in a few words, why would you recommend GraphQL?
Less time to create and maintain, less cost over the long term, less effort, and all for more results.