> A prompt complex enough where it won't get any wrong ideas has to contain as much information as the output would have.. so just write it.

This is only if the output is fully compressed. Writing is not just about encoding the writer's ideas but also about how the reader will ingest those ideas. The writer needs to consider when to put in rests in between complex ideas to help the reader flow through the text. This suggests the LLM could be prompted by a dense complex idea to be presented with the boilerplate needed for the human mind read smoothly and without unnecessary effort.

I thought that as well and then realized I had inserted the word "of" before "using" where there's an implied "by."

The types of skills from FPS games and real fighting are much further apart than gaming and ATC. A closer analogy would be a coworker who knows Judo is needed for Greco-Roman wrestling. Very different sports with different rules, but the skills in building and navigating a mental map of the environment carry over.

I think FPS skills might translate very well to drone operator.

This whole fiasco could have been prevented had the operator included "Make no mistakes" in the prompt.

Or: You are an expert chatbot.

> nowhere in the announcement is coding mentioned

It's right there in the middle benchmark bar "LiveCode Bench" 72%.

All unit tests can pass if you don't assert anything. Just have to make sure to read through all 130k lines of code to check.

This post misses that the people selling their "I built" SaaS advertised as a hobby/passion-project are just marketing something as indie that they fully intended to get rich from the beginning. It was never even a hobby worth giving away for free, it was always an attempt at making an easy fortune because they bought into the dream that infra was selling.

it's probably been thrown out the window compared to office and chatgpt

"If you refuse to estimate, you’re forcing someone less technical to estimate for you."

This is the perfect approach, given that estimates are top down and work to fill the estimate is bottom up.

"When I estimate, I extract the range my manager is looking for, and only then do I go through the code and figure out what can be done in that time."

Except managers also have expectations of what can be done