Skip to content
Snippets Groups Projects
Commit af447ede authored by Henk Buursen's avatar Henk Buursen
Browse files

cleaned a fixed 1st slides

parent 14c4a82c
No related branches found
No related tags found
No related merge requests found
Pipeline #439157 passed
Stage: deploy
    Hide whitespace changes
    Inline Side-by-side
    recitation/debugging/debugging.html
    + 87
    − 60
    View file @ af447ede
    ......@@ -68,86 +68,110 @@
    <img class="r-frame" style="height: 620px; margin: 0 auto 4rem auto; background: transparent;" data-src="./img/hhg_question.png" alt="Attitude">
    </a>
    <aside class="notes">
    <aside class="notes">
    <p>The answer never is: "it doesnt work!" In case of a just
    designed and produced circuitboard, break the "problem into pieces".</p> </section>
    designed and produced circuitboard, break the "problem into pieces".</p>
    - is the board powered?
    - after producing the pcb you did a visual check. Do it again!
    - are the components soldered correctly?
    - are the components the right ones?
    - are the components placed correctly?
    </aside>
    <section>
    <h2>Don't jump to conclusions</h2>
    <p><img class="r-frame" style="height: 90%; margin: 0 auto 4rem auto; fig-align: right; background: transparent;" data-src="./img/jump.jpg"></p>
    </section>
    <section>
    <p class="fragment fade-in-then-out">Approach the problem objectively</p>
    <p class="fragment fade-in-then-out">Everyone (everything) is a suspect!</p>
    <p><img class="r-frame" style="height: 90%; margin: 0 auto 4rem auto; fig-align: right; background: transparent;" data-src="./img/jump.jpg"></p>
    <h2>Don't jump to conclusions</h2>
    <aside class="notes">
    <p>Don't jump to conclusions. It's easy to assume that the
    problem is in the most complex part of the system. Or even
    worse: blaming the manifacturer of the components for faulty
    or misbehaving components. But it's often in the simplest
    part of the system. Maybe it's a mistake you made. You actually
    designed, milled, stuffed and programmed the circuit. </p>
    <p>Time pressure can be a factor in jumping to fast conclusions.
    But it's better to stay calm and think of a step by step
    approach.</p>
    </aside>
    </section>
    <section>
    <video class="r-frame" style="height: 620px; margin: 0 auto 4rem auto; background: transparent;" data-src="./img/Debugging_strategy.mp4" controls></video>
    <aside class="notes"> Fixing a bug that is not, leads to a
    new bug, that is not a bug. And you don't want to end up in
    a situation where you trashed the whole project because of a
    "bug" that wasn't a bug from the beginning. </aside>
    </section>
    <section>
    <h2>Write down what you do</h2>
    </section>
    <section>
    <p><img class="r-frame" style="height: 340px; margin: 0 auto 4rem auto; background: transparent;" data-src="./img/memory.jpg"></p>
    <aside class="notes">Debugging is difficult, and it's easy to forget what you've done. Writing down what you've done can help you remember what you've tried and what you haven't tried.
    It often also helps you to write down what you think the problem is. This can help you to think more clearly about the problem and the solution.
    And last but not least: Often you break something while trying to fix something else. Writing down what you did can help you to undo what you did.
    </section>
    <section>
    <img class="r-frame" style="background: rgba(255,255,255,0.1);" data-src="./img/ThePragmaticProgrammer.jpeg">
    </section>
    <section>
    <h2>Talk to me</h2>
    <aside class="notes">Debugging is difficult, and it's easy
    to forget what you've done. Writing down what you've done
    can help you remember what you've tried and what you haven't
    tried. It often also helps you to write down what you think
    the problem is. This can help you to think more clearly
    about the problem and the solution.
    And last but not least: Often you break something while
    trying to fix something else. Writing down what you did
    can help you to undo what you did.
    </aside>
    <h2>Write down what you do</h2>
    </section>
    <section>
    <img class="r-frame" style="background: rgba(255,255,255,0.1);" data-src="./img/ThePragmaticProgrammer.jpeg">
    <aside class="notes">
    <p>A good read is "The Pragmatic Programmer", a
    collection of tips to improve the development process in
    a pragmatic way.</p>
    </section>
    <section>
    <img class="r-frame" style="height: 440px; background: rgba(255,255,255,0.1);" data-src="./img/duck.webp">
    <h2>Talk to me</h2>
    <aside class="notes">
    In software engineering, rubber duck debugging (or rubberducking) is a method of debugging code by articulating a problem in spoken or written natural language.
    Carry around a rubber duck and debug what you did by forcing yourself to explain what you did, step by step, to the duck. You can also use a instructor, fabacademy
    student or friend, but the duck won't judge you.
    </note>
    In software engineering, rubber duck debugging (or
    rubberducking) is a method of debugging code by articulating
    a problem in spoken or written natural language. Carry
    around a rubber duck and debug what you did by forcing
    yourself to explain what you did, step by step, to the duck.
    You can also use your instructor, fabacademy
    student or friend. Advantage of the duck is that it won't judge you.
    </aside>
    </section>
    </section>
    <section data-visibility="hidden">
    <h2>Hidden Slides</h2>
    <p>
    This slide is visible in the source, but hidden when the presentation is viewed. You can show all hidden slides by setting the `showHiddenSlides` config option to `true`.
    </p>
    </section>
    <section>
    <section>
    <img class="r-frame" style="margin: 0 auto 4rem auto; background: transparent;" data-src="./img/dontpanic.jpg">
    </section>
    <section>
    <video class="r-frame" style="height: 620px; margin: 0 auto 4rem auto; background: transparent;" data-src="./img/Debugging_strategy.mp4" controls></video>
    </section>
    <section>
    <h2>Narrowing down the problem</h2>
    </section>
    <section data-auto-animate>
    <section>
    <h2>Narrowing down the problem</h2>
    </section>
    <section data-auto-animate>
    <ul>
    <li>Reproduce the problem</li>
    </ul>
    </section>
    <section data-auto-animate>
    <ul>
    <li>Reproduce the problem</li>
    <li>Always first do visual check</li>
    </ul>
    </section>
    <section data-auto-animate>
    <ul>
    <li>Reproduce the problem</li>
    </ul>
    <li>Always first do visual check</li>
    <ol>traces</ol>
    <ol>soldering</ol>
    <ol>components</ol></li>
    </ul>
    </section>
    <section data-auto-animate>
    <ul>
    <li>Reproduce the problem</li>
    <li>Always first do visual check</li>
    </ul>
    </section>
    <section data-auto-animate>
    <ul>
    <li>Reproduce the problem</li>
    <li>Always first do visual check</li>
    <ol>traces</ol>
    <ol>soldering</ol>
    <ol>components</ol></li>
    </ul>
    </section>
    <section data-auto-animate>
    <ul>
    <li>Reproduce the problem</li>
    ......@@ -156,16 +180,19 @@
    <ol>soldering</ol>
    <ol>components</ol></li>
    <li>Keep in mind that the problem might not be visible without a microscope</li>
    </ul>
    </ul>
    </section>
    <section>
    <img src="img/visual.jpg" height="600">
    </section>
    <section>
    <img src="img/visual.jpg" height="600">
    </section>
    </section>
    </section>
    ......
    0% or .
    You are about to add 0 people to the discussion. Proceed with caution.
    Finish editing this message first!
    Please register or to comment