<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" ><channel><title>NewPush &#187; software development</title> <atom:link href="http://newpush.com/tag/software-development/feed/" rel="self" type="application/rss+xml" /><link>http://newpush.com</link> <description>Server Hosting, Data Warehouse Hosting, Collaboration</description> <lastBuildDate>Wed, 23 May 2012 03:47:03 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>The Mythical Man Month</title><link>http://newpush.com/2009/08/the-mythical-man-month/</link> <comments>http://newpush.com/2009/08/the-mythical-man-month/#comments</comments> <pubDate>Sat, 22 Aug 2009 14:27:07 +0000</pubDate> <dc:creator>Balazs</dc:creator> <category><![CDATA[Business]]></category> <category><![CDATA[Technology]]></category> <category><![CDATA[software development]]></category><guid isPermaLink="false">http://www.wdream.com/?p=360</guid> <description><![CDATA[Managing Software Development Projects In today&#8217;s world, more and more managers find themselves having to manage an impromptu software project. It usually starts by a need identified by a &#8220;hobbyist&#8221; colleague, who realizes that they can solve a problem by &#8230; <a href="http://newpush.com/2009/08/the-mythical-man-month/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<h4>Managing Software Development Projects</h4><p>In today&#8217;s world, more and more managers find themselves having to manage an impromptu software project.  It usually starts by a need identified by a &#8220;hobbyist&#8221; colleague, who realizes that they can solve a problem by writing a simple software.  Before he knows it, the manager is sucked into the world of managing software development the hard way.  In professional IT shops, it is hard enough for managers to keep software projects on track.  Keeping in line the requirements, the budget, and the time-line is no small feat.  If on top of that, you have to add that you&#8217;re managing hobbyist software developers with no formal training or experience, that can spell disaster.  While <em><a href="http://www.amazon.com/gp/product/0201835959?ie=UTF8&#038;tag=wdr-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0201835959">The Mythical Man-Month</a><img src="http://www.assoc-amazon.com/e/ir?t=wdr-20&#038;l=as2&#038;o=1&#038;a=0201835959" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /></em> might not solve all your problems, it certainly will give you a new perspective making your new predicament easier to deal with.  For example, when you find that your developers find themselves in a cycle of adding yet another feature and the finished product release keeps being pushed out &#8211; this is called scope creep &#8211; you will be able to rely on the guidance in <em><a href="http://www.amazon.com/gp/product/0201835959?ie=UTF8&#038;tag=wdr-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0201835959">The Mythical Man-Month</a><img src="http://www.assoc-amazon.com/e/ir?t=wdr-20&#038;l=as2&#038;o=1&#038;a=0201835959" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /></em>.</p><p>This book is a required reading in  reputable graduate level  computer science curriculae.  Here is the Amazon review of this book:<br /><center><iframe src="http://rcm.amazon.com/e/cm?lt1=_blank&#038;bc1=000000&#038;IS2=1&#038;bg1=FFFFFF&#038;fc1=000000&#038;lc1=0000FF&#038;t=wdr-20&#038;o=1&#038;p=8&#038;l=as1&#038;m=amazon&#038;f=ifr&#038;md=10FE9736YVPPT7A0FBG2&#038;asins=0201835959" style="width:120px;height:240px;" scrolling="no" marginwidth="0" marginheight="0" frameborder="0"></iframe><br /> <a href="http://www.amazon.com/gp/product/0201835959?ie=UTF8&#038;tag=wdr-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0201835959">The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)</a><br /> <img src="http://www.assoc-amazon.com/e/ir?t=wdr-20&#038;l=as2&#038;o=1&#038;a=0201835959" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /><br /></center><br /> &#8220;<em>The</em> classic book on the human elements of software engineering. Software tools and development environments may have changed in the 21 years since the first edition of this book, but the peculiarly nonlinear economies of scale in collaborative work and the nature of individuals and groups has not changed an epsilon. If you write code or depend upon those who do, get this book as soon as possible &#8212; from Amazon.com Books, your library, or anyone else. You (and/or your colleagues) will be forever grateful. Very Highest Recommendation.&#8221;</p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2009/08/the-mythical-man-month/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Try loose coupling in your code</title><link>http://newpush.com/2009/03/try-loose-coupling-in-your-code/</link> <comments>http://newpush.com/2009/03/try-loose-coupling-in-your-code/#comments</comments> <pubDate>Fri, 06 Mar 2009 07:59:42 +0000</pubDate> <dc:creator>Balazs</dc:creator> <category><![CDATA[Technology]]></category> <category><![CDATA[loose coupling]]></category> <category><![CDATA[object oriented design]]></category> <category><![CDATA[software architecture]]></category> <category><![CDATA[software development]]></category><guid isPermaLink="false">http://www.wdream.com/archives/89</guid> <description><![CDATA[Ever ran into the issue of a developer making a change in the code with ripple effects?&#160; Once that happens, you have to institute more comprehensive regression tests throughout the system, hoping to avoid such ripple effects in the future.&#160; &#8230; <a href="http://newpush.com/2009/03/try-loose-coupling-in-your-code/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p>Ever ran into the issue of a developer making a change in the code with ripple effects?&nbsp; Once that happens, you have to institute more comprehensive regression tests throughout the system, hoping to avoid such ripple effects in the future.&nbsp; <a href="http://www.typepad.com/services/trackback/6a01053602891a970c010536f5b3b1970b">The Software Devotional</a> is running a great article about <a href="http://www.thesoftwaredevotional.com/2009/02/loose-coupling-is-good-tight-coupling-is-the-devil.html">loose coupling</a>.&nbsp; This is not the same as encapsulation, and while it might be more expensive on the short run, and an overkill on smallish projects, as soon as the projects get larger, it becomes very painfully obvious that a little bit looser coupling would go a long way in code robustness.&nbsp; My experience certainly validates the assertions <a href="http://www.linkedin.com/in/crawfishmike">Micheal Jones</a> makes in his article.&nbsp; Give it some thought.</p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2009/03/try-loose-coupling-in-your-code/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Served from: newpush.com @ 2012-05-23 05:56:27 by W3 Total Cache -->
