I’m Daniel Fosco, a digital designer working at VTEX.

Writing about your own work can be hard. Writing about a past project is even harder — information is not so fresh and documentation might be lost. Teaming up with somebody else to write about a 3 year-old team project… well, that’s almost archeology, considering I joined the team at VTEX only a year ago.

I teamed up with Augusto, our most senior designer, to write the case study on Smart Checkout, a project that took place between 2010 and 2013 and helped take the whole platform to a new level.

VTEX is an online commerce platform with headquarters in Rio de Janeiro, almost 200 employees and 60+ software developers. Our clients range from big enterprise operations to small shops in over 11 countries around the world.

When I joined the team a year ago, I didn’t really have a lot of experience designing products for the web. Sure, I had enough education and knew how to do design stuff, but no matter how much you train yourself to design things, you will never be prepared to the harsh reality of not being capable to deliver the products you want to.

Writing code is hard. For every 1 minute of bliss typing characters in the computer and seeing it render things that didn’t exist before, there are 10 minutes of frustration with unreadable code and bugs that didn’t exist the night before.

Writing code with Git is hard. Writing code without it is unthinkable. Whether you’re senior developer on a huge team or a designer who just started dabbling with front-end for personal projects, using Git will change the way you code for the best and make group collaboration enjoyable.

This guide will walk you through basic concepts in Git with some hands-on action at the end. It won’t make you a Git master, but you will be able to use Git by yourself with Github and it’s desktop app.