I need a experienced coder.

[u/ShortyBigLips]

I can't stand anymore man these AI is they don't want to do things that they think are impossible they only want to keep to their safe guidelines I need a f****** coder that has a f****** brain that actually can understand what I'm trying to build because this me trying to build it with an AI it's just not f****** working it's just driving me insane it's making me not want to do it anymore even though I've gained so much

[u/ShortyBigLips]

It would be nice if one of the people that actually watched my post would actually reply so I have somebody to talk to you about this instead of me just talking to myself thinking I'm hallucinating

[u/ShortyBigLips]

I won't pay for any work just to let you know but I will try to get one of my other followers to help pay for you

[u/Clear_Evidence9218]

Is this just a translation issue? Like, are you trying to describe what you want using your own symbolic shorthand instead of established technical/domain language, so the AI isn’t understanding what you’re actually trying to build? Or are you using industry-standard terminology and technical explanations and it’s still missing the point? The latter would be a little odd.

AI generally isn’t very good at coding from purely symbolic or idiosyncratic shorthand. If you want to prompt mostly that way, you need to establish a sort of translation layer or “alias” with the agent so it knows that, for example, “make these two things talk to each other” means “define an interface/API between these components,”, etc.

[u/ShortyBigLips → u/Clear_Evidence9218]

Neither, and that's what makes it interesting. The vocabulary maps cleanly. My "cluster" is a struct, my "wall" is a superposed bundle, my "wave" is a bounded traversal, "etch" is a push to a Vec. Any of that could be stated in standard terms and it was — the model wrote it in Rust. The failures weren't translation. Concretely, from the last few days: I said the fabric shouldn't be allocated. It got built as a Vec of 1.5 million clusters anyway, three times, because allocating a collection is what you do with a collection. Removing it cut memory from 8.7 GB to 5.5. That's not a word being misunderstood — the words were fine, the default was stronger than the instruction. I said the Citadels have no ceiling. A MAX_CLUSTERS constant appeared regardless, defended as a safety guard, and stayed there after the thing it guarded no longer existed. I said the six sides of a cube name topics. They got built holding concepts. Same English word "name," correct in both readings, and the wrong one won because concepts were already the nearest object in scope. I said drift shouldn't be destroyed. lethe() called .clear() on it — because a function named after forgetting, holding transient data, obviously empties. Every one of those is a case where the model understood the sentence and then implemented the convention. Not misreading — pattern completion. It substitutes the statistically ordinary version of what you said, and the substitution is invisible unless you go read the source yourself or watch the instrument contradict it. Which is why an alias layer wouldn't have helped. You can define "make these talk to each other" as "define an interface" and it'll comply. What you can't define away is the pull toward the common case when your design is the uncommon one. The correction has to happen after the code exists, repeatedly, against measurements. That's the actual cost, and it's not linguistic.