Any competent developer knows there are limits to prompting.

Personally I've found LLM's suck at multi-threaded applications. (Because I've been tempted by the ~agentic loop~ and been burned. Then I hand code the core logic and all is well).

Woe to the developer who tries to prompt their way through this.

I hit a wall with creating a browser based video editor. Up until then, over the last year, I have been taking my hands off the wheel more and more and really have just become more and more productive. This video editor experience has forced me to get more into the code again.

Skill issue /s

But seriously, lots of apps are just glorified NextJS apps which have tons of training data. Something like rust would likely churn out nonsense that compiles eventually but isn't optimal.

sKiLl IsSuE - some redditor XD

Agreed with the caveat that I think if you know what you're doing and are very cognizant, LLM generated Rust is amazing. I feel like it's hard compilation requirements gives a guardrails for a LLM and if it compiles, you're pretty safe against memory issues.

They suck at multi-threading, they suck at maintaining a coherent goal through multiple files, they suck at basic math (claude could NOT figure out how to get the hypotenuse of a triangle given angle and side lengths...).

Sometimes I mess around with prompts just to see what I get back, more often than not, it's mostly a waste of time. God forbid you use it to refactor anything.

while 0:

   x=ctrl-c("output error report")

   eval(ctrl-v(x))

   sleep(10)

   user("Input...")

something like this?

The industry has always found it strangely taboo to actually talk about the wide variance in developer skill.

True because we have pay bands that everyone has to somehow be hired for and fit within.

Is it? I hear about 10xers all the time