Starting on a large project, should I split it into more concise parts?
Background: Currently an intern at a company and working on repurposing older programs (still in use, but for different departments) for use in testing new hardware. The new hardware is different in terms of register layout and firmware interface from the older iterations of hardware. I have been given free reign on how to setup this project as it is to be used for the new hardware exclusively.
Refactor class (extract methods) in a main / helper classes
Simply spoken, one of my c# classes got too big and I’m currently splitting this class in several subclasses by clustering semantically related methods (actually actions, which do side effects).
Handling fast growing multi-function services
My team has been developing a web business application for more than a year. It started quite small, but now it is growing bigger and bigger. I think it’s time for refactoring.
How far should I expose this status enum?
I wrote a little app to manage an arbitrary series of tasks (e.g., call a SQL sproc and capture out-vars, run another app, run an SSIS package) with dependencies between tasks. Each task has a status (waiting to start, failed and waiting to retry, failed and abandoned, succeeded, etc.). Internally, each Task object has a field of the TaskStatus enum type. There’s a TaskManager object which starts tasks and monitors their successes and failures, and a Dashboard WinForm which displays progress.
How to justify code refactoring time?
Have a very large project more than 70k LOC.
Controllers and re-factoring for maintainability / sensibility
I have read many posts similar to this on the site: however I still am questioning what is best in my situation (also the answers are contradicting from question to question).
What is the term for this type of refactoring
I am sure there is a term for the following bit of refactoring, but I can’t remember it and my Google-fu is failing me!
What are the practical ways to implement the SRP?
Simply what are the practical techniques people use to check if a class violates the single responsibility principle?
How long does one have to wait to consider design change in code?
I had a few days ago. I was having trouble with threads. Had lots of questions asked on StackOverflow and honestly for the first time I did not get the answer I was looking for. Finally, I decided to do a huge re-design of my system code and magically within a few hours I found a solution.
How to deal with code reuse philosophy?
I constantly find myself thinking about code reuse when starting a new project.