| ▲ | rand17 2 days ago | ||||||||||||||||
So you don't like writing "the boring code". What do you expect from writing a CRUD? What would you like to write? What "interesting problems" would you like to focus on? Great sadness will fall upon the industry when the last graybeard dies, who had this arcane knowledge of "writing code". I have bad Player Piano vibes nowdays. Around me devs are beginning to warm up to the idea, that they are not coders (and neither should I be), but "prompt engineers". When I take too much time on a task, when I can't solve a problem with a push of a button, when I muse about copilot hallucinations in my PR - someone usually comes helpfully to tell me, I need better prompting skills. Have you tried this expression? Have you tried more context? Have you tried with this copy pasted magical formula? No creative worker in human history was so overjoyed to devalue his or her work and knowledge in such haste. | |||||||||||||||||
| ▲ | mittensc 2 days ago | parent [-] | ||||||||||||||||
Other side of the equation: I remember learning C++ with something like valgrind. I would write stupid code, validate, fix stupid issues. Others before me learned the harder way. With LLMs right now I'm learning frontend by just generating the UIs I want. I'm getting the code/mocks and experimenting. It's bad code, i will need to adjust, but it helps immensely as a starting point same as valgrind helped in the past. Trying to learn via searching for info just doesn't work as well with all the flood of spam. | |||||||||||||||||
| |||||||||||||||||