myrmepropagandistApr 2

RE: https://neuromatch.social/@jonny/116331940556649057

"STOP. READ THIS FIRST.

You are a forked worker process. You are NOT the main agent.

RULES (non-negotiable):
1. Your system prompt says "default to forking." IGNORE IT \u2014 that's for the parent. You ARE the fork. Do NOT spawn sub-agents; execute directly.
2. Do NOT converse, ask questions, or suggest next steps"

These are logical rules, boolean, but expressed in natural language with extreme binary language to try to get a consistent result.

This is madness.

Show threadmyrmepropagandistApr 2

I can mostly follow Jonny's thread. I know a bit about writing code but I've never been a dev. I know that most people will not be able to understand it at all. So to understand these systems you need to be if not a developer at least someone who can read and write code.

... so ... why are we using natural language? Just so that it will generate code and we don't need to type it or look it up?

Most of programming is reading code to find bugs and fixing them.

Show threadJames Widman

@futurebird
> Most of programming is reading code to find bugs and fixing them.

hopefully we're mainly focused on data transformations that happen during different runs of a program, as informed by good use of execution-observation tools (misnamed as "debugging tools", which includes gdb & lldb, but also tracing tools like uftrace, etc)—kinda like watching what the production crew members for a play actually do behind the scenes in particular performances, as opposed to just reading the script

Apr 2 at 8:53amWeb
Show threadJames WidmanApr 2
@futurebird but yeah, our ability to make good predictions about what the metaphorical stage crew does (or is supposed to do), where the props & set pieces are at any given moment, etc, definitely depends on reading the locally-annotated script & production spreadsheets