How do you organize highly customized software?
I’m working on a large software project which is highly customized for various customers arround the world. This means that we have maybe 80% code which is common between the various customers, but also a lot of code which has to change from one customer to the other. In the past we did our development in separate repositories (SVN) and when a new project started (we have few, but large customers) created another repository based on whatever past project has the best code basis for our needs. This has worked in the past, but we ran into several problems:
How do you name your personal libraries? [closed]
Closed 9 years ago.
Using nested public classes to organize constants
I’m working on an application with many constants. At the last code review it came up that the constants are too scattered and should all be organized into a single “master” constants file. The disagreement is about how to organize them. The majority feel that using the constant name should be good enough, but this will lead to code that looks like this:
Should I implement BackBone.js into my ASP.NET WebForms applications?
Our application is using the WinForms Framework.
Organizing ASP.Net Single Page Application with Nancy
As a personal project, I’m creating a single page, asp.net web application using Nancy to provide RESTful services to the single page. Due to the complexity of the single page, particularly the JavaScripts used, I’ve think creating a dedicated project for the client side of web development and another for service side will organize and simplify the development.
Need some input on storing stdin, stdout, stderr information for debugging
I am working with a legacy system that is not too bad, but I thought of making some improvements to it, and I wanted to solicit your feedback to help me make good decisions. The platform is Linix (different flavors of it).
Big project with many external libraries – source code organisation
I was wondering what is the best way to organize my source code. I was researching on SO and found https://stackoverflow.com/a/1398594/137261 but this source code layout is library specific and doesn’t cover my situation.
Why do we write our specs in different files from our source?
The D Programming Language supports writing unit tests inline with source. There’s a Ruby gem called test_inline that lets you write specs in the same file as your code.
What are standard directory layouts for storing database scripts in TFS?
I recently took over the maintenance of 10-15 SQL Server databases and to my surprise found out that the team does not store the code scripts anywhere. They currently deploy changes to each environment without any paper/code trail.
Organizing related projects and dependencies for nuget publishing
I’ve been working on writing .NET bindings for Rollbar, an error and message reporting service, like Airbrake. My library is working nicely and is published in the NuGet gallery.