2 ms·
I think that is a really important point. I got dinged[1] on my Intel review for "sand bagging" because I had estimated it would take three months to write an i
by ChuckMcM 11y ago
I think that is a really important point. I got dinged[1] on my Intel review for "sand bagging" because I had estimated it would take three months to write an instruction assembler for a chip I was working on validating, I got it done but my manager claimed I had spent almost all the time "goofing off" and then wrote it in the last couple of weeks. Unlike hardware which had all these great milestones to indicate progress, creating a new program was think, think, think, blammo!
This has always been a challenge for me (and at this point I suspect always will). I don't know exactly how I come up with the stuff I do, it just sort of pops into my head. More rigorous people who can write down a series of milestones and check points are great at giving visibility into the process. My workaround has been to work with good project managers when I can and talk to them about what I know and don't know about a project. The "don't knows" become future deliverables, the "knows" become steps that can be done now and shown as progress.
Looking back on my career I have been the most successful in a group which is a mix of types, call them artists and engineers. There is probably a management book out there somewhere that addresses that question.
[1] Or "constructively criticized" using the Intel vernacular.