It's weird, right? The US is just hands down strange in some regards to little procedural things that are important but also easy to implement, and yet for whatever reason don't do and make a big deal over it when it's a complete non-affaire in other countries.
Like voter ID. It's not some partisan issue. None of the political parties are fighting Elections Canada over it and its been around my whole life. Its just not a thing(tm). You go to vote, show your ID and and voilà, done. And yet somehow, this is a "big deal" down south?
Ivy league schools , imho, tend to operate differently--more hands-off approach. The assumption is if you're smart and determined enough to get in, that you will not cheat. The filtering to get in is intense, so this presumably filters out less honest people.
The only possible reason for a school like Princeton that is drowning in cash to not proctor exams is to allow students to cheat.
Also: admissions at all these schools are heavily biased toward wealthy legacy hires, regardless of talent, and the "most determined" are the most likely to cheat.
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?
reply