<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Guest Blog on Sigasi</title><link>https://www.sigasi.com/tags/guest-blog/</link><description>Recent content in Guest Blog on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 27 Nov 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/guest-blog/index.xml" rel="self" type="application/rss+xml"/><item><title>How much time is spent on writing documentation versus developing RTL code?</title><link>https://www.sigasi.com/tech/how-much-time-spent-writing-documentation-versus-developing-rtl-code/</link><pubDate>Wed, 27 Nov 2013 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/how-much-time-spent-writing-documentation-versus-developing-rtl-code/</guid><description>&lt;h2 
 class="uk-heading-large" 
 id="estimation-of-time-for-technical-documentation-and-software-development"&gt;
 &lt;a
 href="https://www.sigasi.com/tech/how-much-time-spent-writing-documentation-versus-developing-rtl-code/#estimation-of-time-for-technical-documentation-and-software-development"
 class="uk-link-reset"
 aria-label="Link to this section: Estimation of time for technical documentation and software development"&gt;
 Estimation of time for technical documentation and software development
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Estimating software development schedules is a skill. The programmer who is going to do the work can figure out what steps they will need to take to implement that feature. And only the programmer can estimate how long each one will take. The nature of software development is that things which seem simple are often surprisingly complicated when we think about all the details. Attempting to estimate a feature before we&amp;rsquo;ve figured out how the feature is going to work, in detail, can&amp;rsquo;t possibly work, even if we multiply our best guess by three, because our &amp;ldquo;best guess&amp;rdquo; is based on very little in the way of facts.
One of the most painful questions that developers are faced with is estimation and justification of time required for technical documentation development. Documentation developers need a methodology to provide a more or less precise and, most importantly, well-grounded estimation of documentation development time, already at the problem definition stage.&lt;/p&gt;</description></item><item><title>Why you need good documentation for your VHDL and Verilog code</title><link>https://www.sigasi.com/tech/why-you-need-good-documentation-your-vhdl-and-verilog-code/</link><pubDate>Sun, 10 Nov 2013 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/why-you-need-good-documentation-your-vhdl-and-verilog-code/</guid><description>&lt;p&gt;&lt;em&gt;In this blog series, guest blogger Smrita talks about the need for
documentation for complex RTL designs.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In engineering, &lt;a
 style="white-space: nowrap;"
 href="https://en.wikipedia.org/wiki/Technical_documentation"
 
 target="_blank"
 
 &gt;technical documentation&amp;nbsp;&lt;span uk-icon="icon: sign-out; ratio: 0.7"&gt;&lt;/span&gt;&lt;/a&gt;
refers to any type of documentation that describes handling,
functionality and architecture of a technical product or a product under
development or use. The intended recipient for product technical
documentation is both the (proficient) end user as well as the
administrator, service or maintenance technician. In contrast to a mere
&amp;ldquo;cookbook&amp;rdquo; manual, technical documentation aims at providing enough
information for a user to understand inner and outer dependencies of the
product at hand. The technical documentation is intended to help the
maintainers of the system (the people who need to keep the system
running smoothly, fix problems, etc.) The maintainers are usually
technical people, who need to know &lt;a
 style="white-space: nowrap;"
 href="https://www.igcseict.info/theory/8/docs/index.html"
 
 target="_blank"
 
 &gt;exactly how the system
works&amp;nbsp;&lt;span uk-icon="icon: sign-out; ratio: 0.7"&gt;&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>