O bicho tava bravo KKKK

Também tem a IA dos dois lados, pelos recrutadores que usam pra filtrar currículos, e pelos entrevistados que usam pra criar/enviar currículos.
Aí você que escreveu seu currículo a mão e enviou 1 vez pra empresa, compete com uma pilha gigantesca de currículo feito por IA e spam

Isso é bem complicado, também estou passando por isso.
Mas acho que o problema vem desde a CLT. Custa caro contratar/demitir funcionário, então as empresas exigem muito nos currículos e entrevistas antes de contratar alguém.

The more you watch it, the more you enjoy the slow pacing. But on the last 10 episodes or so, I think they lost touch

O fato deles ainda usarem Flow é insane

Do you plan to merge the react-hooks plugin with the react-compiler one?

But it comes with trade-offs like you mentioned, when combining with a rendering layer like Solid's, you can't do early returns, states are not `just values` anymore, etc.

With Signals, you're back at the expected behavior of normal JS code:
```
let [count, setCount] = createSignal(0);
setCount(count() + 1);
console.log(count()); // Logs: 1
```
It's more predictable and easier to understand.

With React it's different
```
function Counter() {
let [count, setCount] = useState(0);
setCount(count + 1);
console.log(count); // Logs: 0
}
```
To understand why it logs 0, you have to understand how React renders components and triggers updates.

It's also fair to mention that a Signals approach is easier to reason about than the React mental model.
For example, this is what you expect from writing normal JavaScript code:
```
let count = 0;
count += 1;
console.log(count); // Logs: 1
```

Isso me deixa doido. Vira e mexe eu troco no LinkedIn pra ver qual é melhor como palavra-chave

color-scheme: light dark;

I would change to “not necessarily easier or harder”
It’s just different

What happened?

Thanks! I'm missing some tech news but I guess that'll come along once I start reading more tech posts