To me, it seems obvious that AI will attack this from both directions - upskilling developers to make more design changes AND upskilling designers to make more design iterations and more changes to the codebase -- the design artifact is "new react components" (which can be re-implemented or not) instead of a figma design.

1) commit messages often capture the "why" something changed - versus the code/tests which focus on the what/how for right now.

2) when you have a regression being able to see the code before it was introduced and the code which was changed at the same time is very helpful in understanding the developer's intent, blindspots in their approach, etc.

ideas:

1) maybe add a .yml example to the readme under the /test_nyno screenshot so i know how you configured that workflow

2) what are ways to trigger a workflow? just tcp?

3) the example runs "bestjsserver" which looks like it runs workflows? are some workflows auto running? that just logs from tcp commands you manually running in other terminal? a bit confused what's going on here

Thanks!

In 2021/2022 before it was built:

* Here is what that lot looked like [1]. To assume something wouldn't be built there is optimistic at best. (And there was precedent for data centers at the time - there was already a data center less than half mile away on Vantage Data Plz across the street from Tart Lumber.)

* If you look across the street, ie if the video would have panned to the left, you would have seen the "US Customs and Border Patrol" building - not winning any architectural design awards [2].

For someone who bought their house decades ago, then yes - the area has transformed drastically. But grouping someone who purchased recently with someone who purchased decades ago is a bit muddled.

[1]: https://www.google.com/maps/@38.9991758,-77.4300191,3a,75y,1...

[2]: https://www.google.com/maps/place/IAD146/@38.9981504,-77.428...

https://www.google.com/maps/place/38%C2%B059'57.6%22N+77%C2%...

“Implementing orchestration in a library connected to a database means you can eliminate the orchestration tier, pushing its functionality into the application tier (the library instruments your program) and the database tier (your workflow state is persisted to Postgres).“

That is not a lot of weeks. In fact, that's the bare minimum to get to the plural "weeks".

- blame on file

- scroll to line 123, click on commit to see the change

- ok, that commit wasn’t the “meaningful change” I’m looking for

- click on parent commit

- browse files (for that sha)

- go to file

- click blame

- scroll to line 123 (or similar)

- repeat

https://github.com/moment/moment-timezone/issues/498

There is obviously some cost to expressing the interface between the product/target/usecase. What exact benefit is that cost getting me? do i know that if i expose a certain use case in one target then i have to explicitly decide if i'm going to expose (or not expose) it in a different target, which helps me get consistency/governance between my app as it grows? does it help me "integration test" by application in isolation, in a "similar" way that pact [2] helps with integration testing microservices? (ex: the mobile app relies on X input, but from the ts interfaces, the tool can detect that the web-api is no longer defining an output for that api. if so, is this on the /api/v1/resource level? the openapi schema for a json body response level?). do i get a mono-build-system, where everything flows together and i just say "libmodulor build" and "libmodulor deploy" and I'm good to go?

said in another way: many of the people on HN have a backend api, a react SPA, and a mobile app. what types of problems do i have now which libmodulor solves?

[1] https://ui.shadcn.com/docs/components/dialog [2] https://pact.io/

But I’m still a bit confused on what the project actually “is”. I see you have an architecture and I’m using ts to define the interface between those 4 types of components. But let’s say I have a react-native target: what am I expressing in that interface? A cli which can build/deploy that interface? Each ui screen in that rn app (rn login, rn add contact)? Or all of the api endpoints in the web target which gets called by the rn target?

In the readme, I would focus a bit less on the UML part, and a bit more on the “if I have a webapp and a mobile app, with auth and crud for contacts, here’s what you’d need”

Saying you need todo it for free is bonkers. Students who work in the cafeteria get paid…

And the gap between “a greenfield project” versus rebuilding the app in their infrastructure is so huge… This type of app would take 6 months to build minimum. So insane.

If you only have a few months left, you will barely get out of the initial project scoping meetings talking to all of the various departments (legal, it, hr, etc etc)

I love the clip of @dhh's keynote to engineer's "learned helplessness" to AWS and the cloud [2]. While SST + containers is very very different than DHH's Kamal [3], they both embrace containers without the paas service tax (heroku/vercel/etc) or the overhead of kubernetes.

1: https://www.youtube.com/watch?v=Afpgnb_9bA4

2: https://youtu.be/-cEn_83zRFw?si=oAG3ZUKhXlUIKD88&t=1296

3: https://kamal-deploy.org/