V2
Do you think you can finish a new REST API with 3 simple CRUD endpoints in ONE day? That simple question gets asked many times in your life and it can be a trap, your brain will try to calculate how productive you can be in a single day, what your experiences are with API's and what risks you see. But you are blinded by the fact that the initial task mentions "one day" and you often forget to account for the risks you don't see and you end up giving a really bad estimation! Does it sound familiar? Situations like that show the effects of cognitive bias.
This talk gives an overview of these biases and also exemplifies some of those situations which the goal being to be able to control (or at least be conscious about it) it better in the future!
V1
The Creative Developer is a talk which tries to explore the influences we receive every time while trying to be problem solver, creative and productive all at once during our frequent challenges. The cognitive biases are by themselves in a role which has the power to control all those factors, thus I ask, are they the enemies?
Let's try together to explore a few of them and see how we can cooperate to achieve more!
More information:
Slides: http://talks.mefi.in/the-creative-developer
JoindIn: https://joind.in/user/renatomefidf
This abstract is vague. I'm not sure what this is about. Is it about a developer's bias towards a particular task? How different developers experience or approach a given problem? I think a bulleted list of situations where bias affects the creative process is a good idea. Or something similar. Be more explicit as to what you're talking about. Remember your abstract needs to convey to people what they'll get out of it.