Renato Lacerda

@ralacerda.dev

Web Developer, Open Source enthusiast github.com/ralacerda linkedin.com/in/renato-ac-lacerda/

Crazy how I used to blame my computer/setup when `gh clone` wouldn't work or github was slow to load. And now, I just assume github is the problem (it usually is).

I heard a rumour that they're releasing HTML6 next week, which deprecates semantics and introduces 3 new types of div. Can't wait!

Is it crazy to use prefixes for global css classes when using scoped style (vue and svelte)? - Easier to know where the style is coming from - Harder to get conflicts - 0 specificity with :where make it super easy to override it @w3cj.com & @tolin.ski were talking about hard to find global styles.

Image is a print of the following CSS Code: 
```
:where(.g-card) {
  display: flex;
  flex-direction: column;
  justify-content: center;
  align-items: center;
  padding: 1rem;
  border-radius: 0.5rem;
  box-shadow: 0 0 1rem rgba(0, 0, 0, 0.1);
  background-color: #fff;
}
```

Copilot reviewer is calling attention to the fetch call without `await`. It suggest adding the `await` keyword, but that means it has to include `async` to the `useEffect` callback, which I don't think is best practices for React. I'm not a React dev tho, am I wrong? @joshwcomeau.com @bell.bz

GitHub Copilot code review highlights an unawaited fetch call in a JavaScript file. It suggests using await to prevent unexpected behavior. The call is inside an useEffect call back

One of the coolest things about being middle aged is that (assuming things go reasonably well, statistically speaking) I have my whole life ahead of me! And this time around I actually know stuff and can do things right from the start and I have way more resources. It’s kind of awesome, honestly!