Reorganizing development environment for single developer/small shop
Posted
by Matthew
on Stack Overflow
See other posts from Stack Overflow
or by Matthew
Published on 2010-03-08T19:08:48Z
Indexed on
2010/03/08
19:21 UTC
Read the original article
Hit count: 266
I have been developing for my company for approximately three years. We serve up a web portal using Microsoft .NET and MS SQL Server on DotNetNuke.
I am going to leave my job full time at the end of April. I am leaving on good terms, and I really care about this company and the state of the web project.
Because I haven't worked in a team environment in a long time, I have probably lost touch with what 'real' setups look like. When I leave, I predict the company will either find another developer to take over, or at least have developers work on a contractual basis.
Because I have not worked with other developers, I am very concerned with leaving the company (and the developer they hire) with a jumbled mess. I'd like to believe I am a good developer and everything makes sense, but I have no way to tell.
My question, is how do I set up the development environment, so the company and the next developer will have little trouble getting started? What would you as a developer like in place before working on a project you've never worked on?
Here's some relevant information:
- There is a development server onsite and a production server offsite in a data center .
- There is a server where backups and source code (Sourcegear Vault) are stored.
- There is no formal documentation but there are comments in the code.
- The company budget is tight so free suggestions will help the best.
- I will be around after the end of April on a consulting basis so I can ask simple questions but I will not be available full time to train someone
© Stack Overflow or respective owner