Oracle's official documentation is indeed a great resource, but it depends on who holds it.
Many of you might have had this experience: you ask a question in a forum, and the common reply is "Go read the official documentation, figure it out, and then go to sleep." There's no denying that Oracle's official documentation is excellent—comprehensive, well-organized, and expansive. However, simply telling someone to dive into the official documentation right away is probably not the best approach. Anyone who has read the official documentation knows that it can be challenging to fully understand, and the likelihood of reading through the entire documentation and grasping all its intricacies is very low. Even top-tier Oracle experts probably haven’t read every single word of the massive documentation. For beginners, learning solely through the official documentation is not very practical, unless you have a good command of English and some basic knowledge of programming and SQL; otherwise, it’s difficult to "get into the game." Trying to read all the documentation is both a waste of time and unrealistic. The purpose of the documentation isn’t for you to read it all; it’s there to be consulted when you don't know something or encounter a problem. It’s important not to lose sight of this.
What you need to learn Oracle are three things: the official documentation, an experimental environment, and the internet. As for books, they can come later. Of course, you can systematically learn through the official documentation, but I don’t think it’s necessary to read every single word. Instead, you should focus on the key points, digest the core elements of each module, run through the examples, and leave the finer details for later. This is like building a house: first, you need a design blueprint before construction begins; first, the big picture, then the details. If you focus on perfecting the small details from the start, you might end up picking at the sesame and losing the watermelon—a fruitless endeavor.
What readers need to think about is how to make the best use of the official documentation, how to maximize its benefits, and how to improve their English skills, rather than overthinking it. Many ideas sound great in theory, but reality often pours cold water on them. This reminds me of a thought that popped into my head yesterday: when you’re filled with hope, the next moment might very well lead to disappointment. Oops, I’ve gone off-topic.
So, my advice to readers is: it’s not reliable to jump straight into the official documentation. Of course, you should consider whether what I’m saying is right or not—this is just my humble opinion. Finally, for the sake of sounding profound, maybe I’m wrong about everything I said.
Visit the https://payhip.com/OracleeBookSoftwareShop website to get an e-book about Oracle internal storage.
Top comments (0)