??? 07/11/06 04:05 Modified: 07/11/06 04:11 Read: times |
#120000 - An old chinese wisdom says... Responding to: ???'s previous message |
Rodrigo said:
I don't agree with everything you wrote. I'm sorry! Rodrigo said:
I'm sure about two things... First, you have a lot of experience in both areas: HW and SW Much experience in hardware, but not so much in software. Rodrigo said:
...and second, you'd never got there without help from teachers, experts or books. To be honestly, I'm a physicist. I never learned hardware or software in school or elsewhere, I tought it myself. Rodrigo said:
What I'm saying is that there are times when you can't find answers in books or you can't find your teacher so you come to Inernet and ask. No, not to "ask", but to read and to learn. Rodrigo said:
What I tried to say is that the code will not solve your problem, it will just help you isolate problems. Rodrigo, the problem with newbies here, and why they seem not to get adequate help, is, that they come here and tell with two or three lines that they have a problem. We, who we want to help, suffer then from a total lack of urgently needed details. Then, after several askings for more details, they come (if at all) with a chaos of "code", uncommented, unstructured and totally confusing. They, themselves cannot explain, why they have "coded" this or that, or what the "coding idea" behind was. A newbie must learn to work in little steps. Make a very little step, confirm that everything is working, then, and only then, make the next small step. This means, that the project must not be solved in total, by ONE circuit and ONE software, but that you desgin simple circuit snippets and check them by the help of simple but exactly the point hitting code snippets. For instance, to check, whether a PC accepts the data transmitted by the UART of your micro. Only, if this little check was successful, make the next step, for instance trying to address the LCD by your micro. Again with a tiny circuit snippet and a simple code snippet. Just to check the timing, or what else seems to be problematic. Then, if all these modules are working, add them to the total project. Again, step by step. When following this methode for a few times, you will see how powerful this way of developing is. You will become a master in designing circuit and code snippets, in finding mistakes and failures and you will automatically begin to think in terms of modules, hierarchies and priorities, which is so essential when solving much more sophisticated applications. Now, you will say: "But that will consume a huge amount of time!" Yes, but still an universe less than when trying to do the whole project at once and then having to fight at many many fronts, because nothing works. Beginning to despair will be the consequence then and urgently begging for "working code"... An old chinese wisdom says: "If you are in a hurry, move slowly!" Kai |
Topic | Author | Date |
IMPORTANT FOR TESTS | 01/01/70 00:00 | |
Establish telephone connection (Voip) | 01/01/70 00:00 | |
We had no internet! | 01/01/70 00:00 | |
More | 01/01/70 00:00 | |
1) just visulaize 2) baloney | 01/01/70 00:00 | |
An old chinese wisdom says... | 01/01/70 00:00 | |
English version | 01/01/70 00:00 | |
I am just waiting for the inevitable | 01/01/70 00:00 | |
lunar lander | 01/01/70 00:00 | |
snippets | 01/01/70 00:00 | |
Good Idea or Not, Not a Job for the Pros | 01/01/70 00:00 | |
The problem with sample code. | 01/01/70 00:00 | |
Strategy | 01/01/70 00:00 | |
think positively | 01/01/70 00:00 | |
Non-trivial | 01/01/70 00:00 | |
who said it is trivial? | 01/01/70 00:00 | |
He said "just".. | 01/01/70 00:00 | |
He never attempted to do it... | 01/01/70 00:00 |