code programming

Debugging: Finding It Yourself

The half of programming nobody teaches. You take one working program, break it nine ways, and find every fault by elimination rather than by staring at it. Ends with the kind of bug that raises no error at all.

  • trending_upBeginner
  • schedule5h 21m
  • menu_book9個のレッスン
  • publicEnglish
  • workspace_premiumBasic
Debugging: Finding It Yourself

ブリーフィング

Every beginner course stops at "and now it works". Then the learner goes home, changes one line, and has no method for what happens next. This segment is the method. One small program — a bill splitter, about twenty lines — gets broken repeatedly and you get it back. You will read a traceback properly instead of scrolling past it. You will cut a file in half with `exit()` and cut it in half again until two lines are left. You will comment out everything except one function and drive it directly. You will print a value raw, then stripped, then lowered, so you can see the transformation instead of reasoning about it. Then the gauntlet: missing colon, wrong quote characters, stray whitespace, indentation, `=` where you wanted `==`, a result you never stored, two functions with the same name, an input asked for twice, a `TypeError` on text that was never converted, and text glued together where you meant to add numbers. Six of those tell you something is wrong. The rest do not say a word, and those are the ones that reach other people.

コースアウトライン · 3個のモジュール

lockアクセスで解放
  1. 01 Reading What It Already Told You
    3個のレッスン·1h 9m

    A traceback is read from the bottom. The last line is a sentence. The line number above it is where Python gave up, which is not always where you went wrong. Read it, then act. Guessing before…

  2. 02 Elimination, Not Inspiration
    3個のレッスン·1h 37m

    Real troubleshooting is elimination. You do not find the fault by thinking harder about the whole file; you find it by making the file smaller until there is nowhere left for it to hide.

  3. 03 The Gauntlet
    3個のレッスン·2h 35m

    One fix, one run. A file with four changes in it and a fresh error tells you nothing about which change caused what.

よくある質問

Debugging: Finding It Yourselfでは何を学べますか?
The half of programming nobody teaches. You take one working program, break it nine ways, and find every fault by elimination rather than by staring at it. Ends with the kind of bug that raises no error at all.
事前の経験が必要ですか?
いいえ — Debugging: Finding It Yourselfは基礎から始まり、初心者に適しています。
Debugging: Finding It Yourselfはどのくらいの時間がかかりますか?
Debugging: Finding It Yourselfには3個のモジュールと9個のレッスンが含まれています。自分のペースで学習できます。
アクセスするにはどうすればよいですか?
Debugging: Finding It Yourselfは任意の有料サブスクリプションに含まれています。

プログラミングのその他

Binary, Hex and Data Units
Beginner Binary, Hex and Data Units The topic that costs more marks than any other on the paper, taught by hand. Bits and bytes, binary and hex in all six directions, the 1000-versus-1024 trap, file sizes, transmission times, overflow, two's complement and character sets. Every module ends in a timed drill marked the way an examiner marks it.
First Program — Scratch for ages 5–9
Beginner First Program — Scratch for ages 5–9 Nine Scratch blocks, three sessions of about twenty-five minutes, and one small program a child of five to nine builds themselves. Written for the parent sitting beside them: what to click, what they will get stuck on, what to say when it goes wrong, and when to keep your hands off the mouse.
ハイプなしのAI
Beginner ハイプなしのAI モデルが回答するとき実際に何をしているのか、なぜそれが思考のように見えるものを生み出すのか、なぜ引用を作り出すのか、そしてほぼ誰も説明しないコストの仕組み:チャットは毎回会話全体を再送信します。計算は自分でやります。
Python From a White Sheet
Beginner Python From a White Sheet 9人の学生がすでに歩んだ正確な道筋です。空のファイルから、質問をして、答えをチェックして、不正な入力を拒否するプログラムまで。プログラミングの経験は必要ありません。数学の知識も必要ありません。あなたは意図的に何度も失敗させられます。
IGCSE と GCSE コンピュータサイエンス — 実際に採点される理論
Intermediate IGCSE と GCSE コンピュータサイエンス — 実際に採点される理論 論文の理論部分で、試験会場で生き残るように教えられています。メモリ階層とブート時に実際に起こること。コンパイラ、インタプリタ、アセンブラ、正しく聞こえるのに採点されない答えを含む。スプレッドシートからキーと正規化までのデータベース。Enter キーを押してページが表示されるまでの完全なパス、DNS も含む。システムソフトウェア、および試験用紙で最も簡単な 10 点の倫理と法律のセクション。
Programming for the Exam — Python Answers That Score
Intermediate Programming for the Exam — Python Answers That Score The programming half of the paper, taught at exam pitch. Pseudocode translated both ways, because the mark scheme is written in a notation nobody practises. Trace tables done column by column, including the ones with a loop and a condition inside it. Linear and binary search, bubble and insertion sort, what each costs and the comparison questions boards love. Validation against verification, and the boundary test data everybody forgets. Procedures against functions, and a systematic method for finding your own error with four minutes left.