3 ms·

The standard advice is that you're the one coming up with the list of tasks required to achieve an agreed upon goal, and concocted features to be added are a ne

The standard advice is that you're the one coming up with the list of tasks required to achieve an agreed upon goal, and concocted features to be added are a new, additional contract. Stick to your list, practice establishing boundaries. If you're just working on whatever their whims bring to the table on any given day and can't control the tasks and outcomes to which you've already agreed, you aren't a contractor, you're an employee without benefits. "Banging out code" is nothing special, yet here they are knocking at your door?

ethbr0 5y ago
In my experience, requirements gathering and obtaining project design consensus is a huge part of the value add from a consultant. (1) You're usually better at it than they are, because they're hiring a consultant in the first place. (2) You're outside of their political network, and can thus be a more neutral, objective arbiter. Invaluable! (3) You're looking at the problem with fresh eyes, whereas they're looking at it with a history of counterparty relationships, failed or successful previous projects, etc. Furthermore, requirements gathering and obtaining project design consensus is going to happen at some point. Better you verify that it happens as fully as possible, as early as possible, versus trusting the client that they've done it accurately and sufficiently.
- rhizome 5y ago
  Exactly. The Handyman's Invoice/$1000 Plumber joke is a positive anecdote from the standpoint of the service provider, but it's usually stated as something like "Step 1: Know your value," which is deceptively simple.
throwaway81523 5y ago
> "Banging out code" is nothing special, yet here they are knocking at your door? They tend to want to pay pretty poorly in this situation.
- rhizome 5y ago
  Perhaps, but my point is that calling what one does in this situation "banging out code" is underselling and unfair to oneself.

ethbr0 5y ago

In my experience, requirements gathering and obtaining project design consensus is a huge part of the value add from a consultant. (1) You're usually better at it than they are, because they're hiring a consultant in the first place. (2) You're outside of their political network, and can thus be a more neutral, objective arbiter. Invaluable! (3) You're looking at the problem with fresh eyes, whereas they're looking at it with a history of counterparty relationships, failed or successful previous projects, etc. Furthermore, requirements gathering and obtaining project design consensus is going to happen at some point. Better you verify that it happens as fully as possible, as early as possible, versus trusting the client that they've done it accurately and sufficiently.

rhizome 5y ago
Exactly. The Handyman's Invoice/$1000 Plumber joke is a positive anecdote from the standpoint of the service provider, but it's usually stated as something like "Step 1: Know your value," which is deceptively simple.

throwaway81523 5y ago

> "Banging out code" is nothing special, yet here they are knocking at your door? They tend to want to pay pretty poorly in this situation.

rhizome 5y ago
Perhaps, but my point is that calling what one does in this situation "banging out code" is underselling and unfair to oneself.