Menu
Forums
New posts
Search forums
What's new
New posts
Latest activity
Log in
Register
What's new
Search
Search
Search titles and first posts only
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Help Support The Rugby Forum :
Forums
Other Stuff
The Clubhouse Bar
The technology thread
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="ncurd" data-source="post: 1106780" data-attributes="member: 72205"><p>There is some philsophy talk recently about where the code itself is documentation the only thing you need to produce extensive documentation for is external interfaces and how they work. I see some merit in that I've extensively designed stuff as a starting point in the past and that's a great starting block but reality is that design has had to be modified a huge amount when reality hit it, in the embedded world sometimes chips don't work how you read them to and scope creep is always a thing. Getting access to code with documented external interfaces always helps way more than any design document.</p><p></p><p>Plus the cost of updating documentation is probably not a huge differential to the the onboarding process.</p><p></p><p>To paraphase David Fincher "Software isn't finished its abandoned"</p></blockquote><p></p>
[QUOTE="ncurd, post: 1106780, member: 72205"] There is some philsophy talk recently about where the code itself is documentation the only thing you need to produce extensive documentation for is external interfaces and how they work. I see some merit in that I've extensively designed stuff as a starting point in the past and that's a great starting block but reality is that design has had to be modified a huge amount when reality hit it, in the embedded world sometimes chips don't work how you read them to and scope creep is always a thing. Getting access to code with documented external interfaces always helps way more than any design document. Plus the cost of updating documentation is probably not a huge differential to the the onboarding process. To paraphase David Fincher "Software isn't finished its abandoned" [/QUOTE]
Verification
Post reply
Forums
Other Stuff
The Clubhouse Bar
The technology thread
Top