3 ms·
It turns out that software development is a very immature industry. We simply don't know how to judge successful software projects/developers. In the face of
by kasey_junk 11y ago
It turns out that software development is a very immature industry. We simply don't know how to judge successful software projects/developers.
In the face of that immaturity we can try all kinds of things. Personally, I do anarchist development and hope for the best. Others try cargo cult project management. Still others move to highly constrained development methodologies.
- gearoidoc 11y agoI think its easy to judge if a software project was successful (eg. Did we launch? Did we deploy that feature?). The harder question I suppose is whether it was successful and we've got/maintained a quality codebase.
- kasey_junk 11y agoBut compared to what? Most software continues to be bespoke/new work. If a different team/process was used would we have been as successful/spent as much money.
- majewsky 11y agoThis touches on the classic question of "is coding engineering or art"? If it were engineering, it would become quantifiable once we have enough empirical data from previous projects to base our theories on. If it were art, that would be impossible since every project is as individual as the last one. It's probably inbetween.
- bb88 11y agoEngineering is just applied science. And other engineering fields experience the same types of failure that software engineering experiences -- cost overruns, undefined requirements, unseen technical hurdles, etc.
- partycoder 11y agothat's the same by saying your kids are successful just because they were born.
- gearoidoc 11y ago"just because they were born" Thats an example of a successful pregnancy project.
- partycoder 11y agoSuccessful software is software that implements its functional and non-functional requirements at a reasonable cost. There.
- kasey_junk 11y agoYet interesting enough, that definition doesn't mention any of the actual reasons why you'd build software and doesn't speak to end-user/customer/client happiness. It also implies at least, that we can collect requirements in some adequate way, which is really a circular argument. Requirements gathering is even less mature than other parts of software development.
- partycoder 11y ago"why you build software" = requirement. end-user/customer/client happiness = Customer satisfaction surveys and ratings help you acquiring it. Basic KPIs such as retention rates and engagement can also help you understand this. A/B testing helps the process of testing assumptions in a data driven way.
- kasey_junk 11y agoThat is a definition of requirement that is different than what most of the industry uses. Most of the industry sees requirements as "how the software should behave". Even with your new definition, I've seen little evidence that we have mature processes around collecting requirements. As for surveys, KPIs, A/B testing etc. Those are neither standardized, proven to be valuable in a rigorous way, nor widely used. All signs of an immature industry. Further, they can only be used in software development processes that allow for iterative deployment.