3 ms·
I used to agree with this point, but I actually changed my stance. Once you hit a problem that an AI cannot solve, it's good to be at least aware of what's goi
by miki123211 2y ago
I used to agree with this point, but I actually changed my stance.
Once you hit a problem that an AI cannot solve, it's good to be at least aware of what's going on in the field. You don't necessarily have to remember every formula and every fact off the top of your head, but having an intuition on what facts and formulas there are and where they can be used is immensely helpful.
Imagine you're writing a program in an esoteric scripting language that Copilot doesn't understand, and you need to put a large array of events in order from oldest to newest. If you had to learn this sort of think before, you'll immediately have an intuition that this is called sorting, there are slow (n^2) sorting algorithms and faster (n log n) sorting algorithms and you want the latter, and that quicksort is probably a good candidate to start with. You don't necessarily have to be able to write quicksort by hand, you can look up an implementation online and port it to your weird proprietary language, but the intuition is important.
- ben_w 2y agoHmm. That sounds like a different thing than I'm saying, and I agree with what I think you're saying. So, if an AI can answer "what's a fast sort function" with "quicksort, here's some pseudocode: …", that's a related but different question to "write quicksort in [this brand new language you've never encountered before]". Is like how AI won't take our jobs, but it will take over for each individual task that our jobs are made from.