Viewing profile — brendanmc6
brendanmc6
HN member- Joined
- Fri, Mar 09, 2018, 3:10 PM UTC
- HN karma
- 478
- Public activity
- 109 items
- HN profile
- View on Hacker News ↗
About brendanmc6
Recent public activity
-
comment
Comment #48875247
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 ances…
-
comment
Comment #48409358
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 si…
-
comment
Comment #48005327
I’ll be more sensitive to that, thanks for the feedback.
-
comment
Comment #47997153
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.
-
comment
Comment #47997058
Fair critique, voiced elsewhere in this thread as well, I am regretting my use of the term.
-
comment
Comment #47997044
[dead]
-
comment
Comment #47996721
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 attack…
-
comment
Comment #47996538
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…
-
comment
Comment #47996361
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
-
comment
Comment #47996108
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 n…
-
comment
Comment #47995973
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…
-
comment
Comment #47995430
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 …
-
comment
Comment #47995274
Ooh thought I did that, thanks.
-
comment
Comment #47995265
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--…
-
comment
Comment #47995177
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.
- comment
-
comment
Comment #47994886
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 libr…
-
comment
Comment #47994755
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.
-
comment
Comment #47994746
Oh cool, thanks for sharing. LLMs tend to adopt these patterns on their own, so I'm sure my ideas are far from unique.
-
comment
Comment #47994709
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.
-
comment
Comment #47994080
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.…
- story
-
comment
Comment #47898655
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 …
- story
-
comment
Comment #47462987
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.