All my customers are in US and Canada, so switching to EU will automatically add latency to everything. That's a deal breaker for me, so I end up hosting on DO TOR cloud. At least it's not hosted in US but it is by a US company.
I think clean architecture matters a lot, even more so than before. I get that you can just rewrite stuff, but that comes with inherent risk, even in the age of agents.
Supporting production applications with low MTTR to me is what matters a lot. If you are relying entirely on your agent to identify and fix a production defect, I'd argue you are out at sea in a very scary place (comprehension debt and all that). It is in these cases where architecture and organization matters, so you can trace the calls and see what's broken. I get that largely the code is a black box as less and less people review the details, but you do have to review the architecture and design still, and that's not going away. To me, things like SRP, SOLID, DRY and ever-more important.
The thing with justice is that when you look past it in one place, you don’t really get to ask for it in another. I’m talking about Gaza - it set the precedent that the U.S. and its client state, Israel, can get away with anything. Nothing is out of bounds, criminality is normalized, and accountability is dependent on the identity of the victim. Now that the victims are people affected by the stock market manipulation (people in the West), suddenly we’re interested in justice.
I use openspec and love it. I’m doing 5-7x with close to 100% of code AI generated, and shipping to production multiple times a day. I work on a large sass app with hundreds of customers. Wrote something here:
This is the second endorsement I've seen today. I gave OpenSpec a shot and was dismayed by the Explore prompt. [1] Over 1,000 words with verbose, repetitive instructions which will lead to context drift. The examples refer to specific tools like SQLite and OAuth. That won't help if your project isn't related to those.
I do like the basic concept and directory structure, but those are easy enough to adopt without all the cruft.
This is a great post, thanks for sharing! Over the last couple months I fell into my own unique (but similar) spec driven workflow and couldn’t help but start building my own tooling around it. Since you’ve clearly thought so much about this I would really value any feedback / criticism / reactions you have.
I am still a few days away from open sourcing the stack (CLI / API & Server), plan is to gather as much feedback as I can and decide if this is worth maintaining.
A ticketmaster competitor doesn’t sound like a huge technical challenge unless you’re operating at scale. So my first question would be why do you have a large codebase so with so few customers?
I've been using TideWave[1] for the last few months and it has this built-in. It started off as an Elixir/LiveView thing but now they support popular JavaScript frameworks and RoR as well. For those who like this, check it out. It even takes it further and has access to the runtime of your app (not just the browser).
The agent basically is living inside your running app with access to databases, endpoints etc. It's awesome.
It's a server-side app whose GUI is in the browser, a bit like Electron or what have you.
I guess my question is does Tidewawe only work with a fixed set of known "frameworks" like React and Next, or is it a more general purpose tool for analysing an app based on its source-code and the HTML it produces for the browser?
I suspect it’s mostly a naming convention. Wars are often labeled after the territory where the fighting occurs rather than the actors involved. That’s why we say “Ukraine war” or “Iraq war,” even though multiple states may be involved.
In this case, “Iran war” is a bit misleading because the conflict is largely a missile and proxy confrontation affecting several territories (Iran, Israel, and parts of the Gulf), not just one battlefield.
Personally, I find it clearer to name conflicts after the primary actors involved. For example:
Russia–Ukraine war
U.S. & Israel–Iran war
That makes the participants explicit instead of implicitly framing the war around a single country or location.
Seems to be convention. If you search for "Russian war", the top hit is "Ukraine war", second hit "Ukraine-Russia war". Most results seem to mention both parties but when brevity is needed, the place where it's taking place seems to take priority over the belligerents
Just observing, not saying it's a good or bad linguistic practice
Because we're sitting here on the American side. In Iran it's probably called the America war or the Israeli war.
Another way to name wars, when they aren't happening to you, is based on where they happen. The war is happening in and around Iran. It's very unlikely that Iran will manage to bring the war to America. You could also call it the Gulf of Persia war.
You can also name them propagandistically, as in the "2023 Israel-Hamas war". Thankfully this hasn't happened in this case.
Ukraine war, Nagorno Karabakh war, Iraq war, Kosovo War, Gulf War, Falklands War, Vietnam war, Korean war, wars frequently are named for where they are fought.
Point of view. If you are American its the war with Iran. If you are in most other English speaking countries you would go along with that. That said, I have also seen it referred to as "the Middle East war" and one headline calls it "Trump's war".
reply