"seam" dates back to refactoring & software engineering literature that pre-date LLM use by 20 years -- see Working Effectively With Legacy Code for one example (https://www.oreilly.com/library/view/working-effectively-wit...). Its a great book, still use techniques from it everyday.
"load-bearing" I have never heard used for programming before Opus, and its incredibly annoying and over-used.
Seam is used liberally throughout because it captures the idea well (i.e. a place where you can cleave ball of mud code apart to begin refactoring efforts in an isolated way) and that takes many different forms throughout the book whether that be via methods and classes, source files as a single unit, linker seams, on and on.
AFAIK there is nothing like this out there, because there is not one standard for a "pull reauest" in the sense of how a web based forge does it. and it gets complicated quickly due to complexity of git and forks.
Weird that searching for it didn't yield any results, though I stand corrected.
However it seems that select is the actual "root" of documentation. Filter sends to find_all, find_all sends to filter or select.
This post sets up a straw man from the outset, and only gets worse from there.
I understand how we got here, where many experienced programmers, managers, and bloggers only know capital-A Agile as the watered down version sold via certifications, crummy medium posts, and atlassian flavored kanban boards. But that isn't agile.
I can’t even with the pitch into spec driven development as some sort of high watermark of software methodology.
Wow. So much hate in the comments here. Of all the funding / equity events lately, I wonder how this one gets so much doubt and distrust from the start.
If this isn’t something to at least root for, in the sense of a small team, novel product, serving a real need, then I dunno what is. You can use jj or tangled and still appreciate improvements to git and vcs on the web in general. Competition amongst many players is a good thing, even if you don’t believe in this one particular vision.
Heaven forbid it isn’t 100M going to a YC alum for yet another AI funding raise.
Nothing in this project looks vibecoded. I compel you to try vibecoding this in a couple weeks if you think it’s possible, and then after that to build a business out of it. If the only thing stopping you is the code, you should give it a try.
Yeah /simplify is your friend. That and constrained prompts - “refactor x for simplicity - resulting diff must remove n lines of code. Dont change tests. “
They're talking about before it's configured by the user. It defaults to 'free' models so that the user can ask a question immediately on startup. Once you configure a provider, the default models aren't used.
This has been the case for 15-20 years at least. It’s only now that the horrible experience for regular users is so obvious compared to Linux becoming quite good, and Mac OS ranging from fine to meh.
The continual recall/ai push from Microsoft has not helped at all and is pretty gross. There is a way to do a “recall” style thing that some folks will really want if they can trust it. The msft approach has been the opposite of that.
"load-bearing" I have never heard used for programming before Opus, and its incredibly annoying and over-used.