dhorthy

7 ms·

91.
by dhorthy 1y ago
I have had a user story and a research plan and only realized deep in the implementation that a fundamental detail about how the code works was missing (specifically, that types and sdks are generated from OpenAPI spec) - this missing meant
92.
by dhorthy 1y ago
My advice - never use compact, always stash your context to Md or a wordy git commit message and then clear context You want control over and visibility into what’s being compacted, and /compact doesn’t do great on either
93.
by dhorthy 1y ago
You don’t think early c programmers spent a lot of time reading the assembly that was produced?
94.
by dhorthy 1y ago
I appreciate the share. Yes as I said it was a pretty dang uncomfortable to transition to this new way of working but now that it’s settled we’re never going back
95.
by dhorthy 1y ago
File size matters if you don’t have strategically placed “read the entire file” instructions for certain parts of the workflow (we do)
96.
by dhorthy 1y ago
yeah flat, simple code is good to start, but I find I'm still developing instincts around right balance between "when to let duplicate code sprawl" vs. "when to be the DRY police".
97.
by dhorthy 1y ago
i 100% agree - the folks who are best at ai-first engineering, they spend 3 days designing the test harness and then kick off an agent unsupervised for 2+ days and come back to working software. not exactly valuable as guidance since progra
98.
by dhorthy 1y ago
yeah its kinda funny how some bigger more sophisticated eng orgs that would be called "slow and ineffective" by smaller teams are actually pretty dang well set-up to leverage AI. All because they have been forced to master technic
99.
by dhorthy 1y ago
letting people pick their own editors is a zirp phenomenon
100.
by dhorthy 1y ago
yeah if you read our create_plan prompt, it sets up a 3+ phase back and forth soliciting clarifying questions before the plan is built!
101.
by dhorthy 1y ago
Claude code is Claude code, whether you use in cursor or not Codex and Claude code are neck and neck, but we made the decision to go all in on opus 4, as there are compounding returns in optimizing prompts and building intuition for a speci
102.
by dhorthy 1y ago
i think the general take away for all of this is the model can write the code but you still have to design it. I don't disagree with anything you've said, and I'd say my advice is engage more, iterate more, and work in small
103.
by dhorthy 1y ago
thank you for the feedback! themes are hard. Update going out now
104.
by dhorthy 1y ago
we can come up with something better :)
105.
by dhorthy 1y ago
i think that was one of the key reasons we built research_codebase.md first - the number one concern is "what happens if we end up owning this codebase but don't know how it works / don't know how to steer a model on how
106.
by dhorthy 1y ago
if you read further down, I acknowledge this > While the cancelation PR required a little more love to take things over the line, we got incredible progress in just a day.
107.
by dhorthy 1y ago
https://en.wikipedia.org/wiki/Product_requirements_document
108.
by dhorthy 1y ago
i mean there's also the fact that claude code injects this system message into your claude.md which means that even if your claude.md sucks you will probably be okay: <system-reminder> IMPORTANT: this context may or may not be re
109.
by dhorthy 1y ago
I would say its much more about abstraction and the leverage abstractions give you. You'll also note that while I talk about "spec driven development", most of the tactical stuff we've proven out is downstream of having
110.
by dhorthy 1y ago
alex reibman proposed hyperengineering i've also heard "aura coding", "spec-driven development" and a bunch of others I don't love. but we def need a new word cause vibe coding aint it
111.
by dhorthy 1y ago
yeah once again you need the right context to override what's in the weights. It may not know how to use the responses api, so you need to provide examples in context (or tools to fetch them)
112.
by dhorthy 1y ago
yes - correct. For the record, if spending raw tokens, the 2 prs to baml cost about $650. but yes we switched off per-token this week because we ran out of anthropic credits, we're on max plan now
113.
by dhorthy 1y ago
I tend to think about it like vim - you will feel slow and annoyed for the first few weeks, but investing in these skills are massive +EV long term
114.
by dhorthy 1y ago
s/unique/lazy
115.
by dhorthy 1y ago
yeah i love that there is a lot of source data for "what is good idiomatic go" - the model doesn't have it all in the training set but you can easily collect coding standards for go with deep research or something And then I
116.
by dhorthy 1y ago
i strongly disagree with this - if anything, using AI to code real production code in real complex codebase is MORE technical than just writing software. Staff/Principal engineers already spend a lot more time designing systems than wr
117.
by dhorthy 1y ago
me too :)
118.
by dhorthy 1y ago
why do you think go is better than python (i have some thoughts but curious your take)
119.
by dhorthy 1y ago
definitely - the standford video has a slide about how many cases caused people to be even slower than without AI
120.
Getting AI to work in complex codebases(github.com)
517 points by dhorthy 1y ago|418 comments

More ›