[[if code_where == 'home']][[if code_wk == 1]][[if code_total - 2 * floor(code_total / 2) == 0]][[if seen('sp.pawn')]]The pawn-shop laptop sits at the kitchenette counter, its fan whirring like a small hair dryer.[[else]] The old laptop sits at the kitchenette counter, the cracked hinge propped open with a folded receipt, the fan whirring like a small hair dryer.[[end]] You open the lesson notes Ms. Shaw emailed and start reading.[[else]] The laptop takes four minutes to wake up, so you make instant noodles while it does. By the time the screen is live the noodles are ready, and you start the new material with the bowl balanced next to the trackpad, blowing on a forkful between lines.[[end]][[end]][[if code_wk == 2]][[if code_total - 2 * floor(code_total / 2) == 0]] You get stuck on the same error for most of an hour. The battery dies because the charger only works when the cord is held at one specific angle, and you spend ten minutes finding it again. It finally runs, and you save the file three times.[[else]] Lou knocks on the door to borrow sugar, and when you open the door he sees the code on the screen and walks in without asking. He pulls up a chair. "What does this line do?" he asks. Then he points at the next one. You explain each line slowly and out loud, and that's how you finally understand it yourself.[[end]][[end]][[if code_wk == 3]][[if code_total - 2 * floor(code_total / 2) == 0]] It goes faster than the first two weeks. You notice you're typing without looking things up as often. One more week and the lesson is done.[[else]] The radiator bangs and the fan whines, and you don't notice either one because you're deep in the problem. When you look up it's two hours later and your neck is stiff. You close the file with one week left in the lesson.[[end]][[end]][[end]][[if code_where == 'library']][[if code_wk == 1]][[if code_total - 2 * floor(code_total / 2) == 0]] Your usual computer by the window is free. Ms. Shaw writes the week's topic on the whiteboard in blue marker and leaves you to it.[[else]] Gus, the retired bus driver, is two seats down typing with two index fingers and enormous care. He asks, "What are you starting this month?" You tell him, and he nods like it's a bus route he already knows.[[end]][[end]][[if code_wk == 2]][[if code_total - 2 * floor(code_total / 2) == 0]] The teenager who corrects Ms. Shaw leans over, points at your screen, and says, "There." The bug makes sense. You fix it, and by the time you say thank you she's back in her own chair.[[else]] The computer you always use is taken, so you get the one with the sticky space bar. It slows you down, and you reread each line before moving on.[[end]][[end]][[if code_wk == 3]][[if code_total - 2 * floor(code_total / 2) == 0]] Ms. Shaw stops behind your chair and reads for a while. "Next week you finish this lesson," she says, like it's a fact, not a compliment, and moves on.[[else]] You finish the week's work before the library closes for the first time, and spend the last ten minutes helping Gus find a missing bracket. He finds it, shakes his head at himself, and thanks you.[[end]][[end]][[end]] [[if code_lang == 'typescript']][[if code_level == 0]][[if code_wk <= 1]]You write a greeting in TypeScript. The editor underlines a typo in red before you even run the program, and it feels like being caught early instead of late.[[end]][[if code_wk == 2]] You store your name in a variable, typed as a string, and print three lines instead of one. The editor offers to finish the word for you when you start typing, because it already knows the variable is text.[[end]][[if code_wk >= 3]] You run the program from the command line and misspell the file name. The compiler answers with error TS6053, File not found, and names the file it went looking for, so you fix it in seconds.[[end]][[end]][[if code_level == 1]][[if code_wk <= 1]] You write a function that takes your age as a number. On purpose you pass it the word "nineteen" instead, and the editor refuses to run before anything happens. The error message tells you exactly what it expected and what it got.[[end]][[if code_wk == 2]] You write a function that takes a price and a budget, both typed as numbers, and prints whether it fits. TypeScript stops a string from sneaking in where a number belongs before the program ever runs.[[end]][[if code_wk >= 3]] You add a branch for when the price is exactly the budget. You test it with zero, a negative number, and a word where a number belongs, and TypeScript catches the word at the type level before the comparison even runs.[[end]][[end]][[if code_level == 2]][[if code_wk <= 1]] A loop adds up a week of shift hours from a list. The editor already knows every item in the list is a number.[[end]][[if code_wk == 2]] You loop over the days left until rent is due and print a countdown. TypeScript knows the loop variable is a number, so when you accidentally compare it to a string, the editor flags it before you run.[[end]][[if code_wk >= 3]] You keep a running total of spending inside the loop and break early when it passes the budget. The total is typed as a number, so TypeScript won't let you add a string to it by accident.[[end]][[end]][[if code_level == 3]][[if code_wk <= 1]] A tip calculator with typed inputs that rejects nonsense like a negative bill before the math ever runs. You try every bad input you can think of, and it turns them all away.[[end]][[if code_wk == 2]] You sketch the program on paper, then build the first half: typed inputs for a bill and a tip percentage, with the math done and printed. TypeScript fills in the types behind you, and the editor autocompletes the field names.[[end]][[if code_wk >= 3]] You finish the second half and rename the variables until the code reads almost like a sentence. The editor renames every use of the old name at once, because TypeScript knows exactly where each one is.[[end]][[end]][[if code_level == 4]][[if code_wk <= 1]] You save a to-do list to a file and load it back. A type describes what each item looks like, and when you read the file, the editor already knows the shape of what's coming back.[[end]][[if code_wk == 2]] You save a list of expenses to a JSON file, close the program, open it again, and read the list back. A type tells TypeScript what each item looks like, so the editor knows the shape of the data before the file loads.[[end]][[if code_wk >= 3]] You make the program handle a missing or empty file instead of crashing: the read sits in a try block, and the catch starts you with an empty list. The list is typed as an array of expenses, so even the empty one is the right shape.[[end]][[end]][[if code_level == 5]][[if code_wk <= 1]] You ask a city bus service when the next 14 bus comes, and you describe the shape of its answer as a type. When the response arrives, the editor helps you read it, showing every field without you asking.[[end]][[if code_wk == 2]] You fetch data from a free weather service and print just the temperature field. You write a type for the response, and the editor shows you every field available without you looking up the documentation.[[end]][[if code_wk >= 3]] You handle a failed request with a plain message instead of a crash. TypeScript types the error in the catch block as unknown, so you have to check what you caught before you print it.[[end]][[end]][[if code_level == 6]][[if code_wk <= 1]] You write tests for the tip calculator. One fails because of rounding, a cent off on every third bill. You fix it in one line.[[end]][[if code_wk == 2]] You write a test that passes, then change a plus to a minus in the code on purpose. The test fails, and the output names the exact line where the wrong answer came from.[[end]][[if code_wk >= 3]] You add tests for empty input, a huge number, and a negative bill. The negative one fails because the tip came out negative too, and you fix the code to floor it at zero.[[end]][[end]][[if code_level == 7]][[if code_wk <= 1]] You build a small budget tracker web page in TypeScript, with rent as the first line on the screen. The types catch three mistakes while you write, before you ever open it in a browser.[[end]][[if code_wk == 2]] You build the core of your project from start to finish, defining types for every piece of data that moves through it. The types catch a mismatch between two pieces of data before you ever run the program.[[end]][[if code_wk >= 3]] You fix the rough edges and write a short README so someone else could run it. You run the compiler one last time with strict checks on, and it passes clean, every type accounted for.[[end]][[end]][[end]][[if code_lang == 'javascript']][[if code_level == 0]][[if code_wk <= 1]] A button on a web page changes the page's text when you click it. You click it about forty times.[[end]][[if code_wk == 2]] You put your name in a variable and print three lines instead of one. JavaScript doesn't care if the variable is a string or a number, which is freeing and also a little reckless.[[end]][[if code_wk >= 3]] You run the file from the command line with node and misspell the file name. The error says the module cannot be found, and it takes you a minute to realize it's the file name, not the code, that's wrong.[[end]][[end]][[if code_level == 1]][[if code_wk <= 1]] A page that asks your name and greets you differently in the morning and at night. You change the computer's clock to test it, and it works.[[end]][[if code_wk == 2]] You write a program that asks for a price and says whether it fits your budget. JavaScript reads what you type as text, so "9" and "10" compare backward until you turn both into numbers.[[end]][[if code_wk >= 3]] You add a third answer for when the price is exactly the budget. You test it with zero, a negative number, and a word, and JavaScript doesn't stop you from comparing the word to a number. It just answers false every time, without an error.[[end]][[end]][[if code_level == 2]][[if code_wk <= 1]] A grocery list drawn on the page from a list in your code, one line per item, built by a loop. You add three things to the list and the page updates without you touching it again.[[end]][[if code_wk == 2]] You loop over the days left until rent is due and print a countdown. The loop counts down with i--, and the page redraws the list every time you refresh.[[end]][[if code_wk >= 3]] You keep a running total of spending inside the loop and break early when it passes the budget. JavaScript lets you add a number to a string by accident and quietly turns the whole thing into text, which you discover when the total reads like a sentence instead of a number.[[end]][[end]][[if code_level == 3]][[if code_wk <= 1]] A little countdown page that shows how many days are left until rent is due.[[if item_phone]] You open it on your phone and check it every morning this week.[[else]] You leave it open on the screen and check it every time you sit down.[[end]][[end]][[if code_wk == 2]] You plan the program on paper, then build the first half: a page with a bill input and a tip field. JavaScript grabs the values from the page as strings, and you have to convert them to numbers before the math works, which you forget once and get a very strange tip.[[end]][[if code_wk >= 3]] You finish the second half and rename the variables until the code reads almost like English. Miss one, and JavaScript says nothing until that line runs and throws a ReferenceError, which is how you find the two you missed.[[end]][[end]][[if code_level == 4]][[if code_wk <= 1]] Notes that stay saved in the browser even after you close the page and open it again. You close the tab, reopen it, and the list is still there, the same items in the same order.[[end]][[if code_wk == 2]] You save a list of notes to localStorage, close the tab, open it again, and the list is still there. JavaScript keeps the data in the browser, so it only exists on this device, which Ms. Shaw has said is fine for now.[[end]][[if code_wk >= 3]] You make the program cope with an empty list instead of crashing when there's nothing saved yet. JavaScript returns null when the storage is empty, and your code has to check for it before it tries to loop over something that isn't there.[[end]][[end]][[if code_level == 5]][[if code_wk <= 1]] A page that asks for the weather and turns its background gray when it's going to rain. The next time rain is in the forecast, the page goes gray on its own.[[end]][[if code_wk == 2]] You fetch data from a free weather service and print just the temperature. JavaScript's fetch returns a promise, and you learn to write await before it, so the program waits for the answer instead of trying to read data that hasn't arrived.[[end]][[if code_wk >= 3]] You handle a failed request with a plain message instead of a crash. The catch block runs when the internet is down, and you test it by switching off the network and watching the message appear.[[end]][[end]][[if code_level == 6]][[if code_wk <= 1]] A test for a function that formats prices. It catches $10.5 where it should say $10.50.[[end]][[if code_wk == 2]] You write a test that passes, then break the code on purpose and watch it fail. The test runner prints a green check for pass and a red X for fail, and you stare at the red X until you find what you broke.[[end]][[if code_wk >= 3]] You add tests for empty input, a huge number, and a negative bill. The empty one fails because JavaScript turns an empty string into zero when you do math with it, which is a thing you now know and will never forget.[[end]][[end]][[if code_level == 7]][[if code_wk <= 1]] A tiny game that runs in the browser, catching falling coins with a paddle. Anyone with the link can play it.[[if item_phone]] You send the link to yourself and play it on your phone the next time you ride the bus.[[end]][[end]][[if code_wk == 2]] You build the core feature of your own project from start to finish, with functions that pass data to each other. JavaScript doesn't check types between functions, so you trace bugs by printing what each one receives, one console log at a time.[[end]][[if code_wk >= 3]] You fix the rough edges and write a short README so someone else could run it. You test it in two different browsers, and it works in both, which feels like a small miracle.[[end]][[end]][[end]][[if code_lang == 'python']][[if code_level == 0]][[if code_wk <= 1]] You print a greeting, then have Python work out how many weeks are left until rent is due. It does the math in one line, and the answer is fewer weeks than you hoped.[[end]][[if code_wk == 2]] You put your name in a variable and print three lines instead of one. Python uses indentation to know where each line belongs, so you learn to line them up exactly.[[end]][[if code_wk >= 3]] You run the file from the command line with python and misspell the file name. Python says it can't find the file, plain and short, and you fix one letter and run it again.[[end]][[end]][[if code_level == 1]][[if code_wk <= 1]] A script that asks how much cash you have and says whether this week is covered. You run it with your real numbers.[[end]][[if code_wk == 2]] You write a program that asks for a price and says whether it fits your budget. Python's input function always gives you a string, so you have to convert it to a number before the comparison works.[[end]][[if code_wk >= 3]] You add a third answer for when the price is exactly the budget. You test it with zero and a negative number, then with a word, and Python crashes on the word with a ValueError that tells you exactly what it couldn't convert.[[end]][[end]][[if code_level == 2]][[if code_wk <= 1]] A loop adds up a list of grocery prices. You run the same loop over a thousand made-up prices, and the answer appears instantly.[[end]][[if code_wk == 2]] You loop over the days left until rent is due and print a countdown. Python's for loop reads like a sentence: for each day in the days that are left, print the number.[[end]][[if code_wk >= 3]] You keep a running total of spending inside the loop and stop early when it passes the budget. Python's break keyword jumps out the moment the total goes over, and the program prints how many items it took.[[end]][[end]][[if code_level == 3]][[if code_wk <= 1]] A grocery-list program that adds items, removes them, and prints the total. You add everything you bought this week, remove the thing you took back, and the number is right.[[end]][[if code_wk == 2]] You sketch the program on paper, then build the first half: a grocery list with add and remove. Python lists hold anything, so you can put strings and numbers in the same one, which Ms. Shaw has said is allowed but not wise.[[end]][[if code_wk >= 3]] You finish the second half and rename the variables until the code reads almost like English. Python's naming convention uses underscores between words, so total_spending reads like two words glued together, which it's.[[end]][[end]][[if code_level == 4]][[if code_wk <= 1]] You read a spreadsheet file of shifts and total the hours and pay for the month. Four lines of Python do what would take an hour with a calculator.[[end]][[if code_wk == 2]] You save a list to a file, close the program, open it again, and read the list back. Python's json module turns the list into text and back, and the data comes out in the same order it went in.[[end]][[if code_wk >= 3]] You make the program cope with a missing or empty file instead of crashing. Python raises a FileNotFoundError when the file isn't there, and you catch it with a try block that prints a plain message instead.[[end]][[end]][[if code_level == 5]][[if code_wk <= 1]] You ask a free online service for the exchange rate and print what a dollar is worth in pesos today. It changes every time you run it, and you run it three times just to watch.[[end]][[if code_wk == 2]] You ask a free weather service for data and print just the temperature. Python's requests library makes the call in two lines, and the answer comes back as a dictionary, so you pull the field out by name.[[end]][[if code_wk >= 3]] You handle a failed request with a plain message instead of a crash. Python raises an exception when the service is down, and you catch it the same way you caught the missing file, with a try and a message.[[end]][[end]][[if code_level == 6]][[if code_wk <= 1]] Tests for the pay calculator. One fails on overtime hours, a bug where the extra half-time was never added. The fix is one line.[[end]][[if code_wk == 2]] You write a test that passes, then break the code on purpose and watch the test catch it. Python's assert keyword prints nothing when it passes and a full traceback when it fails, so the silence is the good outcome.[[end]][[if code_wk >= 3]] You add tests for empty input, a huge number, and a negative value. The empty list makes the function divide by zero, and Python raises a ZeroDivisionError, which is exactly what it's called.[[end]][[end]][[if code_level == 7]][[if code_wk <= 1]] A script that sorts your spending into food, rent, [[if item_phone]]phone, [[end]]and bus fare, and draws a simple chart of it. The bar for food is taller than you expected.[[end]][[if code_wk == 2]] You build the core feature of your own project from start to finish, with functions that call each other. Python doesn't need types declared, so the code is short, and you spend the saved time on the logic instead.[[end]][[if code_wk >= 3]] You fix the rough edges and write a short README so someone else could run it. You add a requirements file listing the libraries you used, so anyone with Python installed can install them with one command.[[end]][[end]][[end]][[if code_lang == 'rust']][[if code_level == 0]][[if code_wk <= 1]] A new Rust project that prints hello. The first try fails over a missing quote mark, and the error message tells you exactly where. You fix it and it runs.[[end]][[if code_wk == 2]] You put your name in a variable and print three lines instead of one. Rust requires the mut keyword to make a variable changeable, but a name that stays the same needs nothing extra, and the compiler is happy.[[end]][[if code_wk >= 3]] You move the greeting into its own module file and misspell its name on the mod line. cargo run stops with error E0583, file not found for module, and the help line names the exact file it looked for.[[end]][[end]][[if code_level == 1]][[if code_wk <= 1]] A running total that refuses to change until you tell Rust it's allowed to change. The error explains why in plain words, and once you write the keyword it needs, it works.[[end]][[if code_wk == 2]] You write a program that asks for a price and says whether it fits your budget. Rust makes you read input as a string and convert it to a number, and if the conversion fails, it returns an error you have to handle.[[end]][[if code_wk >= 3]] You add a third answer for when the price is exactly the budget. You test it with zero, a negative number, and a word, and Rust's parse function returns an error for the word instead of letting it through, so you write a fallback.[[end]][[end]][[if code_level == 2]][[if code_wk <= 1]] A loop over a list of numbers. Rust stops you from changing the list while you're still reading it, and when you think about it, you see why that would have gone wrong.[[end]][[if code_wk == 2]] You loop over the days left until rent is due and print a countdown. In Rust you count down by taking a range and turning it around, so the loop reads (1..=days).rev().[[end]][[if code_wk >= 3]] You keep a running total inside the loop and stop early when it passes the budget. Rust's ownership rules mean the loop borrows the list read-only, so you can't accidentally change it while counting.[[end]][[end]][[if code_level == 3]][[if code_wk <= 1]] The number-guessing game from the free Rust book, guess from 1 to 100, too high or too low. You play it ten times, and by the end you never need more than seven guesses.[[end]][[if code_wk == 2]] You sketch the program on paper, then build the first half: input and comparison. Rust's match keyword handles the too-high and too-low branches cleanly, and the compiler checks that every case is covered.[[end]][[if code_wk >= 3]] You finish the second half and rename the variables until the code reads almost like English. Rust's compiler follows every rename and tells you if you missed one, which you did, twice.[[end]][[end]][[if code_level == 4]][[if code_wk <= 1]] You read a file, and Rust won't let the program run until you say what happens if the file is missing. You write the fallback, and the program runs.[[end]][[if code_wk == 2]] You save a list to a file, close the program, open it again, and read the list back. Rust's serde library turns the list into text and back, and the types survive the round trip.[[end]][[if code_wk >= 3]] You make the program cope with a missing or empty file instead of crashing. Rust's Result type forces you to handle the error case before the program compiles, so the fallback is not optional.[[end]][[end]][[if code_level == 5]][[if code_wk <= 1]] You download a web page and count its words, with a plan for what to do when the internet is down. The plan runs the first time, because the internet is, in fact, down.[[end]][[if code_wk == 2]] You fetch data from a free weather service and print just one field. Rust's serde reads the JSON into a struct you defined, so the field is typed and named before the program runs.[[end]][[if code_wk >= 3]] You handle a failed request with a plain message instead of a crash. Rust's question mark operator passes the error up the stack, and you write the message at the top where it lands.[[end]][[end]][[if code_level == 6]][[if code_wk <= 1]] Tests for the word counter. One catches an off-by-one mistake on the last word.[[end]][[if code_wk == 2]] You write a test that passes, then break the code on purpose and watch the test catch it. Rust's tests live in the same file under a test module, and cargo test prints the failure with the exact value that was wrong.[[end]][[if code_wk >= 3]] You add tests for empty input, a huge number, and a negative value. The huge number overflows the total, and because tests run in debug mode, Rust panics with attempt to add with overflow instead of quietly wrapping around. You switch to a bigger integer type, and the negative value exposes a logic bug you fix in one line.[[end]][[end]][[if code_level == 7]][[if code_wk <= 1]] A fast little tool that searches a folder of text files for a word. It's the fastest program you've ever written.[[end]][[if code_wk == 2]] You build the core feature of your own project from start to finish, with functions that pass data through a pipeline. Rust's ownership tracks every piece of data through every function, and the compiler catches two mistakes you wouldn't have found until much later.[[end]][[if code_wk >= 3]] You fix the rough edges and write a short README so someone else could run it. You run cargo build one last time and it compiles with zero warnings, which Ms. Shaw has said is rare enough to celebrate.[[end]][[end]][[end]][[if code_lang == 'go']][[if code_level == 0]][[if code_wk <= 1]] A Go program that prints hello. It builds and runs so fast you think it didn't run, so you run it again just to be sure. Go also tidies your spacing for you without asking.[[end]][[if code_wk == 2]] You put your name in a variable and print three lines instead of one. Go's := operator declares a variable and sets it in one stroke, and the compiler infers it's a string without you saying so.[[end]][[if code_wk >= 3]] You run the program with go run and misspell the file name. Go answers with one blunt line, no such file or directory, and you fix the spelling and run it again in under a second.[[end]][[end]][[if code_level == 1]][[if code_wk <= 1]] A greeting that changes with the hour of the day, using Go's short way of making variables. You change the hour to test it, and the greeting changes.[[end]][[if code_wk == 2]] You write a program that asks for a price and says whether it fits your budget. Go reads input as a string and you convert it with strconv, and if the conversion fails, the function returns an error alongside the result, the Go way.[[end]][[if code_wk >= 3]] You add a third answer for when the price is exactly the budget. You test it with zero, a negative number, and a word, and the word fails the conversion and returns an error, which you check and print, the same three lines you always write.[[end]][[end]][[if code_level == 2]][[if code_wk <= 1]] A loop, Go's only kind of loop, over a list of shift hours to add them up. One kind of loop means one thing to remember.[[end]][[if code_wk == 2]] You loop over the days left until rent is due and print a countdown. Go has only one loop keyword, for, and it handles ranges, conditions, and counters, so there's one thing to learn and you already know it.[[end]][[if code_wk >= 3]] You keep a running total inside the loop and stop early when it passes the budget. Go has no while loop, so you write for with just a condition, and break jumps out the moment one purchase pushes the total over.[[end]][[end]][[if code_level == 3]][[if code_wk <= 1]] A tiny web server that answers hello to anyone who visits its address. You open it [[if item_phone]]on your phone's browser[[else]]in a second browser window[[end]] and the word is there, and you grin at it because you put something on the internet.[[end]][[if code_wk == 2]] You sketch the program on paper, then build the first half: a small web server with one route. Go's standard library includes the server, so you write no imports beyond what comes with the language, and it runs in a dozen lines.[[end]][[if code_wk >= 3]] You finish the second half and rename the variables until the code reads almost like English. In Go, a name that starts with a capital letter can be used from other packages and a lowercase one can't, so renaming is also deciding what to share.[[end]][[end]][[if code_level == 4]][[if code_wk <= 1]] You save notes to a file and read them back, checking for an error every single time, the Go way. The repetition is the point, and nothing goes wrong.[[end]][[if code_wk == 2]] You save a list to a file, close the program, open it again, and read the list back. Go's encoding package turns the list into JSON and back, and every function returns an error that you check, the same three lines, every time.[[end]][[if code_wk >= 3]] You make the program cope with a missing or empty file instead of crashing. Go returns an error from os.ReadFile when the file is absent, and you handle it with an if check that prints a message and moves on.[[end]][[end]][[if code_level == 5]][[if code_wk <= 1]] A server that asks another service for something and hands the answer back, neatly packaged. You visit the address and the answer is there, and you didn't have to know where it came from.[[end]][[if code_wk == 2]] You fetch data from a free weather service and print just one field. Go's struct defines the shape of the response, and the JSON decoder fills it in, so you read the field by name from the struct, not from a raw dictionary.[[end]][[if code_wk >= 3]] You handle a failed request with a plain message instead of a crash. Go's error is just a value, so you check it with an if statement and write the message yourself, no try or catch, just the same pattern you've been writing all course.[[end]][[end]][[if code_level == 6]][[if code_wk <= 1]] A table of test cases for one function. One row fails, and the table shows exactly which input broke it, so you fix that one and run it again, and all the rows pass.[[end]][[if code_wk == 2]] You write a test that passes, then break the code on purpose and watch the test catch it. Go's testing package runs with go test, and a failure prints the test's name and the line that reported it.[[end]][[if code_wk >= 3]] You add tests for empty input, a huge number, and a negative value. Go's table-driven tests put every input and expected output in a slice, and the failing row prints its name, so you know exactly which case broke.[[end]][[end]][[if code_level == 7]][[if code_wk <= 1]] A small service with two addresses that can answer many people at once without slowing down. You open both addresses [[if item_phone]]on your phone[[else]]in two browser tabs[[end]] and they both work, and neither one makes the other wait.[[end]][[if code_wk == 2]] You build the core feature of your own project from start to finish, with functions that pass data to each other. Go's interfaces let functions accept any type that has the right methods, so your code stays flexible without you planning for it.[[end]][[if code_wk >= 3]] You fix the rough edges and write a short README so someone else could run it. You run go build one last time and the binary appears in the folder, a single file that runs on any machine with the same operating system, no installer needed.[[end]][[end]][[end]]