3 ms·
The title is click baiting. Prompt engineering is still important. From a philosophical point, it always makes a difference how you phrase a problem. If you f
by roflmaostc 3y ago
The title is click baiting.
Prompt engineering is still important.
From a philosophical point, it always makes a difference how you phrase a problem.
If you formalize a problem in Lean code, it's easy to understand for a proof assistant but not for most humans (even mathematicians or programmers).
So rephrasing the problem in human language makes it easier to grasp and comprehend.
And given the dataset the AI is trained on, there might be certain style it prefers.
If you train it on Lean code, better input lean code.
Also, more context makes it usually easier to solve the problem.
- dartos 3y agoIt’s important the same way code organization is important. You need to do a good job at it, but it’s not something anyone is going to get a full time job to do.
- samus 3y agoTo expand on your excellent point: the danger to programmer jobs is that one day product owners might be able to cut out the middleman and get the job done without the programmers. On the other hand, being able to communicate clearly with the LLM and knowing its quirks becomes even more important. And for quite a while one wouldn't actually trust the output of a model.
- drewcoo 3y ago> the danger to programmer jobs is that one day product owners might be able to cut out the middleman and get the job done without the programmers To do that, they'd need to have some kind of coherent detailed plans that actually made sense in the context of all the minutia of the rest of the system. If the product were built of fingerpaint and good intentions, POs would still need programmers.