(about estimating - I don't tend to write proposals) You could have a look at https://www.estigator.com
(NB it's a half-finished side project right now)
I'm no longer a contractor, although I have been, and I'm frequently asked by my new employers to provide estimates for dev tasks.
Trouble is, businesses/clients tend to see an estimate as a promise, or a target. From the developer's point of view it is hard to do anything other than guessing (at smaller and smaller granularities). Book recommendation: "The Clean Coder" by Robert C. Martin - esp. Chapter 10)
I started building https://www.estigator.com to see if I could learn React, and come up with something to help me illustrate just exactly who's taking a risk when we say something like "it'll probably take about 3.5 days"
I wasn't quite ready to "Show HN" with this one, but your question made me think of it straight away. Would love to know what people think
(NB it's a half-finished side project right now)
I'm no longer a contractor, although I have been, and I'm frequently asked by my new employers to provide estimates for dev tasks.
Trouble is, businesses/clients tend to see an estimate as a promise, or a target. From the developer's point of view it is hard to do anything other than guessing (at smaller and smaller granularities). Book recommendation: "The Clean Coder" by Robert C. Martin - esp. Chapter 10)
I started building https://www.estigator.com to see if I could learn React, and come up with something to help me illustrate just exactly who's taking a risk when we say something like "it'll probably take about 3.5 days"
I wasn't quite ready to "Show HN" with this one, but your question made me think of it straight away. Would love to know what people think