Become a member
Sign in
Guilherme C. Bertero
Guilherme C. Bertero

Guilherme C. Bertero

95 Following
78 Followers
  • Profile
  • Claps
  • Highlights

Highlighted by Guilherme C. Bertero

See more

From Monorepo: please do! by Adam Jacob

In reality, nobody wants to do any of that shit. It’s way less fun than just fixing the damn API. It’s all human and messy. In a polyrepo, you can j…

From Monorepo: please do! by Adam Jacob

You should choose a monorepo because the default behavior it encourages in your teams is visibility and shared responsibility, especially as teams scale. You will have to invest in tooling no matter what, but it’s always better when the default behavior is the behavior you want to see in your teams.

From The Definitive Guide to Handling GraphQL Errors by Matt Krick

the best: If GraphQL gives you a result with data, even if that result contains errors, it is not an error. No changing HTTP codes based on error types, no reading the errors to decide how “critica…titute an HTTP 429 (too many requests). But at the end of the day, the simplest answer is the best: If GraphQL gives you a result with data, even if that result contains errors, it is not an error. No changing HTTP codes based on error types, no reading the errors to decide how “critical” a parti…

Claps from Guilherme C. Bertero

See more

DevCon 5 — Osaka

Robson Silva

Evite blocos If /else e torne seu código modular com Strategy Pattern

Edmo Lima

Achieving autonomy in the business analytics team aligning people and technology

Luiz Arakaki