What is the best practice for when to check if something needs to be done?
Let’s say I have a function that does x. I pass it a variable, and if the variable is not null, it does some action. And I have an array of variables and I’m going to run this function on each one.
Learning good OOP design and unlearning some bad habits [duplicate]
Possible Duplicate:
What books or resources would you recommend to learn practical OO design and development concepts?
How to write good code with new stuff? [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. I always try to write easily readable code […]
Exception Handling Frequency/Log Detail
I am working on a fairly complex .NET application that interacts with another application. Many single-line statements are possible culprits for throwing an Exception and there is often nothing I can do to check the state before executing them to prevent these Exceptions.
Does studying other people’s programs help in self growth? [closed]
Closed 9 years ago.
Dealing with curly brace soup
I’ve programmed in both C# and VB.NET for years, but primarily in VB. I’m making a career shift toward C# and, overall, I like C# better.
What is the best approach for inline code comments?
We are doing some refactoring to a 20 years old legacy codebase, and I’m having a discussion with my colleague about the comments format in the code (plsql, java).
What would be a non-contrived reason to have an object with Private Copy Constructor as well as Assignment Operator?
Looking for non-conceptual/non-contrived reasons of when one would need to use an object with both a private copy constructor and a private assignment operator?
Programming C++ using Qt4 [closed]
Closed 11 years ago.
Build one to throw away vs Second-system effect
On one hand there is an advice that says “Build one to throw away”. Only after finishing a software system and seeing the end product we realize what went wrong in the design phase and understand how we should have really done it.