Design Document

hec031
Jun 19
1 min read

So as the research progresses on the new SFE thruster design, it has become completely necessary to create a design document. The new system is far more complex and advanced than anything I have done before.

The design document is not only to keep track of what I'm going to do, but also it acts like a test log. I don't know about the rest of you, but if I walk away from a project for too long and come back, I find myself questioning what I did and why.

So this design document will help track not only what I did but why I did it. This is the way I would program. I got used to writing lots of notes, not so much for others but for me.

Just my thought of the day.

2 commentaires

simon.derricutt

20 juin

Hector - Though the full design write-up may help in getting ducks in a row and seeing which are missing, I find that explaining it to someone else generally finds the missing ducks very well. I've also found that each time I write out a new explanation, it not only (generally) gets a bit clearer for others to understand but I also catch a few more errors and find a few more ducks. You'll likely have made some decisions based on hunches, and at some point in re-explaining how and why things work you'll probably suddenly get a reason for those hunches and either fix them as the way forward or re-formulate them to get a better result because you…

hec031

20 juin

En réponse à

Simon, I agree that writing things out or trying to explain things to others tends to give insight and clarity to one's own work. I look back at my own notes from 10 years ago and remember what I was thinking and what I was clueless about. 😂 It took me 6 years to figure out the source of a major problem with the technology. So, keeping notes on what you are thinking at any one moment in time tends to help further down the line. Thanks for the comment.