3 ms·
The condition that enables true solo programming (one developer putting out the entire product) is having a piece of software whose complexity is manageable by
by greenyoda 10y ago
The condition that enables true solo programming (one developer putting out the entire product) is having a piece of software whose complexity is manageable by one person. Most significant software today is larger than that, although something like a small, stand-alone application (iPhone game or PC utility) might still fall into that category.
For commercial software, another constraint is time: a solo developer might be able to create some software in two years, but the product is needed in six months. So the work gets split up.
There are also risk management issues. If there's only one person working on a piece of software, the project takes a big hit if that person leaves or suffers a debilitating accident (there's a "bus factor"[1] of 1).
And there are quality issues: if only one person understands the code they're writing, who's going to review the code to make sure there are no serious bugs or security holes?
I still work pretty much as a solo programmer, but within a large organization. I work on an important component of a large software product, and I'm the only developer who works on (or even understands) that area of the code. I do, however, interact a lot with other groups whose code interacts with mine.
[1] https://en.wikipedia.org/wiki/Bus_factor https://en.wikipedia.org/wiki/Bus_factor
- dasmoth 10y ago>>> I still work pretty much as a solo programmer, but within a large organization. I work on an important component of a large software product, and I'm the only developer who works on (or even understands) that area of the code. I do, however, interact a lot with other groups whose code interacts with mine. Do you hear the "bus factor" and/or lack-of-code review concerns much? If so, how do you respond?
- greenyoda 10y agoNobody has ever brought it up. Regarding code reviews: I try to test and self-review my code thoroughly, and hope that the QA people find the bugs that I don't find. My bug rate seems to be comparable to other parts of the product that are worked on by multiple developers. As for bus factor: if they insist on adding more people to the project, I could deal with that, but it wouldn't make me particularly happy to manage people (I've done it before, but I prefer just being a developer).