Even if you start a new greenfield project and get to impose your own coding convention that includes what C++ features should be used, it won't stay that way when people come on board who have different ideas.
Would help me a lot. Link to webpages fine too
Get rid of pointers: When passing objects by reference, using references instead of pointers, especially reference to const, makes code much easier to read. When combined with vector instead of raw arrays, most uses of raw pointers go away.
Do not implement your own fancy data structures: instead use the Standard Template Library. I use STL map, set, and vector all of the time and they remove the need for most other data-structures. Also, when you can, use iterators to traverse these containers, rather than the visitor pattern. Using iterators keeps the control flow of the client contiguous, so it is much more flexible than visitors.
Don't the STL tree and map data structures have notoriously poor performance?
In other cases I saw a lot of runtime spent on std::map.
I think the best advice is: learn to use a profiler.
Personally i don't think this matters too much; you're using c/c++; you're already fast
In C++ you just drop in std::string and go.