logoalt Hacker News

1659447091 • today at 9:55 PM • 0 replies • view on HN

> some of us come to these threads hoping for useful discussion about getting the most out of the models we have access to

`gpt` is the the overly pedantic team member that no one invites to game night, while `claude` is the "idea" person and the reason company meetings now requires a meticulously scoped itinerary down to the minute. If you know how to work with both types and which type of work each is better suited for each, you can get a lot more out of them. As another comment made: gpt is depth-first, while claude is breadth-first.

Re-using agent files doesnt work. Give claude detailed task boundaries about what a feature should do (and only do) and then a hard config setup. For gpt you tell it the feature scope in noraml discussion terms without worrying about coming back to find a simple rest crud form is now a single page web-app -- even though your users instructions say no javascript -- with 50 ways to ingest a 6 field form that step over each other and looks like it works but probably has bugs waiting to bite you.

For claude: strong settings, well designed hooks, skills, linters and code checkers fully set up to your standard, and a rules & standards system that is emphasized in every single instruction and agent file. Also a standards agent or skill that is used with a critique/review run that is a requirement of the `/goal` (this can go in a hook too).

For gpt: that isnt as important or needed and will probably start to piss you off because of how literal it is. Your rule for online activity: Respect robots.txt; ask the agent to use clojure cli with deps.edn to add a library; agent replies (the dependency repository's) robots.txt says it does not allow automated access. Explain to the agent that means bots and web crawlers not resolving a dependency from the dependency repository. So less really is more. Instructions and prompts is where verbosity helps. Tell it you want a 6 field rest crud form and it will make a 6 field rest crud form. It will also give you directories full of measurements and checks and performance for each one of those 6 form fields. Restrict it at the user instructions and task level spec. If you dont want all 50 checks for each form field, tell exactly what you don't want in its instructions. It's a fine line but the pedantic types will probably love it.