New answers tagged maintainability
0
Some Tests/Indicators:
Turn off the IDE. Can you still read your own code? When there's a bug is it fairly easy to trace through it by hand and figure out what class you'll need a breakpoint in to figure out that's where the problem is? Or when you do use the IDE do you just not even bother and just step through from the very beginning?
Does debug often ...
0
Redmine allows you to configure a hierarchy of projects, and each project has its own separate wiki. The wiki formatting is very simple, so you don't have to go crazy on it. Most wikis we create are just a single page, with links to outside references, a few paragraphs whining about poor code, and then some notes on important @todos.
It also supports source ...
0
Redmine.
Create a project for each of your projects, hook each one up to the SVN section that contains the code and go from there. Each project will gain a bugtracker and a wiki and a way to track changes and information about each project as you determine what that info is. Additionally, you can see the code that comprises the projects and tie it to bugs ...
1
What you are referring to for managing a 'portfolio' of applications is either Project Portfolio Management (PPM) and/or Application Lifecycle Management (ALM). There are numerous tools from low-cost simple management to high-end management.
Do yourself and your organization a favor by NOT trying to put a band-aid on the problem with file based solutions. A ...
2
Instead of a simple spreadsheet or text file, I'd suggest something like TiddlyWiki. It's a simple wiki that runs entirely within a browser, so there's nothing to install or configure. Stick it in a public location and periodically back it up (just commit the file to a Subversion repo). It'll provide a bit of structure without (hopefully) being too ...
2
As Dan points out, having a readme.txt in the project is cruical -- it doesn't need to be thick but it should cover enough to get a trained person building and debugging the code. The key things to cover are external configurations and dependencies and other landmine sort of things.
I would also advise using a project tracking tool with SCM integration. ...
2
Of course you will need to document as much as possible each project but you will also need a centralized "place" where you have your catalog of services/products, descriving the "metadata" of the project as you pointed out: What departement is using it? Who is reposible of mantaining it? What is it used for? What dependencies with other projects are there?
...
3
From what you're describing, it is inevitable that some work will have to be done to get a good idea of what you're dealing with here.
SVN is just the repository. It is meant to store your work in a way that enables you to make mistakes without that leading to big problems. It shouldn't be used to take care of project management!
If you can get some kind ...
8
I use text files inside the project for that sort of thing. They're easy to maintain, easy to find and tough to misplace. Word or Excel would probably work just as well if you need to share but you'll need more discipline to write in some sort of log format so you can easily tell what changed when.
On a side note, I'd aggressively attempt to retire as ...
Top 50 recent answers are included
