Sitemap
Parseyia Anthony

Parseyia Anthony

Weekly Progress Report #2

4 min readSep 27, 2026

Week 2: Interactive Programs & Decision-Making in Python

Week two of the Akwannya Hub Python Essentials course (Cisco Networking Academy) pushed me past static calculations and into the world of interactive programming. By working through Modules 2 and 3 on my own and then comparing notes with my pod during our group discussions, I picked up how to collect input from users, reshape data on the fly, and steer program flow with conditional logic. Below is a run-through of everything I tackled.

Module 2.6: Collecting Input & Manipulating Strings

  • The input() Function: Figured out how to pause a running program and grab whatever the user types on the keyboard. A vital lesson here — if you don't tuck that value into a variable, it vanishes into thin air.
  • Built-in Prompts: Found a tidier way to ask questions by slipping the message straight into the parentheses, like input("Enter your name: "), instead of wasting a separate print() call.
  • The String Trap: Wrapped my head around a rule that trips up nearly every beginner — input() hands back a string no matter what. Type in 25, and Python still sees "25". Try to do arithmetic on that, and the whole thing crashes.
  • Type Casting: Picked up three trusty converters: int() for whole numbers, float() for decimals, and str() for turning numbers back into text. An interesting quirk I noted — int() will chop off the decimal part of a float input, while float() demands a properly formatted number.
  • String Operators: Saw the + and * symbols take on entirely new jobs. The + glues strings end-to-end (concatenation), while * repeats a string as many times as you tell it (replication). Mixing text and numbers with + without converting first is a recipe for an error.
  • Hands-On Labs: Assembled a working calculator that reads user numbers, cracked a few operator-heavy expressions, and built a time calculator that leans on % and // to figure out when an event wraps up.

Module 3.1: Teaching Programs to Decide

  • Comparison Operators: Got comfortable posing yes/no questions with ==, !=, >, <, >=, and <=. Every one of them hands back either True or False. A distinction I drilled into my memory — = stores a value, while == checks whether two values match.
  • The if Statement: Learned to fence off a chunk of code so it only fires when a condition holds true. The recipe: the if keyword, the condition, a colon, then an indented block (four spaces is the convention).
  • The if-else Statement: Added a fallback path. If the condition fails, the else block takes over. Every decision now has a backup plan.
  • The elif Cascade: Discovered how to line up several conditions in a row. Python walks through them top to bottom and slams the brakes at the first true one — meaning only one branch of an if-elif-else chain ever runs.
  • Nested Conditions: Learned to tuck one if inside another. The indentation is what tells Python which else pairs with which if.
  • Hunting for the Largest Number: Practiced a smart strategy — assume the first value is the champion, then let each newcomer challenge it and take the crown if it’s bigger. Also met Python’s built-in max() function, which does the same job in one line.
  • Pseudocode & a Peek at Loops: Got introduced to writing out a plan in plain English before touching real code. Also saw why loops matter — without them, finding the largest of a thousand numbers would mean writing a thousand variables.
  • Hands-On Labs: Wrote a case-sensitive plant-name checker (Spathiphyllum), built a tax calculator using if-else and floating-point math, and coded a leap year detector with an if-elif-else chain powered by the % operator.

🤝 Nexus Pod Discussion Highlights

Get Parseyia Anthony’s stories in your inbox

Join Medium for free to get updates from this writer.

My pod came together this week for another open, judgment-free exchange of ideas. A few members walked us through the VS Code setup and cleared up a common misconception — Python and VS Code are separate tools that happen to work well together, not a package deal. We also swapped tips on using comments to label and temporarily silence code, walked through live examples of input() and its quirks, dug into how int() and float() behave differently, and traded tricks for concatenating and replicating strings.

The session wrapped with a nudge to keep experimenting in the sandbox and to reach out to mentors whenever anything felt unclear.

A big shout-out to the Akwannya Hub team and mentors for guiding us through another week.

Press enter or click to view image in full size

--

--