People often ask what is involved in setting up a website. Here I take a quick look at the process involved:

How do we manage this workflow?

Well that question is often a prerequisite for any collaborative project these days where for example front end developers need to work back to back with back end guys. Well fortunately there are some great resources out there. One solution includes or utilises GIT, a distributed version control system that was conceived by Linus Torvalds, as I understand it to help develop Linux. GIT when you think about it is a great system for managing version control that is loosely based on the evolutionary tree of life.

Anyway to get you started here's an interesting link that explains a little about the git workflow and the use of branches.

http://nvie.com/posts/a-successful-git-branching-model/

Philosophies for Software Collaboration and Production

Underlying the internet are some great philosophies or ways of thinking and ultimately doing things. So it should come as no great surpise that someone has devized a philosphy for Software collaboration and production. One of the most popular and widsespread is the use of the Agile Software Development philosophy:

"On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground and of course, to eat. What emerged was the Agile Software Development Manifesto. Representatives from Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others sympathetic to the need for an alternative to documentation driven, heavyweight software development processes convened. "

http://agilemanifesto.org/history.html

 

Principles behind the Agile Manifesto

We follow these principles:

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in 
development. Agile processes harness change for 
the customer's competitive advantage.

Deliver working software frequently, from a 
couple of weeks to a couple of months, with a 
preference to the shorter timescale.

Business people and developers must work 
together daily throughout the project.

Build projects around motivated individuals. 
Give them the environment and support they need, 
and trust them to get the job done.

The most efficient and effective method of 
conveying information to and within a development 
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development. 
The sponsors, developers, and users should be able 
to maintain a constant pace indefinitely.

Continuous attention to technical excellence 
and good design enhances agility.

Simplicity--the art of maximizing the amount 
of work not done--is essential.

The best architectures, requirements, and designs 
emerge from self-organizing teams.

At regular intervals, the team reflects on how 
to become more effective, then tunes and adjusts 
its behavior accordingly.

 

http://agilemanifesto.org/iso/en/principles.html