Sign in

username:

password:



Not a member?

Search blogs



Search tips

Articles by category



Ads

Our Bloggers

See Also

DSPFPGAElectronics

Embedded Systems Blogs > Kunal Singh > Configuration Management: Why Developers are Avert to

Kunal Singh
Kunal holds a master's degree in Micro-Electronics from BITS, Pilani (India). He has been working on Application Programming, DSP Programming, Systems Programming and Hardware Design for the last seven years. His areas of work include Design, Development and Debugging of Embedded Multimedia Systems. | Personal Website

RSS Feed

Would you like to be notified by email when Kunal Singh publishes a new blog?

  

Configuration Management: Why Developers are Avert to

Posted by Kunal Singh on Mar 3 2008 under   

A few reasons why developers have aversion towards "Software Configuration Management Systems"


(1) They do not understand the importance of configuration management. - It is a common and logical reason. But, it is also a very dangerous sign for any organization. If their developers do not understand the importance of configuration management; then it is highly likely that developers even do not understand the other fundamentals of software development. The situation becomes worst when developers try to protect themselves under aegis of "intellectual freedom".

(2) They are not familiar with the repository access tools - It is a quite common reason. There are too many tools actively available. If a developer has not used a particular tool (being used by current organization) before; it is quite likely that he will find it annoying. Some developers are even too shy to reveal that they are not familiar with the tool - which only aggreviates the situation. A simple solution is to have a formal (and mandatory) training for developers on the tools actively being used by the organization as part of developer's induction.
(3) They are shy to put their software on public display. - Some people do have stage fear. Some times this fear is related to the (bad) quality of code being produced (which indeed is dangerous). At times, it is just a psychological bareer. Having some minimum common coding guidelines in place ensures that developers do not find their code at odd and feel at ease.



Rate this article:
0
Rating: 0 | Votes: 0
 
posted by Kunal Singh
Kunal holds a master's degree in Micro-Electronics from BITS, Pilani (India). He has been working on Application Programming, DSP Programming, Systems Programming and Hardware Design for the last seven years. His areas of work include Design, Development and Debugging of Embedded Multimedia Systems. | Personal Website

Previous post by Kunal Singh: Next on Cell Phone Feature List
Next post by Kunal Singh: Speed Up Your Linux Box
all articles by Kunal Singh


Comments


 

leblancmeneses wrote:

4/15/2008
 
I don't understand the goal of this thread but here are some useful links:

client:
http://alexandria.wiki.sourceforge.net/Subversion+Client+-+TortoiseSVN

server:
on linux use your distro's repo manager and install svn

then purchase this book:

Practical Subversion, Second Edition

Add a Comment
You need to login before you can post a comment (best way to prevent spam). ( Not a member? )