Re:What Everybody Should Know About Contracting Developers
by auctiontheory on Wednesday May 15, 2013 @02:50PM
(#5713963)
Why does anyone expect a specific answer to a non-specific question?
The more you can learn to help the client work through ambiguity, rather than expect the client to match your technical understanding and then be frustrated when they don't, the more successful you will be.
Re:What Everybody Should Know About Contracting Developers
by robmclarty on Wednesday May 15, 2013 @04:46PM
(#5714755)
Granted, that goes with the territory of being in the service business. My gripe is that clients expect to pay for "just the coding" rather than the entire process of discovery, consultation, and strategy + coding.
Re:What Everybody Should Know About Contracting Developers
by marknow on Wednesday May 15, 2013 @06:09PM
(#5715329)
"The more you can learn to help the client work through ambiguity..."
This assistance implies expertise beyond just being a code monkey; higher-level thinking and problem-solving should definitely come at a higher price.
Re:What Everybody Should Know About Contracting Developers
by beat on Wednesday May 15, 2013 @03:06PM
(#5714045)
Ultimately, software is about getting specific answers to non-specific questions.
Re:What Everybody Should Know About Contracting Developers
by ptaipale on Thursday May 16, 2013 @01:18AM
(#5717051)
Absolutely, but that's more than just coding.
Re:What Everybody Should Know About Contracting Developers
by trevmckendrick on Wednesday May 15, 2013 @02:16PM
(#5713750)
"Developers are one step away from computers (literally) and require a lot of the same rigour when interacting with them."
Great point. Most people are not used to the level of specificity required to be a developer.
This usually turns into multiple back-and-forths to flesh out what the client really needs, and usually requires a lot of thinking on the developer's part (me) to nail down an actionable solution that could potentially be estimated in terms of $$$.
I was hesitant reading Trevor's article thinking what he was suggesting was devaluing dev work, but when he emphasized the importance of specificity I was on board with him. If a client has fully thought out their idea to the point of step by step mockups, that takes a LOT of the pain, frustration, and effort out of the equation which translates to the required work not costing as much.
Developers are one step away from computers (literally) and require a lot of the same rigour when interacting with them. Know what you want and be able to explain what you want (in detail) before engaging them ;)