In episode 29 of Does Not Compute, Sean and Paul talk about the importance of introspection and project postmortems as a tool for learning, as well as lay out a few tips for dealing with client questions that require you to research before answering
Special thanks to Digital Ocean for sponsoring this week's episode!
Head on over to http://digitalocean.com/doesnotcompute and you'll get a 1gb droplet for free for an entire month. Again, that's a free ssd backed server with a dozen one click installs available for free.
I'd like to know how developers can better provide input into a job spec/set expectations. When a client says "We need x, y and z" is there a way to say "yes, no or maybe" without spending an hour diving into docs or building a prototype. - @kidqueb
Paul: first off, if doing that is part of your job, you should absolutely have the time to spend as much time as needed figuring out actual requirements and deliverables. Too much pressure on people in this way would make me look at company culture problems, not at individual devs.
If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute Show Notes repo and use GitHub's excellent search tool!
If you've enjoyed the show so far, reach out to us on twitter at @seanwashington and @paulstraw, or join us in the Spec.fm slack community at http://spec.fm/slack!
Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here!