3 ms·
I think the author has a point, as software development is lot different than most other contracting gigs. In most successful contracting jobs one would have a
by achow 11y ago
I think the author has a point, as software development is lot different than most other contracting gigs.
In most successful contracting jobs one would have a very clearly defined scope (processes and materials to be used, what is a clear outcome, etc.).
Software development has lot of ambiguity - processes to be followed, materials (technology stacks) to be used, what is a clear outcome (nobody knows unless it is validated in the field - apart from internal testing scenarios).
- raverbashing 11y agoExactly Most of the time, the people going for upwork have no idea of what they want, they just want 'an iPhone app'
- spdionis 11y agoBut don't forget that there are also good clients. Honestly it's not that hard to tell this kind of clients from the good kind.
- Kurtz79 11y agoIt is in the interest of the customer to define and specify what it wants as much as possible. In more formal environments it is normal to have a requirements specification as a point of entry for developing the SW, and the first output by the contractor should be not code, but technical documents describing how this requirements are going to be met, how they are going to be tested, the technology used... Of course this is a process that require additional effort and time, not only on part of the contractors but from the customer as well (in terms of requirement definition and review). What I'm saying is that there are well known processes and methodologies to deliver SW products, and it's up to the customer to define what it wants, and to what detail, and up to the contractor making sure that he has a clear idea of what he is going to get.