How to deal with almost the same enums?
I need to define enums in several classes. The majority of fields are the same in all of the enums. But one has one or two more fields, another has fewer fields. Now I wonder what is the best way to deal with this?
Naming a class that processes orders [closed]
Closed 9 years ago.
Persuading management that refactoring code is a good idea [duplicate]
Possible Duplicate:
Best supporting argument for refactoring
Recovering an anemic domain model into a multitier architecture
I have spent the past several days learning about domain driven design and attempting to apply it to a current project. I decomposed the problem domain into the canonical logical components: domain, infrastrucutre, and presentation. Having completed a first pass, I stepped back and realized that the architecture I created resulted in virtually all of the business logic being contained in the application services, which is the tell-tale sign of the anemic domain model code smell. After further consideration, domain driven design may not be the correct fit for my application, and even if it is, given the small number of business logic rules in my application, the layering overhead may not be worth it. Since I have only written UML and psuedo code I haven’t invested too much time and effort, but I would like to leverage what I can if it’s possible.
How to implement isValid correctly?
I’m trying to provide a mechanism for validating my object like this:
Rapid prototyping and refactoring
Sometimes when I start a small project (like an android app), I don´t know which approach will work out at the end, and I just go for one approach and give it a try. But if I never used this approach before (for a sort of application I´ve never programmed before) it is like stepping into unknown terrain. I don´t know which libraries to use (maybe I have to try out several libraries) and there are so many unkonwns (like: how to get raw audio data in android)
Refactoring and Open / Closed principle
I have recently being reading a web site about clean code development (I do not put a link here because it is not in English).
Refactoring obscurely commented code
In refactoring code, I came across code that had comments. Looking closer at the comments, I could see that the code was clearly not doing what the comments said.
Quantifying the value of refactoring in commercial terms [duplicate]
This question already has answers here: How can I convince management to deal with technical debt? (17 answers) Best supporting argument for refactoring [duplicate] (7 answers) Closed 11 years ago. Here is the classic scenario; Dev team build a prototype. Business mgmt like it and put it into production. Dev team now have to continue […]
How Visual Studio could help to avoid duplicating code?
I work within a team of developers. Everyone is making their changes without carrying too much if the same thing is already implemented in the codebase. This leads to classes constantly growing and to severe duplication.