|
|
|
|
|
|
by da_chicken
2793 days ago
|
|
|
It's kind of like learning how to program when you don't have any task to complete. Especially for a data store of some kind. If you've ever tried to learn SQL, even if you've got an example database, you'll find it's incredibly difficult not because the syntax is all that difficult or the logic is particularly daunting. No, you'll find it's difficult because you don't have any questions to answer. You'll feel, "Okay, now what?" When you try to make up a question to answer, it's difficult to tell if you're answering the question correctly. You need the focus that a real problem gives you. You need the guidance that understanding what the data means gives you (or someone else) to know if your answer is right or wrong. It's easy to see what a tool is designed to do. It's very difficult to see what a tool can be used for and why you might want to use it that way, let alone when you might want to deviate from that or find alternatives due to limitations or new requirements. Or when you might need entirely different tools. We learn best when we're working on a problem. Just like going to the moon required solving a lot of problems which led to major advancements in the 20th century, going to Mars, colonizing Mars, and colonizing the moon have even more challenges. Goals give research and development a clear purpose beyond, "I dunno, make something people want that we can sell." |
|
|