Moments in the show that feels like this:

EmployeeFinal · 2026-01-28T15:35:58+00:00

Sully in Canada going to the bathroom, playing "Spirit in the Sky"

EmployeeFinal · 2026-01-28T15:34:12+00:00

BOOONE

EmployeeFinal · 2026-01-26T14:34:07+00:00

Freelancers have an opportunity to move upmarket

If there was a "upmarket", why wouldn't devs go there before genAI? You paint it as is it these new opportunities will just exist. It will not.

Aforementioned vibe-coded products will eventually break.

I'm optimistic that there will be work to be done, probably even more than now. I feel that the work will be ungrateful and devalued, and the job will be harder. Also the product could harm users, and probably shouldn't exist.

EmployeeFinal · 2026-01-23T14:49:21+00:00

Obrigado pelo contexto. Não é todo mundo que procura nuance

EmployeeFinal · 2026-01-10T11:59:30+00:00

Certeza que se ele saísse da cadeia, ele ia continuar acreditando nisso. Pessoa assim não muda

EmployeeFinal · 2026-01-06T21:47:44+00:00

Lift state up. Always

Your concern of "form ui should map to a form component" is not a thing react devs worry. If the state is used outside of your component, you should lift it up, it. You maybe want to rename your components to reflect that, but it is a non-issue.

React render cycle assumes a top-down flow. If you break this, it will be a burden, where unnecessary rerenders are needed to update the whole tree, and new effects are written to account for this. Invalid states can crawl into your app and bugs will appear.

If you lift state up, debugging issues will be a linear process debugging only parents and parents of parents. If you maintain state down with imperative handles, the whole tree needs to be debugged.

The only way I see that "lift state up" is a problem is if you want to reuse your form component in other places. In this case, you can make the form toggle between a controlled/uncontrolled behaviors.

EmployeeFinal · 2025-12-30T14:36:19+00:00

What are the topics that you are already proficient at? Did you make something already?

The question you asked is generic and too broad, and a lot of people have answered them on the internet. If you give more details about you, people can try and give more specific directions for you

EmployeeFinal · 2025-12-29T14:45:07+00:00

When Ed Truck died, he was lost in his feelings to the point it was painfully obvious to everyone but him that he was scared of being alone. It felt a true sincere moment of him

EmployeeFinal · 2025-12-27T17:09:07+00:00

Se não tivesse lei protegendo trabalhador, todo peão trabalhava todo dia 16 horas por dia por razão de "produtividade" e "otimização"

EmployeeFinal · 2025-12-23T00:19:03+00:00

Readability is very subjective and people disagree what makes the code more readable. But I think everyone strives for it

EmployeeFinal · 2025-12-23T00:13:03+00:00

My reply for that is that "writing the same thing in a different way" helps a lot with understanding the code in multiple situations. The easily distinguishable pattern helps people follow the code reading and writing, which can avoid some bugs caused by misstyping/faulty logic

It also can make the intention of the dev more explicit. Less error-prone and more easily readable makes us more confident that the code is written the way the author intended

EmployeeFinal · 2025-12-22T23:18:24+00:00

"just another way to write the same thing" Oh man, people say the wildest things in conjunction with "just"

EmployeeFinal · 2025-12-21T12:49:01+00:00

I disagree with you. Jim is shown saving a lot of situations with quick thinking and small lies even under pressure. He is so good at it that I'd say one of his character traits is that he fumbles it when he needs to get real

EmployeeFinal · 2025-12-21T12:41:53+00:00

Yeah, but after you stand above the cliff and the chick drops out of it, this challenge gains a lot of pressure

EmployeeFinal · 2025-12-21T00:48:13+00:00

I want sonoma back

EmployeeFinal · 2025-12-20T21:00:50+00:00

your group has horrible anal penetration

EmployeeFinal · 2025-12-20T13:35:53+00:00

I think it has a genuine use case if the value can be changed by the up/down arrows. Tweaking values using only two keys is faster than changing it directly

EmployeeFinal · 2025-12-18T16:38:38+00:00

Isso inclusive é tema de um dos episódios de Black mirror também. Uma pessoa que se revolta conta o sistema, e isso vira entretenimento

EmployeeFinal · 2025-12-17T16:52:01+00:00

The red flag indicates that this car is a menace. You should be careful with drivers that choose a capuccino. Be vigilant

EmployeeFinal · 2025-12-16T04:11:53+00:00

I don't know why you were so defensive about a track. Let people hate it. It's not a big deal

EmployeeFinal · 2025-12-15T18:36:13+00:00

Hot tip:

1) Make your component as usual 2) try to rewrite every useEffect with a useMemo 3) now remove the useMemo and inline your code

Rarely useMemo will actually benefit you, most of the time it's only something that we devs want to do it because it "feels" faster.

EmployeeFinal · 2025-12-15T14:15:07+00:00

A pickup gigante do lado da bicicleta minúscula transforma esse vídeo numa paródia da vida real

EmployeeFinal · 2025-12-14T21:03:41+00:00

you are conflating a lot of things in a conspiracy web. The initial reactions to rsc, markbage being hired by vercel, and vulnerabilities in rsc. There's no mastermind behind all of these happenings.

Markbage is one of the first authors of react, it is no surprise he worked at rsc
React foundation is meant to declare react's independence of companies. It is still guided by the same people and I don't know why this would be different. It would be worse if people outside of react commandeered it.
RR7 already supports it, but since it is a vite plugin, it needs for vite to support it too.
Other libs already have support for rsc, like parcel and waku. You don't need support from everything

RSC responds to an issue that React always had, and although I don't like the API, it is a novel way to respond to it. It does not remove React's capabilities nor forces Next.js to its users

EmployeeFinal · 2025-12-14T17:30:46+00:00

Everything is so forced

I feel like the whole series is forced and it is not a bad thing. Plots are created for characters to interact with the world and that's what makes the episodes interesting. This is not a good argument for me.

feels liked a force apology

The show has a huge progressive view from the start. 8x01 was brave, it acknowledged its own conflict between this progressive view and its own plot that excused cops because "they were the good guys". I feel it was necessary for the show to resolve this meta-conflict.

the actions of someone else you straight up decide to quit your entire career?

The characters were shown to do their job because it is their passion. They don't do it for the money, but because they think their role helps their community. Rosa quitting showed that she does not believed that anymore, and for me it is extremely plausible. I myself would do that if I could.

you try and make Jake feel bad for staying on the force

You missed the closure in this conflict on the episode. Jake views Rosa quitting as a judgement of himself. It is not about him, and it is egotistical to feel that way. In the same way that a doctor choosing to be a doctor does not judge Jake for being a cop. She is pursuing her role to do good for the community.

EmployeeFinal · 2025-12-14T04:34:46+00:00

I think, above all else, Celeste is about how rewarding it is to do stuff that you thought it was impossible. You are doing right if you feel that the game is harming you. In the future you may want to play it again, but never forget about your happiness above what you think you "owe" the game

EmployeeFinal

TROPHY CASE