|
|
|
|
|
by InclinedPlane
4877 days ago
|
|
Oh, it's plenty different. First off, software is not one thing. It encompasses more orders of magnitude of difference than almost any other industry. At one end you might have throwaway fart apps or single serving joke websites and at the other end you might have spacecraft avionics or industrial systems control or banking systems, and in the middle there is a multi-dimensional realm of tremendous breadth and volume. Additionally, software construction is by its nature creative. Creating a million or a billion or even a trillion copies of a piece of software is a more or less trivial and heavily automated task. Software isn't like making cars or houses or bridges. When you make a bridge there is a lot of work that goes into design but most of the work is in implementation. In software the implementation (the actual running of the software) is automated, all of the development work and all of the so-called "implementation" work is in truth just design work on finer and finer scales. The combination of all of these factors makes software a different sort of beast than a lot of other work. Now, as I said, that doesn't mean that you can't still attack it with brute force and obtain results, but software is actually one of the realms where that is one of the least effective strategies. |
|
Your statement about design vs implementation shows that you're clearly outside of your knowledge space when talking about other disciplines. Depending on bridge span, length, and construction method, the man hours required for design can be much more than those required for construction.
Software is not really all that different from any other type of work. It even shares the trait that people that are part of the software sector think that their sector is somehow inherently different.