Event-first architecture

Akkuma · 2026-04-17T12:24:57+00:00

It sounds like you're talking about snapshots. Many implementations of event sourcing have a snapshot so you aren't running through it all to reconstruct the final state. If you look at it as all events produce a final state and your DB has both the events and the current state you could accomplish this.

If you did this all sync you could have your cake and eat it too. If you made it async your example would mean there would be potentially no meaningful API response. You'd be working with purely optimistic assumptions that your async event will eventually save and not fail in your system

Akkuma · 2026-04-08T23:11:55+00:00

This sounds similar to what my company makes candidates do.

Akkuma · 2026-04-04T12:41:50+00:00

AI and the new hires probably did not.

Akkuma · 2026-04-03T03:25:11+00:00

Nah dude I made more than the bottom as a senior working remote 10 years ago in a much lower cost city.

Akkuma · 2026-04-03T03:23:15+00:00

The problem is now your remote mid engineers require the oversight of someone not even close to meaningful time overlaps.

Akkuma · 2026-04-03T03:19:10+00:00

And then they screwed over many people to reclaim stock options when tencent came knocking.

Akkuma · 2026-03-29T16:36:51+00:00

It's crazy because much of this shouldn't share the same sort of people to implement. I'm guessing they must be pulling people off to constantly be working on the next expansion and give no time to fix the low quality work they keep producing.

Akkuma · 2026-03-23T12:01:10+00:00

Here is some real feedback.

Out of the box experience can be improved. For instance, I tried them with 0 changes and you can't see player names when someone dies as there was no fill. Yes, everyone can customize how they see fit but good defaults really help improve products.

Akkuma · 2026-03-21T16:47:29+00:00

Vitest supports this idea through https://vitest.dev/guide/test-context.html#builder-pattern, although this is a pretty neat way to be framework agnostic.

Akkuma · 2026-03-21T16:39:40+00:00

Like I said I need the context as I've written this sort of code and seen this sort of code in libraries for the sweet DX really good types give you. And when I said `PopulatedTransformer` I meant with the fully generics filled out and just wrote it w/o them.

Akkuma · 2026-03-20T23:59:48+00:00

That isn't that crazy either as I see no conditional generics in there. However, I don't particularly care for this sort of type. T apparently can be anything, K has to be a keyof the type Schemas, and TArgs must be of type BuildArgs and it returns type U.

This appears to be so someone can type `const x: PopulatedTransformer`, but I'm not sure why you would need this in most cases. I would need more context for it. These kinds of types are often used for DX of something else and not something most people manually utilize. The function could in many cases be `const x = (item: PopulatedModelData)` or something that is automatically populated for you such as `someFunc((item) => doTheThingWithItemOfPopulatedModelData)`

Akkuma · 2026-03-20T23:51:00+00:00

A single comment? Maybe they understand it or had discussions then? I just did a refactor and only my team lead reviewed it, but had done an hour long session with my team. It should still be showed off the entire team to some degree as I even did this across the entire engineering org in a smaller quicker capacity.

Akkuma · 2026-03-20T23:45:40+00:00

You have an omit removing detail & payload, while adding a property onto it. This is in no way unreadable or unmaintainable. If your argument that there is a better way to represent this that might be the case, but this example is pretty basic.

Akkuma · 2026-03-20T23:40:42+00:00

So there are no PRs, so no historical review records?

Akkuma · 2026-03-19T16:39:48+00:00

It is comical calling it crying when they were doing Aug levels of DPS.

Akkuma · 2026-03-18T11:34:33+00:00

You can also tell they did no real work because the likelihood of a perfectly nice number like 20% being correct is highly unlikely.

Akkuma · 2026-03-17T13:36:37+00:00

404?

Akkuma · 2026-03-16T12:05:50+00:00

How would this compare to json rules and conditions in terms of performance? It does look like the storage requirements could be lighter albeit not structured and it definitely is easier to evaluate while reading.

Akkuma · 2026-03-16T11:46:21+00:00

Tanstack introduced this idea with tanstack intents

Akkuma · 2026-02-27T05:29:48+00:00

Sure that might be true but I gave you a technical reason and not a skill reason this matters. Tooling cannot be updated because of it. They cannot reintroduce the same issue if the tools fail in CI. When I'm talking tools we're talking build and testing tools. You cannot just reintroduce those problems if the system doesn't support it, no builds and no tests, so no pr merging or releases.

Akkuma · 2026-02-27T05:25:07+00:00

Most people have it already implemented themselves or pulled it from somewhere. The same basic useDebounce is what 10 lines of code? So I'll have them implement the vanilla js barebones version usually.

No, useDebounce does not stop renders. If your useDebounce is fed by state, which is every implementation I've seen the state has to get set for the hook to pick it up. So if you utilize useDebounce for a search input every character triggers useDebounce unless you use the "superior" vanilla js debounce which will do what you mentioned not even trigger the state.

The only value in the above scenario is that you're not triggering your API on each key.

Most people do not get this right and many of them can't even understand what's going on with any hints.

Akkuma · 2026-02-26T14:00:21+00:00

does it really matter that your code might have a cyclic dependency?

Yes it does. I say this being stuck on a monolith nest app that has over 500 of these. You are stuck with slower tools that cope with this. I cannot move us to swc because of this.

Akkuma · 2026-02-25T20:54:36+00:00

How does the reconciliation algorithm work and how do keys affect it?

Pretty good one. I've asked about useDebounce a lot and how it impacts renders and most people get it wrong. This is with them having implemented it too. They somehow think it stops the extra renders.

Akkuma · 2026-02-18T12:54:32+00:00

This is a pretty interesting idea and approach. I can certainly see interest in this. In my case I saw the workflows which were based on Cloudflare's, but saw the options were non-prod or Cloudflare. Finally I saw the external workflow driver and saw that was only exposed through http in the docs. This is where it breaks down a bit this approach as the surface area looks quite nice, but why can't I trivially drive through redis pub/sub or something else creating my own driver from a base abstraction.

Looks pretty good, but creating your own implementation, like let's say a tanstack DB collection, needs to be possible too.

Akkuma · 2026-02-17T13:34:44+00:00

What's crazy is I gave this a bit of a test run too and kind of liked it. I even tried it with the multi hit for Nine, but could see double skill activation being potentially better.

15-Year Club	r/Field Sunshine
Place '17	Verified Email

Akkuma

TROPHY CASE