People with deep expertise I think -- and it's no criticism, just human nature -- tend to forget what it was to be a newcomer just starting up a learning curve (or maybe half way up but still trying to learn).
Although I do not consider myself being someone with deep expertise I am able to get by pretty well. At least I do not have to ask many questions anymore as I am usually able to find the answer myself (I already mentioned in one of my previous posts the paths I take in order to get there) .
But for sure I remember the time that nothing seem to work as advertised if there was any documentation to begin with. Very frustrating.
Most of the knowledge I gained wrt pascal programming comes form TP, BP and Delphi and the numerous books that where published back in the day. I still own books with titles as "the tome of Delphi" and "Delphi unleashed" amongst others. The Delphi accompanied Helpfiles literally thought me how to write relational databases with Delphi though I already had experience with RLDB's using DBase.
I can most certainly sympathize with newcomers because a lot has changed (added) over the years and it is a lot to digest. You simply can't learn all that in a couple of days (or even months) and it requires quite a lot of experimenting especially if you do not have something like a guide that is able to help you through that process. But even then, I you honestly think there is people out there that know every existing component from hearth then you got another thing coming. It is something I am still learning about to this day and it is something that will never end.
I more or less disagree with just simply pushing your question to the forums in the hope that will be able to teach you something because it really doesn't. Not unless you put in the time and effort to understand what solution was provided and do your own research based on that. In practice most people tend to just copy-paste an answer with no clue whatsoever with no intention to find that clue either (at least that is my experience though there are some that you can see that really do something with a provided answer and for whom you are able to see and watch them grow over time).
It is far better to try first and when stuck (for example when you read the reference of a component that is conflicting for you and you don't get things to work) ask specific questions about a topic. A simple "how do i use component x" is usually frowned upon especially since when you got the name for the component you can search for it. 9 out f 10 times there exist a wiki article or there is an example present that show how to use the component.
The only way that is ever going to improve is if someone writes a detailed documentation for each and every existing component showing all kind of use cases in which the component can be used. tedious, tiresome and boring work that nobody really wants to waste time on/with. Most wiki articles only mention some specific details about a component and which is mostly based on questions asked in the forums (or otherwise). Ofc there are exceptions such as for a simple example the rgba components but even there it is only the tip of the iceberg of what those components/classes can actually do.
2 cents.
Recent
