| ▲ | psadri a day ago | ||||||||||||||||
Learning to code = understanding a problem, breaking it down into small, manageable pieces, putting all the pieces back together. Debugging. Iterating towards better metrics, etc. All these are amazingly valuable skills/mindsets that can be highly portable to other "problem solving" domains. | |||||||||||||||||
| ▲ | al_borland a day ago | parent | next [-] | ||||||||||||||||
Steve Jobs used to say that everyone should learn to program, because it teaches you how to think. | |||||||||||||||||
| |||||||||||||||||
| ▲ | manyaoman a day ago | parent | prev | next [-] | ||||||||||||||||
This. Even before LLMs it was well understood that you don't really understand a program unless you wrote it yourself. There's just no shortcut for it. | |||||||||||||||||
| ▲ | snek_case a day ago | parent | prev | next [-] | ||||||||||||||||
Yeah I mean, if you don't know how to code, you just know how to prompt, you have no idea how to tell what's a good solution vs what isn't. The best you can do is have the model figure it out for you. You also have no idea how to design a good API, or how to break up a system into modules, etc. The issue is probably that many managers can't really tell the difference between a good programmer and a vibe-coder. The vibe coder ships a lot of PRs. Maybe they themselves ship some vibe-coded PRs. They hate the idea that programmers might know better than them. | |||||||||||||||||
| ▲ | a day ago | parent | prev [-] | ||||||||||||||||
| [deleted] | |||||||||||||||||