brendanmc6

6 ms·

1.
by brendanmc6 6d ago
Why? It is built from Ubuntu[1]. I am a very happy full-time daily user. Anecdotally it is more stable and productive than Windows ever was for me, and plenty of enterprises use windows… [1] https://system76.com/support/
2.
by brendanmc6 17d ago
It takes five seconds to scroll to the bottom and see that it's a Jekyll theme before posting a negative comment
3.
by brendanmc6 2mo ago
Progress is a fiction? What an enraging and awful take. You are living in a world that is so extraordinarily safe, comfortable, populous, peaceful, free and entertaining your ancestors literally would not believe you if you told them. Most
4.
by brendanmc6 4mo ago
I am also quite happy with Elixir output, and it’s much more pleasant to review. Unit test runs are fast, and testing LiveView is overall more pleasant and effective compared to similar Typescript / React projects I’ve maintained in th
5.
by brendanmc6 5mo ago
I’ll be more sensitive to that, thanks for the feedback.
6.
by brendanmc6 5mo ago
Totally agree. This is 100% where I want to be focusing my energy next! A lot to learn and explore still, just need to find the time.
7.
by brendanmc6 5mo ago
Fair critique, voiced elsewhere in this thread as well, I am regretting my use of the term.
8.
by brendanmc6 5mo ago
If you do end up taking a closer look (very much appreciated), take a peek at this security checklist I went over before publishing. I'm also scarred by all the supply chain attacks lately, do let me know if anything is missing. http
9.
by brendanmc6 5mo ago
I think we are actually saying the same thing! We could think of situations where the cache would be verboten (sensitive info), or where it would be mandatory, like in your example, or optional like in my example. My aim was to voice disagr
10.
by brendanmc6 5mo ago
Ah, I should have said explicitly or provided an example of in the post; The tooling expects that you refer to each requirement by full ID e.g. # admin.AUTH.1
11.
by brendanmc6 5mo ago
Here is how I got from Markdown to YAML in a few easy steps: 1. Start with unmaintainable prompt. Add auth to the admin route. It must only be accessible to team members. It must not be accessible to team members with the `quarantine` r
12.
by brendanmc6 5mo ago
I think you are confusing the spec as "this is how it must be built", as opposed to, "this is what the software must do and must not do to be acceptable". To me saying "the code is the spec" is like saying &quo
13.
by brendanmc6 5mo ago
I guess I misappropriated the term then, woops. AI OCD? AI obsession? Whatever you call the behavior that I saw myself and others falling in to. Getting obnoxiously fixated on the tooling and the models to a counterproductive degree.
14.
by brendanmc6 5mo ago
Ooh thought I did that, thanks.
15.
by brendanmc6 5mo ago
Totally agree it's not exciting, even though I am personally excited by it, and I also agree it's not something most people want to try, even though some people do want to try it-- and I found a few of them right here on HN. Dis
16.
by brendanmc6 5mo ago
It's ok friend, all I did is put acceptance criteria in a list so I can parse it and quickly track cross-references. The rest is just Elixir/Phoenix and some creative writing.
17.
by brendanmc6 5mo ago
Fair, I could have made that point clearer. It's a couple things. First is that I finally stopped experimenting with TUIs, harnesses, models, subagents, roles, skills, mcp, md libraries etc. and have mostly settled on this approach, an
18.
by brendanmc6 5mo ago
Should I apologize for being excited about something I built and use daily and for wanting people to try it, discuss it, critique it? Not sure by the tone of your message.
19.
by brendanmc6 5mo ago
Oh cool, thanks for sharing. LLMs tend to adopt these patterns on their own, so I'm sure my ideas are far from unique.
20.
by brendanmc6 5mo ago
Indeed I have a lot of catch up to do, will spend some time with the popular tools before I go too much further down this road.
21.
by brendanmc6 5mo ago
Author here, if you don't want to read all that, I'll post one excerpt that I think sums it up nicely: > My point is, the spec must live somewhere, even if you don’t write it down. The spec is what you want the software to be.
22.
Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML(acai.sh)
287 points by brendanmc6 5mo ago|295 comments
23.
by brendanmc6 5mo ago
Interestingly I have gone the opposite direction and decided that design does not belong in long lived artifacts or docs. I went down quite a rabbit hole experimenting with what I call “specsmaxxing” (wrote about it too, see my post history
24.
Specsmaxxing(acai.sh)
3 points by brendanmc6 5mo ago|0 comments
25.
by brendanmc6 6mo ago
Of course, my point is that these trailing models are close behind, and cost me a lot less, and work great with harnesses like OpenCode.
26.
by brendanmc6 6mo ago
Sure happy to share. It’s been trial and error, but I’ve learned that for agents to reliably ship a large feature or refactor, I need a good spec (functional acceptance criteria) and I need a good plan for sequencing the work. The big expen
27.
by brendanmc6 6mo ago
I’ve been extraordinarily productive with this, their $10 Go plan, and a rigorous spec-driven workflow. Haven’t touched Claude in 2 months. I sprinkle in some billed API usage to power my task-planner and reviewer subagents (both use GPT 5.
28.
by brendanmc6 6mo ago
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 thi
29.
by brendanmc6 7mo ago
Yup and they do, but then I figured out that I can just write loosely structured yaml and the ids come for free. I then encourage the agents to tag and reference them everywhere, especially tests.
30.
by brendanmc6 7mo ago
A few things really leveled up both my software quality and my productivity in the last few months. It wasn’t session history, memory files, context management or any of that. 1. Writing a spec with clear acceptance criteria. 2. Assigning I

More ›