Mastodawn

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 thread

myrmepropagandist Apr 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 thread

rhempel

@futurebird I would offer that most of writing code is knowing when to not write code :-)

There's fun in writing, sure. But then there's docs, and tests, and bugs, and the biggest killer of productivity - ego.

That being said, there is no substitute for having fun with code, learning new techniques or ways of thinking about algorithms, fundamental data structures, and debugging.

At some point, young developers need a mentor to help them hone the skills that they have a passion to use.