Month: January 2026

Posted on

Weather Up! (And API Down… Then Up Again)

Day 11 of 100 Days Coding Challenge: Python

Let’s talk weather. Today’s project is a Python weather app using the OpenWeatherMap API—because there’s nothing like stepping out in a parka when it’s 80 degrees and sunny. I wanted a tool that would tell me if the sky is smiling or sobbing.

My goal? Get the current weather description (like “clear sky” or “air you can drink”), temperature in both Celsius and Fahrenheit (because I live in Celsius and my husband lives in Fahrenheit—we’ve agreed to disagree), and humidity (mostly for hair-related decisions). If this app could avoid one argument about overdressing, it would already be worth it.

Today’s Motivation / Challenge

The motivation was simple: make a useful, real-world app that doesn’t just live in the land of console output. Also, this was the perfect excuse to play with an API and brush up on Python’s ability to talk to the internet like a well-mannered bot. Plus, nothing says “grown-up developer” like a weather app you built yourself.

Purpose of the Code (Object)

This program lets you type in a city name and then fetches the current weather for that location. It displays the weather description, temperature in both Celsius and Fahrenheit, and the humidity. It’s a lightweight, beginner-friendly way to explore APIs, data handling, and basic user interaction with Python. No fancy dashboards, just solid weather facts.

AI Prompt: Make it cleaner

Create a simple Python weather checker using the OpenWeatherMap API. It should take a city name as input and return weather description, temperature in Celsius and Fahrenheit, and humidity. Keep it beginner-friendly and avoid unnecessary complexity. Please make the code for the GUI.

Functions & Features

  • Fetches real-time weather for any city using OpenWeatherMap API
  • Displays weather description, temperature (°C and °F), and humidity
  • Supports basic error handling (invalid city names, bad API keys, etc.)

Requirements / Setup

  • Python 3.x
  • requests library

pip install requests

Minimal Code Sample

response = requests.get(f”https://api.openweathermap.org/data/2.5/weather?q={city}&appid={API_KEY}&units=metric”)

data = response.json()

temp_c = data[‘main’][‘temp’]

temp_f = (temp_c * 9/5) + 32

Weather Checker App

This little stretch of code is like your personal weather butler. First, it knocks on OpenWeatherMap’s digital door and politely asks, “Excuse me, what’s the weather like in [city] today?” Then it grabs the answer, digs into the juicy details, and pulls out the temperature in Celsius. But wait—because not everyone lives in metric harmony—it whips out its calculator and converts it into Fahrenheit, just in case someone in the household insists on imperial drama.

Notes / Lessons Learned

I got the code, ran it… 401 error. Unauthorized. Rude. I copied the API key. I pasted it into my browser like so:
https://api.openweathermap.org/data/2.5/weather?q=Chicago&appid={API key}

Still 401. I stripped the key just in case it was haunted by invisible characters:

 API_KEY = “your_api_key”.strip()

Nada.

Then I tried curl from the command line like a tech-savvy detective:

 curl “https://api.openweathermap.org/data/2.5/weather?q=Chicago&appid={API_KEY}&units=metric”

 And BOOM—it worked!

Turns out my API key hadn’t activated yet. (Yes, that’s a thing. No, I didn’t read the fine print. Yes, I will next time. Maybe.)
Once the key was activated, I plugged it into my app and voilà—weather at my fingertips.

Optional Ideas for Expansion

  • Add a simple GUI with tkinter
  • Show weather-based icons or descriptions (e.g., “Bring an umbrella” for rain)
  • Include a 3-day forecast by upgrading to the OpenWeatherMap One Call API

Day 10
Day 12

Posted on

Hangman: Now With 100% More Drama

Day 10 of 100 Days Coding Challenge: Python

Today, I felt bold. No more basic calculators. No more polite input prompts. I wanted to make a game—something a little more chaotic good. So I chose the classic: Hangman. But not just any hangman. Oh no. I wanted emojis, buttons, sound effects, and drama.

The goal? Create something that could rival middle school memories, minus the chalkboard and emotional scarring. I didn’t just want to code—I wanted a full-blown performance. One wrong guess and boom, a dramatic sound plays. It’s Hangman, but with flair like Shakespeare meets Tkinter.

Today’s Motivation / Challenge

Games are fun to build because they feel alive. They react, they make noise, they mock your guesses (sometimes too quickly). This project allowed me to apply everything I’ve learned so far—logic, GUIs, and user input—but in a playful way. It also scratched that nostalgic itch of typing letters into a school computer and hoping not to draw the stick figure’s head. Plus, there’s something weirdly satisfying about pushing a button and hearing a ding. It’s Pavlovian, really.

Purpose of the Code (Object)

This project creates a simple Hangman game with a graphical interface. The player guesses letters by clicking buttons, and the game shows progress with emoji art and sound effects. It’s a fun and interactive way to practice conditionals, loops, and GUI design—without requiring any advanced programming knowledge. Beginners can build it, play it, and immediately annoy their family with the sound effects.

AI Prompt: Make it cleaner.

Create a Hangman game in Python using Tkinter. Include emoji-based visuals for the hangman and sound effects for correct, incorrect, win, and lose outcomes. Add a restart button to replay without restarting the app.

Functions & Features

  • Button-based letter guessing (no typing required)
  • Emoji visuals that change with each incorrect guess
  • Sound effects for correct, incorrect, win, and lose outcomes
  • Restart button to play again instantly
  • Tracks lives and guessed letters in real time

Requirements / Setup

  • Python 3.x
  • Tkinter (comes with Python)

Install playsound module (use this version!):


pip install playsound==1.2.2

Minimal Code Sample

from playsound import playsound

def guess_letter(letter):

    global lives

    if letter not in secret_word:

        lives -= 1

        playsound(“wrong.wav”)  # Plays sound for wrong guess

This plays a sound when the user guesses incorrectly.

hungman_gui

Notes / Lessons Learned

Turns out version 1.2.2 of the playsound module works best, so if you try this at home—just skip the suffering and install that one. You’re welcome. I grabbed a few .wav files from freesound.org, which is great, but somehow every username I tried was taken. Even “CodeWizard47” and “ILoveLoops.” Apparently I’m not special. Also, be warned: your .wav files must be in the same folder as your script unless you create an asset folder and specify the path.

Sound + visuals = more chaos to debug, but also way more fun to play.

Optional Ideas for Expansion

  • Add a timer to increase the pressure
  • Create categories (animals, tech terms, random snacks)
  • Keep score across rounds or show a leaderboard

Day 9
Day 11

Posted on

The Mysterious Case of My Monday Weight That Didn’t Move

Brian’s fitness journal after a brain stroke

After my run today, I stepped on the scale expecting the usual Monday plot twist—only to find that my weight and body composition hadn’t changed since Saturday. This was deeply suspicious.

For the past several weeks, Monday has reliably been my heaviest day of the week. I’ve learned not to take it personally. I usually blame the weekend—and more specifically, pizza. Delicious, sourdough-based, entirely worth it pizza.

My kidneys, however, do not behave like those of a perfectly cooperative adult. Depending on what I eat, my body becomes very enthusiastic about holding onto water. Most days, we eat healthy, homemade meals. Pizza is strictly a once-a-week luxury. Still, every Sunday I make sure pizza happens. Every Monday, my weight usually responds accordingly—thanks to a combination of glycogen storage and water retention.

So today’s unchanged number was unexpected.

I generally try not to obsess over my weight. It can swing by a few pounds easily, and I’ve learned not to panic. This past weekend, I ate exactly as I usually do. My exercise routine was also mostly unchanged—except for a peaceful three-kilometer walk with my wife on Sunday. The weather was lovely, and she wanted some sunshine. I wouldn’t expect that walk to single-handedly rewrite my Monday numbers, but I can’t think of any other explanation either.

I track my weight alongside my other biometrics because my nephrologist uses these trends to monitor my overall health. When we meet, he checks for sudden changes in weight, blood pressure, or heart rate. His rule of thumb is simple: sharp shifts usually mean something is going on inside the body.

Since I’m less active now than I was in the summer, I actually expected maintaining my weight to become easier. But because I move less in winter, I’ve also cut back on snacks. With kidney disease, almost everything seems to contain something I’m supposed to limit—phosphate, sugar, potassium, salt. Sometimes avoiding food altogether feels like the safest strategy.

Because my weight usually fluctuates more than this, today’s stability caught me off guard. At the same time, it means I need to be more careful this week. Starting lower than usual raises the risk of losing muscle too quickly—and that’s something my doctor very much does not want.

So for now, I’ll watch the numbers, eat carefully, move thoughtfully, and let the scale do its strange little science experiment in peace.

Back
Next

Posted on

Split Happens: A GUI Tip Calculator That Doesn’t Judge

Day 9 of 100 Days Coding Challenge: Python

Once upon a time—aka last year—I built my first tip calculator in Python. It lived in the command line, wore black, and gave off strong hacker-in-a-diner vibes. You’d open the terminal, type in your numbers, and squint like you were breaking into a Michelin-starred mainframe.
Fast forward to today: that humble little tool got a much-needed makeover. Out with the minimalism, in with the buttons and window dressing. I gave it a GUI, added some visual flair, and—because I can’t resist—threw in a few emoji just for the drama. Because splitting the check shouldn’t feel like tax season, it should feel like friendship, math you can trust, and just a dash of fun.

Today’s Motivation / Challenge

Splitting the bill is easy… until someone pulls out a calculator and says, “Wait, how much with tip?” Then it becomes a group project in advanced math, complete with decimal debates and passive-aggressive sighs. Today’s challenge was to take that stress and turn it into something visual, intuitive, and mildly delightful. A GUI tip calculator solves a real-world problem with just enough code to feel proud—but not overwhelmed. It’s also a great excuse to practice building interfaces without becoming a full-time software architect.

Purpose of the Code (Object)

This program prompts the user to enter the number of people in the group, the total bill, and the desired tip percentage. Then it calculates the tip, adds it to the total, and shows how much each person owes. It’s a handy tool for group dinners or awkward birthday lunches when no one wants to do mental math.

AI Prompt

Create a GUI app in Python that:

  • Asks the user for number of people, bill amount, and tip percentage
  • Calculates total tip, total amount with tip, and per-person payment
  • Displays the results in a user-friendly window with labeled input fields and a result area

Functions & Features

  • Prompts for number of people, bill amount, and desired tip percentage
  • Calculates total tip and total amount
  • Splits the bill evenly between party members
  • Displays everything in a clean, readable GUI with labeled entries and a result section

Requirements / Setup

Library Requirement: pip install tk

This app runs on Python 3.x and uses the built-in tkinter module for the interface.

Minimal Code Sample


tip_amt = receipt_amt * (tip_percent / 100)
total_amt = receipt_amt + tip_amt
per_person = total_amt / num_people

This logic calculates the tip and divides the total among the group.

TipTopSplitter

Notes / Lessons Learned

Once the app was running, I showed it off to my husband. He clicked the buttons, tried a few different amounts, and gave it a test run with some imaginary sushi bills. No standing ovation, but he did mumble, “Hmm, not bad,” with just enough approval to make me smug.
Honestly, the hardest part wasn’t the math—it was spacing the widgets just right. Building GUIs is like setting a dinner table: all the pieces matter, and you’ll only notice when something is off.

Optional Ideas for Expansion

  • Add a dropdown for common tip amounts (10%, 15%, 20%)
  • Include a dark mode (because tip math deserves mood lighting)
  • Add a “copy to clipboard” button to paste payment amounts into your group chat

Day 8
Day 10

Posted on

Time, Ticks, and Birthday Tricks with Python birthday countdown app

Day 8 of 100 Days Coding Challenge: Python

After a certain age—which I’d rather not disclose—the excitement of birthdays began to fade. The promise of cake and candles slowly gave way to the grim arithmetic of filling out forms. These days, I find myself less eager to celebrate and more focused on avoiding mirrors, calculators, and the word age.

Some applications are merciful and only ask for your birthdate. Others, however, are far less tactful—they demand your age outright, forcing you to confront the passing years in cold, hard numbers. To soften that emotional blow, I decided to build something playful: a Birthday Countdown and Age Calculator. It answers life’s small but dramatic questions, such as “How long until I’m older?” and “Exactly how much older am I now?” Whether that brings joy or existential dread is entirely your choice. So, I built a Python birthday countdown app.

Today’s Motivation / Challenge

This idea came from one of those moments when you wonder, Why don’t I already have this in my life? I wanted a lighthearted app that could tell me how far away my next birthday was—and, while at it, remind me just how far I’ve come. It’s perfect for when forms, job interviews, or curious children insist on knowing your exact age.

Beyond curiosity, this project gave me a chance to strengthen my Tkinter GUI skills. I wanted to design something simple, cheerful, and mildly threatening—a friendly little window that cheerfully informs you of your own aging process.

Purpose of the Code (Object)

The app asks for your birthdate, calculates your current age, and shows how many days remain until your next birthday. It turns all that existential math into something visual and almost comforting—a bright window with friendly text and a bit of decorative flair.

Best of all, there’s no math required on your part. The app handles everything for you—delivering the results instantly, for better or worse.

AI Prompt: Make it cleaner

Create a Python app with a GUI using tkinter that asks for a user’s birthdate, then displays how old they are and how many days remain until their next birthday. Include light-hearted messaging and emoji art in the GUI labels.

Functions & Features

  • Asks the user to enter their birthdate
  • Calculates and displays the current age
  • Tells you how many days are left until your next birthday
  • Shows the results in a friendly pop-up window with styled text

Requirements / Setup

Python 3.7+
No extra libraries are required—just the good old tkinter, which comes built-in.

Minimal Code Sample

from datetime import datetime
birth_date = datetime.strptime("1990-07-20", "%Y-%m-%d").date()
today = datetime.today().date()
age = today.year - birth_date.year
if (today.month, today.day) < (birth_date.month, birth_date.day):
    age -= 1
next_birthday = birth_date.replace(year=today.year)
if next_birthday < today:
    next_birthday = next_birthday.replace(year=today.year + 1)

days_until = (next_birthday - today).days

This snippet calculates your current age and how many days until your next birthday.

Birthday GUI App

Notes / Lessons Learned

For the record, I was never what you’d call a macro wizard. In my early days, I was more of a macro gremlin—copying random snippets from mysterious corners of the internet and hoping something, somewhere, would work.

But today felt different. I built this GUI myself—with a little help from AI—and for once, I felt like a real coder. Decorative buttons and all. It wasn’t perfect, but it was mine, and that felt pretty great. I even realized I could reuse and modify the same logic for my next app.

When I tested it, the program politely informed me how many days remain until I’m older (how thoughtful) and reminded me of my current age (again, thank you very much). Naturally, I showed it off to my husband. He gave a proud nod, followed by the classic question:
“Wait… does it use my birthday too?”

And that, my friends, was today’s code—equal parts functional, funny, and mildly existential.

Optional Ideas for Expansion

  • Let the user save multiple birthdays (friends, family, pets, plants)
  • Add a feature to notify you when your birthday is one week away
  • Include an optional countdown animation or confetti pop-up

Day 7
Day 9

Posted on

Early Wake-Ups, Asian Groceries, and a Very Organized Saturday

Brian’s fitness journal after a brain stroke

Today’s plan was simple: visit the Asian grocery store and then pick up flea medication for our kitten on the way home. Both places open at 8:00 a.m., which left me with that uniquely uncomfortable block of time between my normal wake-up time and when departure is actually allowed. It is because I have a long list of a Saturday morning routine.

I usually wake around 7 a.m. I need more sleep than my wife—about 7.5 to 8 hours—thanks to a brain injury that politely requires extra rest. One doctor told me I’d need it. An occupational therapist told me to keep a consistent schedule. So now I live in a delicate alliance with both science and my alarm clock.

My wife, on the other hand, operates like a Swiss watch. Saturdays do not alter her internal firmware. She wakes up roughly two hours earlier than I do, workday or not. She says it’s because her brain works best when her schedule is regulated. I believe her. I also fear her efficiency.

This left me with too much time to do nothing… but not quite enough time to comfortably start my usual full Saturday morning routine.

Fortunately, my wife, our kitten, and my bladder formed a secret alliance and woke me up an hour early. I briefly considered going back to sleep. Then I remembered that future-me would be grateful if present-me used the bonus hour wisely. So I stayed up.

Our kitten, as always, was thrilled. She waits patiently on the bed every morning until I open my eyes—sometimes even dragging her beloved toy mouse with her. I’ve been hiding that toy before bedtime because otherwise she launches nighttime solo parkour sessions and loses it somewhere in the house. This morning, she didn’t need the toy. She already had me. Her happiness upon my awakening was… overwhelming.

I fed the kitten, poured my cereal, completed my texting and language-app practice, and even finished my morning exercises. And just like that, I had less than thirty minutes before departure—perfect timing to work on this post.

It turns out doing part of my routine before the grocery run is surprisingly satisfying. That’s one less task waiting for me when I return home.

So thanks to Artemis, my wife, and my kidneys, my day already feels strangely coordinated.

Once we return, I’ll prep for my weekly 10K run, cook supper, and then head out again for our regular grocery trip. I sincerely hope my wife’s perfectly structured day forgives the extra logistics.

Back
Next

Posted on

Python BMI calculator: Because Mass is Interesting

Day 7 of 100 Days Coding Challenge: Python

Ah yes, the BMI calculator—a classic Python rite of passage. I built one last year when I was still figuring out how loops worked and thought elif was a typo. It worked… but only in metric. That was fine for me, having grown up in Japan and lived in Canada, where weight is measured in kilograms, height is measured in meters, and the weather is often cold.

But then I remembered: the U.S. exists. A land where temperature is measured in fractions of lava and weight in pounds that are somehow not British. Clearly, this app needed to accommodate both worlds—metric precision and imperial chaos.

So this time, I added a choice: metric or imperial. Because inclusivity matters. I even sprinkled a little personality into the experience—some clever text formatting, gentle prompts, and error handling. As a Japanese person, I believe that even software should have good manners.

Today’s Motivation / Challenge

The challenge today wasn’t just writing a BMI calculator—it was writing one that respects cultural measurement quirks. The metric system is excellent, but millions of people use the imperial system, and they deserve not to be confused. More importantly, this was an opportunity to practice user input, conditionals, and conversions—all critical building blocks in a beginner’s coding toolkit. And let’s be honest: anything that turns body mass into a friendly number is kind of fun.

Purpose of the Code (Object)

This app calculates your Body Mass Index based on your weight and height. You choose whether to use the metric system (kilograms and meters) or the imperial system (pounds and inches). Behind the scenes, the code converts everything into metric and then applies the BMI formula. The result? A simple number—and a label—that gives you a rough idea of your body composition.

AI Prompt

Write a Python app that asks users to choose metric or imperial units, collects weight and height, converts if needed, and calculates BMI with a health category.

Functions & Features

  • Prompts user to choose between metric and imperial units
  • Collects weight and height accordingly
  • Converts imperial inputs to metric for calculation
  • Calculates BMI using the standard formula
  • Classifies the result (underweight, normal, overweight, or obese)
  • Includes input validation with try/except to handle typing hiccups

Requirements / Setup

  • Python 3.x
  • No external libraries needed (runs with pure Python)

Minimal Code Sample

python

CopyEdit

if unit == “imperial”:

    weight_kg = weight_lbs * 0.45359237

    height_m = height_in * 0.0254

bmi = weight_kg / (height_m ** 2)

This snippet handles unit conversion and calculates BMI.

BMI Calculator App

Notes / Lessons Learned

By the way, I used try/except to catch input errors because I care about user experience—and also because I’ve personally broken every beginner app by typing “ten” instead of “10.” It’s a small thing, but it saves users (and me) a lot of head-scratching.

And yes, the final BMI result pops out like a helpful robot telling you how dense you are… in the kindest possible way.

Could I have just said, “Google your BMI”? Sure. But where’s the fun in that? Now I’ve got a custom-built BMI calculator that speaks both metric and imperial, politely handles mistakes, and makes me feel like an international coder of mystery.

Posted it on GitHub, naturally. Another green dot was added to the timeline. I still haven’t cleaned up the repository names, but hey—that’s a Day 30 problem.

Day 7: BMI balanced. Unit confusion conquered. Nerd pride: fully intact.

Optional Ideas for Expansion

  • Add age and gender inputs to adjust health ranges
  • Build a GUI version using Tkinter for a more visual experience
  • Allow saving BMI history to a text or CSV file for tracking progress

Day 6
Day 8

Posted on

I Build A Python Temperature Converter App

Day 6 of 100 Days Coding Challenge: Python

Let me tell you—one of the most confusing things about living in the United States isn’t the healthcare system or tipping culture. It’s Fahrenheit. That mysterious, overly enthusiastic temperature scale where 100 means “you’re baking alive” and 0 means… still not freezing?!

I was born and raised in Japan. Then I spent 30 years in North America—most of that in Canada, where people measure temperature in Celsius like civilized, snow-loving humans. But here in the U.S.? Fahrenheit reigns supreme, and I’ve been stuck doing mental gymnastics every time I check the weather.

So, today I thought, ‘Why not make an app?’ Sure, you could just Google “Celsius to Fahrenheit” like a regular, functional adult—but where’s the fun in that? So, today’s project is to build a Python temperature converter app. I wanted something mine. Something precise. Something that spells Fahrenheit for me, because let’s be honest—I still double-check it every time.

Today’s Motivation / Challenge

This wasn’t just about temperature—it was about taking control. Every time I squinted at a weather app and tried to remember the formula, I felt like I was failing a pop quiz I never signed up for. So, I built a tiny utility to stop the guessing and start converting with confidence. It’s practical, simple, and oddly satisfying. Plus, it’s one of those “you’ll use it more than you think” tools.

Purpose of the Code (Object)

The app asks which direction you want to convert—Celsius to Fahrenheit or the reverse—and then does the math for you. No need to remember formulas or worry about spelling Fahrenheit. It provides a clear answer, allowing you to dress appropriately, avoid weather-related drama, and continue with your day.

AI Prompt

Make a Python app that converts temperatures between Celsius and Fahrenheit. Let the user choose the direction (C to F or F to C), input a number, and get the converted result. Keep it clean, beginner-friendly, and fun to read. No extra libraries—just use basic input/output.

Functions & Features

  • Asks the user if they want to convert Celsius to Fahrenheit or Fahrenheit to Celsius
  • Accepts a numerical input for temperature
  • Calculates and displays the converted result, rounded nicely
  • Includes basic input validation

Requirements / Setup

  • Python 3 (no external libraries required)

Minimal Code Sample

temp = float(input(“Enter temperature: “))

converted = (temp * 9/5) + 32

print(f”{temp}°C is {converted:.2f}°F”)

This calculates and prints the Fahrenheit equivalent of a Celsius input.

Python temperature converter app

Notes / Lessons Learned

My husband had opinions. He pointed out that the app simply responds with one message—”Toasty!”—regardless of the temperature.

“Toasty?” he said, side-eyeing the screen. “It’s only 24°C today. That’s barely ‘light sweater’ weather.”

Okay, fair. I was feeling a bit lazy and didn’t add any if…else logic. No chilly messages, no heatwave warnings—just a one-size-fits-all toastiness. Technically, the app works, but let’s just say it’s emotionally flat.

One day I’ll give it some flair. Maybe it’ll say “Brrr!” when it’s cold, or “Oven-grade heat” when things get spicy. But for today? Toasty is my default setting—and this app is officially done.

Optional Ideas for Expansion

  • Add personality: change messages based on the temperature (e.g. “It’s sweater weather” or “Don’t forget sunscreen”)
  • Build a GUI with buttons for easier interaction
  • Let the user convert a whole list of numbers (batch conversion)

Day 5
Day 7

Posted on

Three Bags of Leaves and the Stubborn Tree That Won’t Quit

Brian’s fitness journal after a brain stroke

I scheduled today as an official Leaf Day. The morning was cool, but the forecast promised warmth later, which meant it was finally safe to commit to the mission. With determination (and mild dread), I headed outside to clear our lawn of fallen leaves.

Recent windy days had turned our trees into enthusiastic confetti machines. Naturally, every single leaf seemed to land in our front yard. We try to keep things tidy, but I skipped this chore on Tuesday—and leaves, like unread emails, multiply when ignored. Some of our neighbors let their yards turn into a brown carpet museum, but we live under the cheerful supervision of an HOA, where “neatly maintained” is not a suggestion but a lifestyle.

I confidently assumed this would be a one-bag job.

It was not.

One bag became two. Two became three. At that point, I began to question both my math skills and my life choices. I had cleared the yard just last week, so the sheer volume of leaves felt borderline disrespectful. It took a few solid hours to finish, but thankfully, it was still nowhere near the level of suffering known as summer lawn mowing.

Despite the surprise workload, the chore was strangely satisfying. With every pass of the leaf vacuum, the front yard visibly transformed from “abandoned forest floor” to “suburban responsibility.” After emptying the third bag, I finally stopped—mostly because my motivation had also reached full capacity. The yard looked noticeably neater, and I felt just proud enough to justify a future complaint about it.

For reasons known only to nature, the tree in our front yard still hasn’t finished shedding its leaves, while the neighbor’s tree is nearly bald. An arborist once told us our tree is weakened by its much larger neighbor and suggested we remove it. That suggestion was immediately vetoed by my wife, who has a deep sentimental attachment to trees.

A few years ago, we had to remove a massive tree behind our house because it was threatening the structure itself. It was so tall that owls used to visit it at night—often waking my wife around 2 a.m. with dramatic hooting. Even our kitten loved leaping from branch to branch. Cutting that tree was emotionally difficult, which is why the front-yard tree still stands today… heroically dropping leaves every autumn.

I powered through the task and completed it to my own satisfaction. Living at the bottom of a hill means we naturally collect more than our fair share of wind-blown leaves—especially near the storm gutter, which today was completely buried under a dense mat of leafy ambition.

Three bags. One stubborn tree. Zero regrets.
Well… maybe mild regret.
But the yard is clean.

Back
Next

Posted on

I Built My Own Python Birth Date Calculator App!

Day 5 of 100 Days Coding Challenge: Python

This is how I decided to create my own Python birth date calculator App. My husband, in his ever-charming, spreadsheet-souled way, has taken to sending his siblings bizarre messages like, “It’s been 3,472 days since your child was born!” No “Happy Birthday” or “Hope you’re doing well.” Just pure data. His love language is clearly math over mush. Where some people give hugs, he gives decimal points.

Naturally, I asked him, “How do you even know that?”
“Oh, I use this app,” he said, as if that explained everything. “It updates every day. Totally accurate.”

Hmm. I smelled a challenge. A numeric gauntlet had been thrown.
So today, I set out to make my own Python birth date calculator app—because if anyone’s going to calculate our niece’s lifespan with theatrical flair and a better font, it’s going to be me. Sorry, dear. It’s not personal. It’s Python.

Today’s Motivation / Challenge

Sometimes coding isn’t just about solving problems—it’s about proving a point. This project was part logic puzzle, part sibling scoreboard, part marital competition. I wanted to build something that turns a regular birthdate into a fun set of trivia: how many days, weeks, months, and even seconds someone has been alive. Because deep down, don’t we all want to feel like the star of our own oddly specific countdown clock?

Purpose of the Code (Object)

This app asks the user to enter a date of birth, and then calculates exactly how long it’s been—down to the day. It tells you how many days, weeks, months, and years have passed since that date, and even throws in the total number of seconds, just in case someone needs an existential crisis. It’s a surprisingly fun way to work with dates and time calculations in Python.

AI Prompt

Write a Python program that asks for a birthdate and calculates how many days, weeks, months, years, and seconds have passed since then. Format the results clearly for the user.

Functions & Features

  • Prompts the user to enter a birthdate
  • Calculates the total days, weeks, months, and years since that date
  • Displays the time passed in a readable summary
  • Bonus: includes total seconds alive for dramatic effect

Requirements / Setup

Python 3.10 or higher
No external libraries required


Minimal Code Sample

from datetime import datetime

birthdate = input("Enter your birthdate (YYYY-MM-DD): ")
b = datetime.strptime(birthdate, "%Y-%m-%d")
now = datetime.now()
delta = now - b
print("You’ve been alive for", delta.days, "days.")

This calculates the number of days since the user’s birthdate.

Python birth date calculator app

Notes / Lessons Learned

Birth Day App: created, posted, and ready to tell you how long you’ve been alive—whether you wanted to know or not. It’s oddly satisfying watching Python crunch your life into a tidy block of numbers.

And now for the grand finale:
I ran the app and checked how many days it had been since our niece was born. Then I compared it to my husband’s mysteriously accurate app.

Drumroll…

The numbers matched. Exactly.

So now I don’t know whether to shout, “Wow, my app actually works!” or mumble, “Okay, fine, my husband is right.”
Let’s call it a tie.
But mine has better UX. And color-coded text. So really… it’s a win.

Optional Ideas for Expansion

  • Add the ability to count down to future birthdays or anniversaries
  • Include fun facts like “You’ve lived through 6 leap years”
  • Add a time zone selector for dramatic international flair

Day 4
Day 6