A Team Should Build the Most Impactful Parts of Its Software

3 min read

Publicly available solutions are ubiquitous. These products can fill a team’s need so well that it is tempted to build its software from a mélange of packages sown together.  A mishmash of libraries is an appealing approach. Yet, a unit is better off avoiding that method. Instead of the Frankenstein technique, a group should build the most impactful parts of its software to gain otherwise unattainable knowledge. When a team builds a consequential piece of its software, the unit acquires knowledge, which can be used to make well-informed estimations.  A squad makes enlightened guesses when it has the expertise acquired…...

This article is free to read

Login to read the full article


OR

By subscribing to our main site, you will also be subscribed to DDIntel - our regular letter showcasing our featured articles and applications.

Collin Rusk Since the mid-2000’s, Collin Rusk has worked on a variety of projects, using his interest and expertise in software engineering to develop and/or architect enterprise systems. Business products have unique challenges. Enterprise systems are often complex, and they typically have to be supported for a period of at least a decade. Long support-durations and complexity make shortfalls in software engineering particularly harmful. Those deficiencies can cost an organization hundreds of truckloads of cash. Inadequacies on multiple products allow those amounts to accumulate to destructive levels, an event that Collin has witnessed multiple times. Those events, and his own mistakes, have spurred his interest in software engineering (a distinct concept from programming). Collin has used that interest, and the knowledge gained from it, to move the enterprise systems that he builds in a less destructive direction. Collin has been architecting enterprise software since 2010. He has a B.S. in Management Information Systems from Le Moyne College and an M.S. in Computer Science from Lawrence Technological University. Collin is interested in a variety of subjects. Using those areas, he attempts to augment his software engineering knowledge.