

Boring standard coding is exactly where you can actually let the LLM write the code. Manual intervention and review is still required, but at least you can speed up the process.
VGhlcmUgaXMgbm8gZ2VudWluZSBpbnRlbGxpZ2VuY2UgLCB0aGVyZSBpcyBhcnRpZmljaWFsIHN0dXBpZGl0eS4NClRoZXJlIGlzIG5vIHNlcmVuaXR5LCB0aGVyZSBpcyBhbnhpZXR5Lg0KVGhlcmUgaXMgbm8gcGVhY2UsIHRoZXJlIGlzIHR1cm1vaWwuDQpUaGVyZSBpcyBubyBzdHJ1Y3R1cmUsIHRoZXJlIGlzIHBvcnJpZGdlLg0KVGhlcmUgaXMgbm8gb3JkZXIsIHRoZXJlIGlzIGNoYW9zLg==


Boring standard coding is exactly where you can actually let the LLM write the code. Manual intervention and review is still required, but at least you can speed up the process.


My armpits refuse to talk to me. I’ll take that as a sign that overflow errors are a feature, not bug.


Also depends on your level of expertise. If you have beginner questions, an LLM should give you the correct answer most of the time. If you’re an expert, your questions have no answers. Usually, it’s something like an obscure firmware bug edge case even the manufacturer isn’t aware of. Good luck troubleshooting that without writing your own drivers and libraries.


Hacker News?


Realistically though, asking an LLM what’s wrong with my code is a lot faster than scrolling through 50 posts and reading the ones that talk about something almost relevant.
I’ve found some interesting and even good new functions by moaning my code woes to an LLM. Also, it has taken me on some pointless wild goose chases too, so you better watch out. Any suggestion has the potential to be anywhere from absolutely brilliant to a completely stupid waste of time.