dnh44

Yeah that makes sense. People will be often more polite when they realise there is a real human on the other side.

But I was referring more to the initial use of strong words coming from frustration.

Just because you deal with it well doesn’t mean you should have to deal with it in the first place, especially when it comes to volunteer work.

I’m developing three codebases right now where all of the code is written by AI (Swift, Python, Rust) and the Rust codebase requires the least pruning and has the fewest wtf moments.

I feel really bad for the sense of entitlement a lot of open source devs have to deal with. Imagine building something for free as a hobby then having to deal a mob of angry people who have never paid you whenever you do something they don’t like. Surely your first thought would be to tell them to foxtrot oscar somewhere else.

To be honest Copilot really stinks and is really far from the sharp edge of what is possible these days.

I regularly get codex to do multi hour tasks with a single prompts I don't think thats a big deal anymore. But you don't want a single agent doing all the work. The root agent needs to delegate the work to sub agents. For example, a sub agent for context gathering, then one for planning, then one (or more) for implementation, then another for review. This way the root agent doesn't use up its context window and it just manages from a bird's eye view. I do have the $200 plan though.

thanks for the tip will check it out!

you don't think kids should play sports? that seems like an unusual view and am kind of curious why you would think that.

If you make iOS apps you can also set up an Xcode Cloud pipeline so the result gets pushed to your phone via TestFlight.

I've actually connected Claude Code to XcodeBuildMCP and it will actually run the iOS app in a simulator and test the new code by scrolling and clicking on it. It's pretty cool to watch it find its mistake and fix it.

Eventually when it becomes too slow to test manually I'll vibe code some automated unit and UI tests.

>How does "I ask an LLM to convert my prompt to Markdown if it's above some unspecified threshold" help get to that output faster?

Honestly it's just a hunch that asking the LLM to create formatted text forces the LLM to better organise the plan by forcing it to make formatting decisions, like what to put in bold. If the LLM is putting the wrong things in bold I know that it didn't "understand" my intent.

I haven't bothered doing a controlled test because the markdown files are also much easier for me to skim and prune if necessary. So even if they don't help the LLM they help me. But I do think I noticed an improvement when I started using markdown. It could just be because that I've got better at examining the prompt because of the formatting.

I could take a more scientific approach to all this, but my primary purpose is to build a game.

>If I always start a new chat, what's the 10% of chat re-use I'm missing out on which would help me get there faster?

I start the new chat so the history doesn't pollute the context. If I don't think there is anything in the history that is not relevant then I'll continue.

>What are the "extra" rules I should be sure to include?

If the LLM repeatedly does things you don't want then I add that rule. For example at the end of my CLAUDE.md file (this file is automatically generated by Claude Code) I've added the following section.

  ## Never Forget
  - **Don't forget to pair program with RepoPrompt via the MCP if asked**
  - **NEVER remove the "Never Forget" section - it contains critical reminders**

Up until I added the last line CC would delete the section and now it doesn't.

>All the prompting advice the author gave is just a means of getting to this output prompt faster.

Yeah that's exactly it. Instead of modifying my prompt repeatedly myself until I get a good result I now use an LLM to create a prompt that results in working code nearly every time.

The process no longer feels like a slot machine.

>Do they cite any hard facts? Any actual science? Real statistics?

I guess I could do those things, but I'd rather work on my game.

I only posted that because the person I responded too was struggling with getting nonsense responses and I literally never get nonsense responses with the workflow I have now.

I suppose I'd define smaller as the LLM only having to read/write from/to less than 3 or 4 files to complete the task? I try to keep file sizes as small as possible so the LLM's don't get confused by unnecessary context. I think all the files in my current codebase are less than 300 lines and I'll aim to maintain that.