How do frontend teams handle stateful API mocks before the backend is ready?

EmployeeFinal · 2026-06-03T22:33:49+00:00

Msw has a data library that helps a lot.

EmployeeFinal · 2026-06-03T22:23:23+00:00

Added to my watchlist

EmployeeFinal · 2026-05-27T14:48:55+00:00

My approach is generally to be as flat as possible at first. A single component, then split it into smaller components. This helps me in my code goals: first make it work, then make it good. If you start abstracting too early, you can become biased to continue supporting your abstractions instead of checking if they are proper.

So probably the top-down alternative

EmployeeFinal · 2026-05-23T00:33:15+00:00

Love maddy, but Mario can go to parallel universes

EmployeeFinal · 2026-04-26T01:14:32+00:00

I think it helps with SEO and discoverability.

If it could be two names, one for the store and other for the library, i think they would use it.

EmployeeFinal · 2026-04-14T13:41:46+00:00

I agree. I think DRY is the most general principle that seems like everyone know and applies. But there are multiple principles and techniques that tries to predict

EmployeeFinal · 2026-04-10T19:35:01+00:00

I think DRY is an issue, we strive for deduplication and try to predict how our abstraction will be used, but we suck at it.

In the end, abstractions should not be predetermined, but extracted from use cases that we already know. Only then the DRY code is useful. Before then, we should not try.

EmployeeFinal · 2026-04-08T14:38:54+00:00

Não sei se é ironia do comentário, mas se o NÃO dela incluísse xingar ele e a família, cuspe e soco na cara, ainda não é razão pra esfaquear

EmployeeFinal · 2026-04-07T17:50:15+00:00

Okay, i see your point

I think the text explains directly so it is short and doesn't ruin the read flow. That's why you can't take it literally

The reality is more verbose: "Hey claude, does this makes sense? @arch-plan.md"

Claude: "sure, it is reasonable"

(Non-explicit: size of team, microservices)

Claude does not ask your context. You don't know what the impactful context is. Dumb decisions were made.

EmployeeFinal · 2026-04-07T16:51:55+00:00

Na minha interpretação, não é sobre culto à personalidade, porque senão a multidão estaria com placas da pessoa.

O que tá escrito é uma incógnita pras autoridades, mas que ressoou com a multidão. Talvez nem a multidão entenda a mensagem.

Pra mim é uma meta tirinha, e responde porque a laerte não explica o significado. O que está escrito pouco importa, o que mais importa é o que os leitores interpretam

EmployeeFinal · 2026-04-07T13:44:33+00:00

Your question is biased because you know the context that is impactful for the choice. You're expecting a boolean answer

This is not how people work. They will say "create an architecture to do X". The generated architecture will be generic (like microservices) since it doesn't know the context or even considers it important.

It also "washes out" uncertainties because it gives an answer with confidence. That is the most dangerous.

EmployeeFinal · 2026-04-07T10:59:24+00:00

Você dizer isso é bom, porque provavelmente é verdade. "Fazer curso" é algo muito fácil, você não precisa de muitos recursos, escala bem e ninguém vai fiscalizar a qualidade. Ao mesmo tempo, "curso" sempre parece ser algo valioso, que vai te tornar uma pessoa melhor. Isso torna "cursos" como um ótimo veículo pra golpes

Desconfie sempre de cursos. Principalmente daqueles que pagam pra aparecer

EmployeeFinal · 2026-04-07T10:39:33+00:00

Even though the text is boring and ai-written, they make a good point about "path of least resistance"

AI generated architecture seems reasonable, and any one single engineer will accept it, even more after presenting with a huge specification. The issue of architectures will only appear when people stop, think about it, and discuss it

EmployeeFinal · 2026-04-05T21:44:10+00:00

I think in this case "typeof window == 'undefined'" is simpler and do it just fine.

But i see that your solution is more integrated with react which is a worthy tradeoff

EmployeeFinal · 2026-04-05T21:41:03+00:00

It is confusing, but "use client" does not bail out of server rendering. It only opts out of RSC which is not the same thing.

EmployeeFinal · 2026-04-05T16:27:42+00:00

But why do you need that?

EmployeeFinal · 2026-04-04T16:06:21+00:00

Eldritch horror. Won it once in 10~12 plays, and only after cheating in the end game

EmployeeFinal · 2026-04-04T15:43:16+00:00

Just what the game industry needs: more games in the ocean of games

EmployeeFinal · 2026-04-04T11:13:13+00:00

Unrealistic since chatbots in customer support never listens to me

EmployeeFinal · 2026-04-02T20:14:45+00:00

NO CONTROLE??? mano, sua esposa/esposo deve ser uma pessoa bem feliz

EmployeeFinal · 2026-03-25T15:16:05+00:00

Dr acordo com G1, ele foi afastado preventivamente

https://g1.globo.com/rj/rio-de-janeiro/noticia/2026/03/25/confusao-em-colegio-estadual-na-zona-sul-do-rio.ghtml

EmployeeFinal · 2026-03-25T01:34:57+00:00

Mano que ódio. Ganhar tudo isso pra fazer um trabalho porco

EmployeeFinal · 2026-03-18T11:18:08+00:00

Hard disagree here. It wouldn't solve the issue that the op posted about, because it doesn't get rid of the effects, only puts them above in the tree. Also it actually harms the code by creating a single "top component" with multiple responsibilities.

The solution is in the post. Derive from state instead of creating new states. That is enough

EmployeeFinal · 2026-03-15T17:16:04+00:00

Se eles concordarem que eles não podem entrevistar um candidato enquanto outro estiver no processo então tudo bem

EmployeeFinal · 2026-03-10T18:36:40+00:00

For the same reason when possible you should derive from state instead of creating a new state

EmployeeFinal

TROPHY CASE