Best practices? Or bestest practices?



Email    print   
August 15, 2008 —  (Page 1 of 7)
The very best practice in software development may well be to embrace the understanding that there is no single “best” way. Everyone does their best a little differently: reducing pages of hand-written notes to a few equations, the implementation of which is trivial; writing a program on the couch while a football game plays in the background; rolling out new features month after month; or participating in an enterprise-wide rollout that takes 18 months to plan and deliver. All of these might be one's "best" experience, but all of them are developed in very different ways. So, let's narrow things down a bit.

Corporate development is that of software built for commercial purposes, but not for direct resale. It may generate value directly, as in a Web storefront, or indirectly, as in supply chain coordination, but at its core it is in service to the company's bottom line. Corporate development embodies significant domain knowledge and business rules; this creates a characteristic combination of logic that's "so obvious, no one's ever stated it" and, likewise, it’s "not understood but has to be implemented to stay competitive."

There's typically a Web component to such software, but 100% compatibility with all the world's browsers and OSes is not usually a concern; a requirement to use IE or even a beta version of Silverlight may well be acceptable if it delivers high value.

Speed of development is the final sticking point for corporate development. All corporate development teams have a backlog. Even—maybe especially—in companies that don't consider themselves in the business of software development, time to develop and time to deploy are often the two factors that control the rate at which the company can seize new opportunities. So there is always a premium on high productivity in corporate development.

But in opposition to high productivity is risk: risk of major delay, risk of a show-stopping technical incompatibility, or risk of embracing a tool or technique that is reaching the end of its evolution. Such risks can have huge costs, and it’s very reasonable for project managers to make conservative decisions, especially when it comes to critical infrastructure components. (Prototypes, one-off conversion programs and administration automation are, in contrast, places where there is less risk in exploring newer technologies and techniques.)



Related Search Term(s): Flash, .NET, Silverlight, software development, Visual Studio, Adobe, Microsoft

Pages 1 2 3 4 5 6 7 


Share this link: http://sdt.bz/32678
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Third-party tools showcased at Professional Developers Conference
ComponentOne has a new development kit for the iPhone and the iPod Touch, while Infragistics created a version of NetAdvantage for Silverlight. Also, Developer Express and Microsoft announced a joint code-quality effort for C# Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb