3 ms·
Great list. One I would add would be understanding what the client's problem and building an appropriate solution. Too many times I've seen developers just div
by seanwilson 10y ago
Great list. One I would add would be understanding what the client's problem and building an appropriate solution. Too many times I've seen developers just dive in coding up the solution the client suggested without trying to understand the problem the client is trying to solve. For example, by adapting the problem to using an existing CMS or SAAS you can avoid a huge amount of custom coding.
A good developer would be able to write simple code for a given solution but a better developer would suggest a simpler solution leading to even simpler code.
- Joeri 10y agoThis is exactly the thing that makes a person a "10x" developer. Being able to write lots of reliable code in a short amount of time is a good trait, but knowing when not to write code is equally important.
- elliotchance 10y agoFor me this falls in to the "understanding" category. The problem your trying to solve and what the client wants are often mixed up as the same thing - but they seldom are. You shouldn't expect that the client will know what they want even if they ask for it. There is however always an underlying reason why they think they need it. Take the time to understand that rather than just more billable hours. It will be better for you and them in the long run.