Leonardo Negrão

I have been working with React.js since 2019. Since then, the library went through a lot of changes and the community grew.

Next.js became the most popular framework, and with good reason: static pages, API, and many other features. While I used Next.js for the last three years, I still keep an eye for other technologies. I've worked with Angular and Vue for short periods of my career, as well as played a little with Remix which is another popular framework based on React.js.

TailwindCSS facilitates the development of design systems, keeping common classes well defined, while offering an easier way to write CSS, by doing so directly in the markup code.

It works really well with React.js frameworks and is ideal for many projects. There are a few other tools that can be used, such as Styled Components and the much newer StyleX from Facebook.

I use Figma to create modern, responsive designs. Having experienced what Design Systems could achieve, I see the benefit of Figma to create web based designs as it enforces the concepts of reusability that are already present in the development side.

I also used Adobe XD in the past, but given that Figma is now part of Adobe, I decided to only use Figma in my projects. I also use Adobe Photoshop and Illustrator for small tweaks that may be required.

In most of my roles I needed to at least understand the API, while in some I worked as a Full-Stack developer. In all of them, the back-end was written using Node.js. Now, with the trend of front-end taking a lot of responsibilities of the back-end, I am prepared to work with APIs.

Although I never really worked with any other language for the back-end, I understand the fundamental concepts and can catch similarities. I also am familiar with databases.

I have some experience regarding cloud providers, the experience one would expect of someone that had to interact and write code for specific needs. In the past I had contact with AWS and Google Cloud, in general, this included reading logs to debug issues, use storage and fetch data.

For hosting, while I have experience hosting smaller sites in AWS, nowadays I tend to use Vercel (even though Vercel itself uses AWS) for its other features.

I have worked with DatoCMS and Contentful. I don't have a particular preference, so I keep in mind the project budget and what are the needs. I see Contentful as something broader, while DatoCMS is useful por strictly managing content.

I am also keeping an eye in Payload, and played a little with it.

For Analytics, Google Analytics is a market leader and a sensible choice. It works well for general tracking but for something more robust I also worked with HubSpot, which has many features.

It's a decision that tends to be made by the marketing team, which is something I respect.

I've used GitHub, GitLab and BitBucket in my past experiences, and I am familiar with the fundamental features.

However, I can handle workflows in GitHub, and consider a powerful feature for almost any kind of integration. From tests, to task tracking and live previews, I really enjoy using workflows to improve the quality of the work.