Design & Code
Articles
|
Feature Injection: Part One We are leaving the "last responsible moment" for a while. This month we start a discussion of Feature Injection, an analysis process based on real options and Kolb's circle of learning. The first episode ( of five ) introduces the "Information Arrival Processes. |
||
|
What Software Developers Can Learn from Their Cafeteria Did you know that Starbucks sells a cup size called "short"? It's a small cup that is less expensive than the other cup sizes. They never mention it on their menu; you have to know it exists before you can order one. Why? By having a smaller, cheaper option, they give their budget-conscious customers an opportunity to pay for coffee rather than go without. This kind of thinking has important repercussions to software developers. |
||
|
Refactoring Doesn’t Mean Rewrite Peter Schuh writes that it is not a good thing that the use of the term refactoring has grown so common, which makes him cringe every time he hears a business person say the word. Refactoring is meant to be one skill of many that is second-nature to a journeyman programmer. |
Peter Schuh
March 9, 2009 |
|
|
Configuring CruiseControl for Continuous Integration Builds Michael Sayko introduces CruiseControl, which enables the implementing CI of Java applications. Using CruiseControl's build loop, dashboard, and build resultsJSP, Michael shows how any Java development team can receive added value through this open source tool. |
Michael Sayko
January 4, 2009 |
|
 |
How Early Interface Analysis Reduces Risk Analyzing a project's interface requirements often starts late and focuses--sometimes exclusively—on creating a snazzy user interface. But failing to conduct interface analysis in a early increases the risk of project delays, overruns, and even failure. In this column, Mary Gorman makes the case for investing in interface analysis by explaining what it is and how it reduces the risk in software projects. |
|
|
Why You Need to Be Specific about Agile Practice Adoption Amr Elssamadisy presents one way to share our knowledge that is more specific than full methodologies and processes, more general than war stories, and will help new agile adopters get beyond the mantra "It depends!" |
||
|
Tool Integration In Distributed Agile Development This article provides an overview of various tools, integration strategies and their benefits in agile environments. These tools would come in handy in implementing key agile practices like daily builds, refactoring, continuous integration and test driven development. |
||
|
Using Mocks to Verify Interactions In the March 2006 issue of Better Software magazine, Dan North began a discussion of the evolution of behavior-driven development from test-driven development. Here, North continues the conversation with closer look at "mocks," utility classes that, for testing purposes, pretend to be some component or service with which your object will interact. |
||
|
Agile Processes: Making Metrics Simple IT organizations and, in particular, application development departments, are increasingly under pressure to provide performance and compliance metrics to justify annual spend. Unfortunately, many metrics campaigns collapse under their own weight. |
||
|
Structure Marking Structure marking is a programming technique that defends data against damage, especially from software bugs. It adds flags to data structures and checks them at each use to detect damaged data immediately. |
Tom Van Vleck
August 5, 2005 |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.