#484 in Computers & technology books
Use arrows to jump to the previous/next product
Reddit mentions of Writing Solid Code (Microsoft Programming Series)
Sentiment score: 5
Reddit mentions: 7
We found 7 Reddit mentions of Writing Solid Code (Microsoft Programming Series). Here are the top ones.
Buying options
View on Amazon.comor
Used Book in Good Condition
Specs:
Height | 9.07 Inches |
Length | 7.37 Inches |
Number of items | 1 |
Weight | 1.45946017444 Pounds |
Width | 0.85 Inches |
I've posted this before but I'll repost it here:
Now in terms of the question that you ask in the title - this is what I recommend:
Job Interview Prep
Junior Software Engineer Reading List
Read This First
Fundementals
Understanding Professional Software Environments
Mentality
History
Mid Level Software Engineer Reading List
Read This First
Fundementals
Software Design
Software Engineering Skill Sets
Databases
User Experience
Mentality
History
Specialist Skills
In spite of the fact that many of these won't apply to your specific job I still recommend reading them for the insight, they'll give you into programming language and technology design.
Could it be "Writing Solid Code" by Steve Maguire? https://www.amazon.com/Writing-Solid-Code-Microsoft-Programming/dp/1556155514
Anyway, it's still one of my favorite. Highly recommended.
The "Spot the bug" posts here are like that although I think they are c++ (http://blogs.msdn.com/b/rsamona/).
Books like Writing Solid Code (http://www.amazon.com/Writing-Solid-Microsoft-Programming-Series/dp/1556155514) are also helpful if you're going to be writing a lot of C or C++ code. It has some helpful ideas about how to build C code that is debuggable.
Steve McConnell's Writing Solid Code is also good. As are the other two in Clean Code's "Frequently Bought Together" section.
Besides what has been mentioned, these two are also good:
: teaches good design practices in C.
> going through your 800 lines of code to figure out where the bug is
Hmmm, Developer here with 30 years experience.
It sounds to me like you seriously need to learn about debugging. It's something of an issue because most CS courses don't teach how to debug code with anything like the application they should, instead you're sort of left to figure it out on your own.
This is really really old now, and concentrates on pure C, but the techniques it describes are just as relevant today as they ever where and if you see a copy anywhere worth a couple of hours skimming.
https://www.amazon.co.uk/Writing-Solid-Code-Techniques-Programming/dp/1556155514
You can replace the implementations of C++'s operator new and delete with your own that do extra processing to ensure all memory is released properly. You would normally only implement this in your Debug builds. When you release an official version of the program to customers you would just remove your modifications (e.g. via an #IFDEF).
Steve Maguire tackles this in his book Writing Solid Code.