What pitfalls are inherent in using partial classes?
Over at this question in the comments I mentioned that I heard that partial classes are best avoided if possible.
Pass ID or Object?
When providing a business logic method to get a domain entity, should the parameter accept an object or an ID? For example, should we do this:
Why is Clean Code suggesting avoiding protected variables?
Clean Code suggests avoiding protected variables in the “Vertical Distance” section of the “Formatting” chapter:
Reusable VS clean code – where’s the balance?
Let’s say I have a data model for a blog posts and have two use-cases of that model – getting all blogposts and getting only blogposts which were written by specific author.
Does software rot refer primarily to performance, or to messy code?
Wikipedia’s definition of software rot focuses on the performance of the software. This is a different usage than I am used to; I had thought of it much more in terms of the cleanliness and design of the code—in terms of the code’s having all the standard quality characteristics: readability, maintainability, etc. Now, performance is likely to go down when the code becomes unreadable, because no one knows what is going on. But does the term software rot have special reference to performance? or am I right in thinking it refers to the cleanliness of the code? or is this perhaps a case of multiple senses of the term being in common usage—from the user’s perspective, it has do with performance; but for the software craftsman, it has to do more specifically with how the code reads?
Effective handling of variables in non-object oriented programming
What is the best method to use and share variables between functions in non object-oriented program languages?
Is it bad style to redundantly check a condition?
I often get to positions in my code where I find myself checking a specific condition over and over again.
Constant values in the interface
Some time ago I have read two different books and each of them gives totally different answer for the question if it is a good pattern to define constant values in the interface (in java).
Try/Catch or test parameters [duplicate]
Possible Duplicate:
Arguments for or against using Try/Catch as logical operators
Efficient try / catch block usage?
Which is more maintainable — boolean assignment via if/else or boolean expression?
Which would be considered more maintainable?