I always think that one of the necessary capabilities of engineers is the ability to query materials.
Engineers used to need the library to check information. Now it is much more convenient, just Google it.
For how to use Google to solve the problem, refer to my article:
Http://blog.csdn.net/redguardtoo/archive/2005/04/15/348601.aspx
It's too simple, right?
I am also familiar with a lot of software engineers (regardless of country, age, education...), can really have a sense of information, can be said to be rare. There are countless negative examples.
For example (Question: Is STL thread-Safe ?) :
Http://community.csdn.net/Expert/topic/4006/4006577.xml? Temp =. 6024897.
Google "STL thread safe", the first is the answer. This is much faster than posting on csdn.
Depending on your STL version, you can also Google "vc stl thread safe" "stlport thread safe" to get the answer.
I read the post. The problem is that the main program may have bugs. he suspected that the bug was caused by the use of non-thread-safe STL in multi-threaded programs.
We only need to Google "program debugging" to get the names of debugging books from foreign authors and some Google authors, you can get some articles on debugging for * free * (Article). These articles can quickly solve many bugs (the author's bug may be a typical bug ).
Regardless of the time spent and the quality of information, Google is much faster!