While I agree the bus-number is an important factor. Most products, programs, languages, platforms early on were developed by 1-3 programmers, maybe closer to one.
Also, the bus number is usually only applied to programmers whereas product managers, executives, etc all dont' have the same bus number over their head. It is almost like companies hate the fact they have a valuable technologist or programmer and try to consistently offset that.
Now of course if the single programmer is not communicating or after the project is done they play complexity games then that is different (only one person can read their code) but usually I see the 1-2 man teams obliterate the 3-7 person teams on a regular basis.
Programming is not construction, the number of programmers on a project has little to do with success ever. So the bus-number is quite silly. What about the bus-number for the CEO, or the project manager, or the one person that handles billing etc.
Also, the bus number is usually only applied to programmers whereas product managers, executives, etc all dont' have the same bus number over their head. It is almost like companies hate the fact they have a valuable technologist or programmer and try to consistently offset that.
Now of course if the single programmer is not communicating or after the project is done they play complexity games then that is different (only one person can read their code) but usually I see the 1-2 man teams obliterate the 3-7 person teams on a regular basis.
Programming is not construction, the number of programmers on a project has little to do with success ever. So the bus-number is quite silly. What about the bus-number for the CEO, or the project manager, or the one person that handles billing etc.