Menu
So, in reading this site, it seems that the shop in which I work does a lot of things wrong and some things right. How can I improve the code that I work with from my colleagues? The only thing I can think of is to lead by example - start using Boost, etc. Any other thoughts?
481
Code improvement at the level of basic blocks is known as local optimization. It focuses on the elimination of redundant opera- tions (e.g., unnecessary loads or common subexpression calculations), and on effective instruction scheduling and register allocation.
For the code to be easy enough to change, it needs to be readable, testable, and reusable. It also needs to be reliable, maintainable, and gracefully handle failures without any user effort.
Clarity: The quality of your code can be tested when it can be easily read and understood by anyone who is not even the creator of the code. If the code is easy to understand, maintaining and extending it becomes easier for an expert who is new at the development process.
You probably have to look more closely at what it is your shop does wrong and what they do right. What can you actually change there? What can you change about your own practices that will improve your skills or that of your team? It can be difficult to realize change in an entrenched shop. Try proposing code reviews (on your code first), which could lead to discussion.
For tangible items, I'd look at Scott Meyers' Effective C++, etc. Develop your skillset and you will either help improve others around you or move on to a shop that will. Also, look at the Gang of Four's Design Patterns book.
133
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
