Önceden deneyim sahibi olmam gerekiyor mu?

From Python to C++ — and Why the Difference Matters'yi başlamadan önce biraz ön bilgi önerilir.

From Python to C++ — and Why the Difference Matters ne kadar sürer?

From Python to C++ — and Why the Difference Matters 4 modül ve 12 ders içerir. Kendi hızınızda öğrenirsiniz.

Nasıl erişim sağlarım?

From Python to C++ — and Why the Difference Matters tüm ücretli aboneliklere dahildir.

code programming

From Python to C++ — and Why the Difference Matters

You already have a working Python program. You are going to write it again in C++, line for line, and reproduce its worst bug on purpose. Along the way you find out why the compiler wants to know the size of the box before you put anything in it, and why the error now arrives before the program has even run.

trending_upIntermediate
schedule6h 15m
menu_book12 ders
publicEnglish
workspace_premiumBasic

lock_open Öğrenmeye başla

From Python to C++ — and Why the Difference Matters

Özet

This is not a C++ course for people who have never programmed. It is a second language for someone who has a first one, taught entirely by contrast. Python let you write `age = 11` and never asked what `age` was. C++ makes you declare it, and it makes you choose between six kinds of box before you have put anything in one. That is annoying for about two hours and then it is the reason your program runs fast enough to finish inside a four-second limit. The spine of the segment is a port. You take the small question-and-answer script from the Python track — the one that asks your name, asks your favourite food and judges the answer — and you rebuild it in C++ a line at a time. Then you type your answer with a trailing space and it fails in exactly the same way it failed in Python. That is the point of the whole exercise. The trailing space was never a Python bug. It was an input bug, and it followed you. The last module points at USACO Bronze: what a competitive problem actually looks like on paper, how the input arrives, why the array is fixed at a thousand before you have read a single number, and why nearly everyone in that room is writing C++.

Kurs içeriği · 4 modül

lockErişimle açılır

01 The Box Has a Size
3 ders·1h 22m

Python worked out what you meant. C++ makes you say it in advance, once, and then holds you to it for the rest of the program. Everything in this module is that one trade, examined.
02 Where the Error Arrives
3 ders·1h 23m

Python runs a line, then reads the next one. C++ reads the whole file, refuses it if any part of it is wrong, and only then produces something you can run. Nothing you wrote today runs until all of…
03 The Port
3 ders·1h 55m

Port it, do not rewrite it. Same order, same questions, same output. If you improve it while you translate it you will not be able to tell which differences are C++ and which are you.
04 The Shape of a Contest Problem
3 ders·1h 35m

A contest problem is a contract. Input format, output format, constraints, limits. Read the constraints before you think about the algorithm — they are telling you which algorithm is allowed.

Sık sorulan sorular

From Python to C++ — and Why the Difference Matters kursunda ne öğreneceğim?: You already have a working Python program. You are going to write it again in C++, line for line, and reproduce its worst bug on purpose. Along the way you find out why the compiler wants to know the size of the box before you put anything in it, and why the error now arrives before the program has
Önceden deneyim sahibi olmam gerekiyor mu?: From Python to C++ — and Why the Difference Matters'yi başlamadan önce biraz ön bilgi önerilir.
From Python to C++ — and Why the Difference Matters ne kadar sürer?: From Python to C++ — and Why the Difference Matters 4 modül ve 12 ders içerir. Kendi hızınızda öğrenirsiniz.
Nasıl erişim sağlarım?: From Python to C++ — and Why the Difference Matters tüm ücretli aboneliklere dahildir.

Programlama içinde daha fazlası

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.

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.

Beginner Python From a White Sheet The exact sequence nine students have already walked, from a blank file to a program that asks questions, checks the answers and refuses bad input. No prior programming. No maths. You will break it repeatedly, on purpose.

Beginner AI Without the Hype What the model is actually doing when it answers you, why that produces something that looks like thinking, why it invents citations, and the cost mechanic almost nobody explains: a chat resends the entire conversation on every single turn. You will do the arithmetic yourself.

Intermediate IGCSE and GCSE Computer Science — Theory That Actually Gets Marked The theory half of the paper, taught so it survives the exam room. The memory hierarchy and what actually happens at boot. Compilers, interpreters and assemblers, including the answer that sounds right and scores nothing. Databases from a spreadsheet up to keys and normalisation. DNS and the full path between pressing Enter and seeing the page. Systems software, and the ethical and legal section that is the easiest ten marks on the paper.

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.