Always Multiply Your Estimates by π (2013)
This reminds me of my game development job I had years back.<p>I was new to the field (but not new to software development) and there was this small software team doing programming tasks for the game.
The lead developer was concerned on my performance after a few months I was there.<p>I remember him drawing an image excatcly like the second picture in this article (an arrow going from A to B). He said that my performance was very poor, and then he drew another picture that was like the circle in the article.<p>The way I worked was searching for a solution, going wrong direction a few times, asking designers for more information and then eventually landing on a solution (that worked, and users like it).<p>But I was told this is wrong way of doing software. I was not supposed to ask advice from the users (because the team "knew better").<p>He also told me that a good software developer takes a task, solves it (goes from A to B), and then takes another task.<p>After a few weeks I was fired from that job.<p>To this day I'm still baffled by this. The company was really succesfull and everyone knew how to make software. It seemed like a very harsh environment. Is it like this in the top software companies everywhere? Like the super-pro-developers really just take a task and solve it without issues?