> Also a request for any resources of scientists trying to get their head around how to write good software, we're all pretty much people who once read a C++ tutorial and just went with it.
I guess this is hard to find, because theres no generic way that will work for all programming languages and contexts.
But i will tell you where i often find them: directly in source code.
People that are really good at this, dont have time to teach, and if they teach, its hard to get to the point to teach the 'tricks' implemented directly in source code.
Also, im my experience, besides the generic algorithms and protocols that you can implement in any language, the rest is very much context dependent.
So in the context of C++, that you have mentioned, there are for instance, at least, two great C++ shops for great source code, experience and tricks that i particularly like: Google and Microsoft C++ stuff.
The problem with this approach, is that you have to be like a 'source code vulture', opening up the engines you are interested in, and willing to expend some time reading and understanding what the source code do.
With this you can match and map with the more abstract knowledge in the field.
I've learned A LOT reading others people source code, specially the 'canonical' pieces of software out there.
Something no book wandering over abstract ideas can taught you about (the first exception to this that comes to mind is Tanenbaum books about OS, but he made Minix as a source code realization of the ideas in the book, so...)
I guess this is hard to find, because theres no generic way that will work for all programming languages and contexts.
But i will tell you where i often find them: directly in source code.
People that are really good at this, dont have time to teach, and if they teach, its hard to get to the point to teach the 'tricks' implemented directly in source code.
Also, im my experience, besides the generic algorithms and protocols that you can implement in any language, the rest is very much context dependent.
So in the context of C++, that you have mentioned, there are for instance, at least, two great C++ shops for great source code, experience and tricks that i particularly like: Google and Microsoft C++ stuff.
The problem with this approach, is that you have to be like a 'source code vulture', opening up the engines you are interested in, and willing to expend some time reading and understanding what the source code do.
With this you can match and map with the more abstract knowledge in the field.
I've learned A LOT reading others people source code, specially the 'canonical' pieces of software out there.
Something no book wandering over abstract ideas can taught you about (the first exception to this that comes to mind is Tanenbaum books about OS, but he made Minix as a source code realization of the ideas in the book, so...)