Chris Kiehl

He mentions this being a follow-up to a similar earlier post: https://chriskiehl.com/article/thoughts-after-6-years . HN discussions on that post: https://news.ycombinator.com/item?id=25887373 (4 years ago|686 comments), https://news.ycombinator.com/item?id=32162716 (3 years ago|58 comments), and https://news.ycombinator.com/item?id=41633156 (4 months ago|56 comments).

Event sourcing is a pattern (antipatern?) that appears useful because it solves an interpersonal problem. It is the kind of thing that middle management salivates over because it appears to decentralize control, which to such a manager sounds like "gives me more control of my own sphere". Every team creates their own event schemas and subscribes to other teams' events and we all live happily ever after. Never again will we have to wait on some other team to spin up an API for us! It promises an engineering solution to engineering itself. I could write and write and write about it, but this rather infamous blog post is so good I'll just link it. https://chriskiehl.com/article/event-sourcing-is-hard

Hearing that other people struggled with this problem gives me solidarity. It took me an embarrassing amount of time to get "click and drag thing" working in isometric [0]. Rendering differently sized sprites was a whole other thing. Figuring it out without google was immensely satisfying, though. Reminded me what I love about programming. [0] https://chriskiehl.com/article/home-theater-calculator

Sure, I was talking about the workaround mentioned here: > You can also invoke any arbitrary executable [https://chriskiehl.com/article/gooey-as-a-universal-frontend], not just python, which is pretty handy. Rhetorics aside, you can use Gooey for any CLI tool using a small Python glue (pardon the pun) code, so it was not a flat out lie.

It means going from: Frontend > React > [state management library of choice] to Frontend > Data Layer > View Layer (React) This is MVC, no? That's basically the diagram for MVC on the Wikipedia page. I suppose giving it a "-first" (god I hate this trend) moniker spiffs it up a bit. We could also name it "modern MVC" for ultimate internet points. I'd also read this article (not mine): https://chriskiehl.com/article/react-as-an-implementation-detail Pay attention to the caveats. Specifically: > The complex pieces usually warrant it, the simple ones usually do not. There's nothing original or revolutionary in these ideas, they're often just forgotten. And that's probably why we do React with ad hoc Redux today. It's the path of least resistance. Why think about boring business rules and how to model them with lots of tiresome boilerplate when you can just throw up a prototype in React. You could probably fit a good argument of why so many people reach for NoSQL over SQL in there too. Ultimately, all code starts simple. So you're screwed from the start. Only later do realize your code is a mess and your lack of modeling is causing chaos everywhere, from one-off TypeScript interfaces everywhere to lots and lots of null checking.