The Stock Market Mood Ring

Day 62 of 100 Days Coding Challenge: Python

Yesterday, I taught my script how to look into the past—specifically, the last 30 days of each tracked stock’s closing prices. Today, we’re talking emotions—well, stock emotions. I added a function in Python to show each stock’s daily percentage change, color-coded like a moody person: green when it’s up, red when it’s down, and default when it’s flat.

Now, to be clear, I’m not a day trader glued to five monitors with live tickers whizzing by. I have a full-time job, thank you very much, and no one’s got time for that kind of circus. I check in weekly, adjust when needed, and focus on consistency over drama. Still, this function gives me a quick visual snapshot of how things are moving—and more importantly, how they might move. It’s like giving your portfolio a morning coffee and asking, “How are we feeling today?”

Patterns are the name of the game. If I can start spotting them, maybe one day I’ll teach this program to make some educated guesses—and eventually, add a bit of risk management to keep me from playing financial roulette. The next few days are all about adding the kind of analytical firepower that helps with smarter decisions down the road. And honestly? I’m kind of pumped.

Today’s Motivation / Challenge

You know that moment when you look at your bank account and squint, wondering, “What happened yesterday?” That’s what this feature is for. It’s like a digital mood chart for your stocks—without the therapy bills. Adding daily change percentages, especially in color, helps me scan for drama or calm in seconds. It’s a tiny step toward building a truly useful tool for hands-off investors like me, who want the intel without the stress.

Purpose of the Code (Object)

This code adds a quick visual check-in for each stock in my portfolio. It tells me whether a stock’s price went up or down today—and by how much—without needing a spreadsheet or third-party app. It’s lightweight, readable, and tailored to my investment rhythm.

AI Prompt (used to create today’s function):

“Please add the following function to the script.
Daily Change (%): Show today’s % change for each stock with green/red highlight.

Functions & Features

  • Calculates daily percent change for each stock.
  • Highlights gains in green and losses in red.
  • Leaves unchanged stocks in default color.
  • Makes my console look like it actually cares.

Requirements / Setup

pip install yfinance

Minimal Code Sample

if change_percent > 0:

    color = “\033[92m”  # Green

elif change_percent < 0:

    color = “\033[91m”  # Red

else:

    color = “\033[0m”   # Reset

This assigns a text color based on the day’s percent change in stock price.

Stock Tracker

Notes / Lessons Learned


I’m starting to feel like a feature-adding machine—well-oiled, slightly caffeinated, and surprisingly organized. Thanks to the roadmap I drafted early on, it’s easier to stack new functions like LEGO bricks (minus the foot pain).

Today, I learned how to add color using ANSI escape codes. Think of them as secret signals you whisper to your terminal to make it look fancier. So now, green means the stock had a good day, red means it might need a hug, and the reset command keeps the rest of the terminal from turning into Christmas.

What I love about this feature? It’s subtle but powerful. Visual clarity goes a long way when you don’t have time to deep dive. And hey—who knew the terminal had a flair for drama?

Optional Ideas for Expansion

  • Add arrows (↑/↓) next to the percent for more flair.
  • Let users set custom alert colors (purple for panic? Why not).
  • Create a summary line showing how many stocks gained vs. lost today.

Watching Your Stocks Like a Hawk (But With a Graph)

Day 61 of 100 Days Coding Challenge: Python

The last five days were all about laying the foundation—think of it as assembling IKEA furniture, but with Python and fewer Allen wrenches. I got the stock tracker’s bones in place, installing essentials like the yfinance library. Now, it’s time to dress it up and make it do something more alive—like track real stock movement over time.

I’m finally stepping into the exciting part: creating a portfolio visualization that doesn’t require squinting at 14 browser tabs.

We’re starting simple. One historical price chart per stock. No more, no less. Why? Because trying to cram five charts into one screen is like watching five soap operas at once—dramatic, confusing, and probably bad for your blood pressure.

Back in university, my finance professors swore by stock observation like it was a sacred rite. Watch the markets, they said. Understand the impact of events—unemployment numbers, interest rate announcements, or when Jerome Powell so much as blinks. These things shake the market, and now, thanks to a bit of Python magic, I can watch those ripples without hopping from one website to another.

Today’s Motivation / Challenge

Have you ever tried checking your stocks manually, one by one? It’s like chasing toddlers in different directions. Today’s goal: automate that madness. With a single function, I want to see the historical price trends of each stock in my portfolio—visually. Because numbers are fine, but a chart? A chart speaks volumes.

Purpose of the Code (Object)

This little script fetches and plots the past 30 days of closing prices for each stock in your portfolio. It doesn’t try to impress anyone with fancy calculations. It just shows you what your stock has been up to, in a nice, simple line graph—so you can stop opening 27 browser tabs.

AI Prompt

Add the function to plot past 30-day price history for a single stock

Functions & Features

  • Plots past 30-day price history for a single stock
  • Automatically fetches historical data from Yahoo Finance.
  • Easy to reuse for each stock in your portfolio

Requirements / Setup

pip install yfinance matplotlib

Minimal Code Sample

import yfinance as yf

import matplotlib.pyplot as plt

def plot_stock_history(ticker):

    stock = yf.Ticker(ticker)

    hist = stock.history(period=”30d”)

    hist[‘Close’].plot(title=f”{ticker} – Last 30 Days”)

    plt.xlabel(“Date”)

    plt.ylabel(“Price ($)”)

    plt.grid(True)

    plt.show()

→ Fetches and plots 30-day closing price for a given stock symbol.

Stock Tracker

Notes / Lessons Learned

To get this feature working, I first installed yfinance and matplotlib. Easy enough—until I noticed the pip version nagging me to update (again). I was on 25.1.1, and suddenly it wants 25.2. It’s like that one friend who insists on “just one more update” before going out.

This is the reality of programming: libraries get updated more often than your favorite streaming shows, and if you’re not careful, your working code might just throw a tantrum the next day. I used to roll my eyes when game servers went down for “maintenance.” Now I know—those devs were heroes.

Also, pro tip: stock movements don’t just come from earnings reports. Tariff announcements? Those hit hard. I saw a few of my stocks tumble right after one went into effect. Should’ve bought the dip… but hey, now I can at least see it happening, in style.

Optional Ideas for Expansion

  • Add a dropdown menu or an input box to select stock instead of typing it
  • Color-code gains vs losses on the chart
  • Combine charts into one interactive dashboard (when you’re feeling brave)

How to Simulate Weighted Stock Investments in Python

Day 60 of 100 Days Coding Challenge: Python

When it comes to investing, I tend to lean toward the systematic approach. I like a plan. Not a “buy high, panic low” kind of plan, but a “how can I make $100 go as far as possible without needing a spreadsheet and a prayer” plan. Many stocks—especially ETFs—allow fractional share purchases, which is a blessing for anyone whose investing budget is less Wall Street and more wallet lint. That’s the beauty of modern investing: even if you don’t have a mountain of capital, you can still climb the hill.

So today I asked myself, what if my program could simulate that for me? What if I could say, “Here’s my $100,” and the program could allocate it automatically? Then I thought: what if I want to invest 25% in TSLA and only 5% in that random biotech company I’m not sure I trust? That’s where the idea of weighted allocation came in. A little money invested consistently can become something big over time—and the code now knows how to treat your dollars like they matter. Because they do.

Today’s Motivation / Challenge

You’ve probably heard some version of the advice “invest consistently, even with small amounts.” But how do you split that $100 in a smart, intentional way? Today’s challenge was about helping the program act like a friendly robo-advisor. Instead of dividing your money equally, it now lets you decide how much each stock gets. More TSLA, less risk. Or more risk, less cash. Either way, it’s your call—and the math is on your side.

Purpose of the Code (Object)

This new feature lets you simulate how much stock you could buy with a specific amount of money based on custom weight percentages. You choose the amount to invest, set the allocation weights for each stock, and the script calculates how many shares you could get, what it would cost, and how much remains. It’s budgeting, but for your imaginary portfolio.

AI Prompt: 

Create a Python function that takes a total investment amount and a custom percentage for each stock, then calculates how many shares can be purchased and the cost per stock using yfinance.

Functions & Features

  • Add or remove stock symbols from your portfolio
  • View real-time prices of all tracked stocks
  • Simulate investment allocation based on equal weights
  • Simulate investment allocation based on custom weight percentages
  • Check the price of a specific stock
  • Exit the program (option 99)

Requirements / Setup

pip install yfinance

Works with Python 3.8+. Use a virtual environment for clean setup.

Minimal Code Sample

def simulate_weighted_allocation():

    total = float(input(“How much to invest? $”))

    for symbol in stocks:

        weight = float(input(f”{symbol} weight (%): “))

        allocated = (weight / 100) * total

        shares = allocated / get_price(symbol)

        print(f”{symbol}: {shares:.4f} shares for ${allocated:.2f}”)

Takes your total investment and simulates purchasing based on custom weights.

Stock Tracker App

Notes / Lessons Learned

Initially, my simulation just split the money evenly—simple and safe. With 13 stocks in my portfolio, that reminded me of those index funds that allocate 1% to everything, like some kind of financial democracy. And while that’s a solid strategy (Vanguard would approve), I wanted control. I wanted to give TSLA a bigger slice of my $100 pie. So I added a custom weight input. Now the script lets me play mini portfolio manager.

One catch: if your percentages don’t add up to exactly 100, the program will throw a gentle tantrum. So you do have to plan ahead and know what you’re allocating. Otherwise, it’s like hosting a potluck and forgetting who brings dessert—awkward and disappointing. Still, once it worked, I thought: This is cool. It’s like mock investing with real math—and zero risk.

Optional Ideas for Expansion

  • Save your weight presets for recurring investment styles
  • Add error handling to automatically rebalance weights to 100%
  • Display a pie chart of your allocation with matplotlib

This marks the point where the stock tracker grows from a utility to a personal investing playground. And we’re only 60 days in.

The Price is Modular: Breaking Up is Clean to Do

Day 59 of 100 Days Coding Challenge: Python

Yesterday, I caught myself on the edge of a rookie mistake: copying the same chunk of “fetch price” code into every place that needed it. It was like déjà vu with worse indentation. So I took a breath, cleaned it up, and extracted that logic into a shiny, single-purpose function: get_price(). Now, anytime I need the current price of a stock, I just call one clean little line. And if I ever want to swap out Yahoo Finance for Alpha Vantage—or carrier pigeons, who knows—I only have to update it in one place.

Unlike my previous project (the slightly chaotic book tracker that looked like it was written in a storm), this time I’ve actually thought about structure. I outlined a rough roadmap and started slicing features into small, logical pieces. Turns out, coding for your future self is a real kindness. It’s already making the script easier to manage, and I haven’t even spilled coffee on it yet.

I also added an extra feature that turned out to be more useful than expected: the ability to check the current price of a single stock on demand. It’s perfect for those moments when I randomly wonder, “How’s TSLA doing today?” or “Is MSFT still climbing?” Now I don’t have to scroll through my entire portfolio—I just type, fetch, and boom. Market curiosity satisfied.

Today’s Motivation / Challenge

 This project is starting to feel like a real tool, not just a list of stock symbols collecting digital dust. But with functionality growing, it was time to tidy up the code before it turned into a spaghetti bowl. By modularizing the price-fetching logic, I gave myself room to grow—because adding new features is so much easier when your code isn’t held together with duct tape and denial.

Purpose of the Code (Object)
 

The script now includes a reusable function, get_price(), that handles all price-fetching tasks. It simplifies the process of displaying current prices and opens the door to adding new features without clutter. I also added a quick price-check tool for any stock—not just ones in your portfolio.

AI Prompt: 

Refactor price-fetching logic into a reusable Python function using yfinance. Add an option to check the real-time price of any single stock.

Functions & Features

  • Add or remove stock symbols
  • View your portfolio with current prices
  • Fetch real-time price for any single stock
  • Show stock symbol list
  • Exit the program (option 99, always last)

Requirements / Setup

pip install yfinance

Python 3.8+ recommended. Use a virtual environment if possible for clean installs.

Minimal Code Sample

python

CopyEdit

def get_price(symbol):

    ticker = yf.Ticker(symbol)

    return ticker.info.get(“regularMarketPrice”)

A reusable function to get the latest market price for a stock symbol.

Stock Tracker

Notes / Lessons Learned
 

The key to keeping a growing script from turning into chaos? Organization. Even with AI in your corner, you still need to think ahead. During my book tracker project, I just tacked on features as they came to mind—resulting in a menu that looked like a word jumble and an exit function mysteriously wedged in the middle of everything.

This time, it’s different. Each function has a purpose, and I’m building with intention. Adding the “check a specific stock” feature was fast and satisfying. I tested it with TSLA and MSFT—worked like a charm. It’s amazing what a little structure (and a lot less clutter) can do.

Optional Ideas for Expansion

  • Add error handling for invalid or misspelled stock symbols
  • Include the timestamp of last price update
  • Build a search history so you can revisit recently checked stocks

This project is starting to feel less like a toy and more like a tool. Clean code, clear menus, and real data—what’s not to love?

Now Showing: The Price is (Almost) Right

Day 58 of 100 Days Coding Challenge: Python

Today, I finally unlocked the magic of seeing live stock prices for the companies I’ve been tracking. I activated the virtual environment I had so carefully crafted for this project—like slipping into a freshly pressed lab coat—and copied my previous file to create the next version. This has become my ritual. I don’t trust myself enough to overwrite yesterday’s work. I’ve learned the hard way: one misstep, and suddenly you’re debugging into the void at midnight.

But this time, everything felt smoother. More methodical. Like my stock tracker finally got itself a LinkedIn profile and a morning routine. I added the new function and, for the first time, watched real prices pop up for the stocks I entered. It was like watching your kid take their first steps… except your kid is Apple and it’s walking straight into your fantasy portfolio.

Today’s Motivation / Challenge


Sure, it’s fun to say you’re tracking stocks—but it’s even better to see what they’re actually worth. Today’s goal was to bring those tickers to life with live price data. It’s like turning a guest list into a party: you know who’s there, but now you see what they’re wearing. A clean interface that pulls prices makes the tracker feel real—and a lot more useful than a plain list of letters.

Purpose of the Code (Object)


This update adds a function that displays all currently tracked stocks alongside their latest prices pulled from Yahoo Finance. It keeps things simple and readable, so users can check their “portfolio” at a glance without needing to log into a brokerage or scroll through a financial website.

AI Prompt:

Add a function to a Python script that displays all stock symbols in a list along with their current market prices using the yfinance library.

Functions & Features

  • Add stock symbols
  • Remove stock symbols
  • Show tracked symbols
  • View current stock prices
  • Exit the program (option 99, always last)

Requirements / Setup

pip install yfinance

You’ll also need Python 3.8+ and a virtual environment (optional but recommended).

Minimal Code Sample

import yfinance as yf

def view_portfolio():

    for symbol in load_stocks():

        price = yf.Ticker(symbol).info.get(‘regularMarketPrice’)

        print(f”{symbol}: ${price:.2f}” if price else f”{symbol}: Price unavailable”)

Fetches and displays each stock’s latest price using Yahoo Finance.

Stock Tracker

Notes / Lessons Learned


For this feature, I added the yfinance library and made sure to import it up top with the rest of the code crew. I also handled the situation where your portfolio might be empty—no one likes being told they have nothing, but it’s better than a crash. Thankfully, all the stocks I added yesterday were valid, so prices rolled in smoothly like a stock market ticker parade.

The function pulls from regularMarketPrice, which seems to be the most consistent for daily price checks. There were no errors, no false alarms, and no imaginary companies to spoil the moment. Just sweet, sweet confirmation that this tracker is starting to walk, maybe even jog.

Optional Ideas for Expansion

  • Show daily percentage change or price movement alongside current price
  • Highlight gains and losses in green/red
  • Let users refresh prices without restarting the script

Day 58 marks the moment this project stopped being theoretical. It’s starting to feel real—and I’m here for it.

Name It and Claim It: Deleting Stocks and Wrestling Filenames

Day 57 of 100 Days Coding Challenge: Python

Yesterday, I made a small typo when entering a stock symbol—just one little slip of the keyboard, and suddenly I’m the proud owner of a fictional stock ticker. Unfortunately, the program didn’t come with an “oops” button, so today’s goal was obvious: build a function that lets me delete stock symbols from my list before my portfolio starts sounding like a toddler named it.

While I was at it, I got curious about filenames. You see, in the past, I’ve gone a bit wild with my naming convention—stuff like Book_Tracker_v2.py, final_final_please_work.py, or the classic version3_newest_final_backup2.py. This time, I wanted to test a more polished approach. I tried naming my file stock_tracker v1.1.py, thinking it looked quite professional. Spoiler alert: Python did not agree. Turns out, spaces in filenames are like pineapple on pizza—technically possible, but likely to cause arguments and strange behavior. Thankfully, stock_tracker_v1.1.py worked like a charm. I even read online that while dashes (-) are allowed, underscores (_) are generally the safer bet, especially if you want to avoid those sneaky bugs that only show up on Tuesdays after coffee.

Today’s Motivation / Challenge

Stock lists, like closets, need regular cleaning. If you accidentally track “TSLAA” instead of “TSLA,” your code won’t yell at you—but your future self will. Today’s challenge was all about giving the user (ahem, me) the power to tidy up their tracked stocks without digging through JSON files manually. It’s about building habits—and menus—that you can live with.

Purpose of the Code (Object)

This code lets you remove any stock symbol you’ve previously added. You just type the ticker you no longer want, and poof—it’s gone from the list. No editing files, no drama. The script also includes the option to view your list or exit gracefully (with a nod of thanks).

AI Prompt:

Write a Python program that allows users to delete a stock symbol from a JSON-based watchlist. The program should prevent duplicates, validate user input, and display a clean menu.

Functions & Features

  • Add new stock symbols to your list
  • View all currently tracked stocks
  • Remove a stock symbol by name
  • Quit the program (option 99, always last)

Requirements / Setup

Python 3.8 or higher

No additional libraries are needed. If you’re starting from scratch, create a virtual environment:

python -m venv venv

source venv/bin/activate  # macOS/Linux

venv\Scripts\activate     # Windows

Minimal Code Sample

def remove_stock(symbol):

    symbol = symbol.upper()

    stocks = load_stocks()

    if symbol in stocks:

        stocks.remove(symbol)

        save_stocks(stocks)

Removes a stock from your tracked list if it exists.

Stock Tracker

Notes / Lessons Learned

The trusty “Exit” option is still holding strong at number 99—right where it belongs. Tucking it at the bottom of the menu means no more accidental goodbyes when all I meant to do was clean up a typo. It’s like the emergency exit: always there, but hopefully not pressed by mistake.

Now, about filenames. I had this grand idea to name my script stock_tracker v1.1.py—you know, a classy versioning system worthy of a Silicon Valley pitch deck. Python, however, wasn’t impressed. Turns out, putting spaces in filenames is a little like trying to run a sprint in flip-flops. Technically doable. Practically… a terrible idea. After a few errors and some Googling, I landed on stock_tracker_v1_1.py, which behaved much better. Pro tip: underscores are your friends, hyphens are moody, and spaces are just asking for trouble.

Oh, and that rogue stock symbol I entered yesterday? Gone. Deleted. Justice served.

Optional Ideas for Expansion

  • Confirm before deleting a stock (a simple “Are you sure?” prompt)
  • Add auto-complete for stock symbols already in the list
  • Show a “last modified” timestamp next to each symbol

Stocks, Aristotle, and Other Risky Investments

Day 56 of 100 Days Coding Challenge: Python

Introduction to DIY Portfolio: A Python-Powered Stock Tracker (Day 56-Day75)

I’ve always had a curious relationship with investing. Back in my early twenties—just when online trading was beginning to sparkle with possibility—E*TRADE was running flashy stock-simulation competitions. I never had the nerve to join in, but the idea of tracking trades fascinated me. While others were glued to leaderboards, I was quietly watching market psychology unfold.

In one of my marketing classes, we studied consumer behavior, and I couldn’t help noticing the parallel. Stocks, like shoppers, are swayed by emotion. A bad headline sparks panic selling; a glowing report sends buyers rushing in. It was less about the spreadsheets and more about human nature in motion.

That said, I am no day trader. With a full-time job, I simply don’t have the bandwidth—or appetite—to chase tickers every second. Early on, I learned the hard truth: betting heavily on a single stock feels thrilling right up until it doesn’t. So I shifted to a disciplined rhythm. First, parking cash in money markets weekly, then funneling it into chosen investments. Eventually, I swapped most individual stocks for ETFs, which let me hedge my bets without needing caffeine-fueled midnight monitoring.

This is where my stock tracker comes in. It isn’t just a neat dashboard—it’s a sanity check. How much should live in bonds? How much in equities? The tracker keeps me honest, reminding me that a balanced pie chart beats chasing shiny objects.

Unlike my earlier Book Tracker project—where I bolted on features haphazardly and ended up cleaning a digital junk drawer—this time I built with a vision. The bigger the project, the less forgiving chaos becomes. Structure first, spaghetti later (preferably with marinara, not code).

What surprised me most was not the tracker itself but the realization of just how powerful Python can be. With a few libraries and some determination, I had built something that, in the past, I would have had to pay for—except now it’s tailored exactly to me. A personalized financial sidekick, minus the subscription fee.

Experience

Today marks the thrilling kickoff of a brand-new project: a stock tracking system. That’s right—I’m building a little Wall Street in my terminal. This time, I’ve sworn an oath to the ghost of Aristotle not to wing it. Last time, when I built a book tracker, I skipped the whole “final cause” thing—you know, the actual goal—and ended up redesigning everything from the menu to the data structure while muttering like a sleep-deprived philosopher. It was less “Eureka!” and more “Why did I do this to myself?” But not today. Today, I have a plan. A real roadmap. With arrows and everything. Step one? Get a stock symbol into the system without accidentally starting a recession.

Today’s Motivation / Challenge

We all want to be savvy investors, right? Or at least know what “diversification” means without Googling it every week. Today’s project is the first brick in a 20-day tower of financial wisdom—well, mock financial wisdom. We’re not handling real money here (unless you count emotional investment). The goal is simple: give users a way to start tracking the stocks they care about. It’s the tech equivalent of sticking Post-its on your fridge, but smarter—and less sticky.

Purpose of the Code (Object)

This tiny program lets you add stock symbols you want to track. It stores them in a JSON file so you don’t lose them the moment you close the terminal. It also shows you your current list, so you can admire how financially responsible you look. No actual money involved—yet.

AI Prompt:

Write a Python program that allows users to input and store multiple stock symbols, display them, and save the list in a JSON file. Make it beginner-friendly.

Functions & Features

  • Add a stock symbol to your personal watchlist
  • Display your current stock list
  • Save everything to a JSON file for future sessions
  • Quit the program using a menu option (helpfully numbered 99)

Requirements / Setup

Python 3.8 or higher

No external libraries required (yet). If you’re starting fresh, set up a virtual environment like this:

python -m venv venv

source venv/bin/activate  # On macOS/Linux

venv\Scripts\activate     # On Windows

Minimal Code Sample

def add_stock(symbol):

    symbol = symbol.upper()

    stocks = load_stocks()

    if symbol not in stocks:

        stocks.append(symbol)

        save_stocks(stocks)

Adds a new stock symbol to the list and saves it—simple, clean, effective.

Stock Tracker

Notes / Lessons Learned

I meant to start this two or three weeks ago, but I blinked and suddenly forgot how to create a virtual environment. My brain filed it somewhere between “how to fold a fitted sheet” and “useful Latin phrases.” After some desperate Googling, I finally got it working and documented it—this time for real. No more fumbling with pip and hoping for the best.

Since I want my little tracker to actually remember the stocks I add, I set it up to save everything in a JSON file. I also made the menu option to quit the program number 99. Why? Because it looks dramatic, and it guarantees it’ll always show up at the end of the menu. Will this strategy work? Unclear. Will I pretend I did it on purpose even if it doesn’t? Absolutely.

I enthusiastically added all the stock tickers I wanted to follow… and of course, I immediately typed one in wrong. Which means tomorrow’s task is obvious: build a delete function so I can pretend that the mistake never happened.

Optional Ideas for Expansion

  • Let users add a nickname or note next to each stock (e.g., “my retirement bet”)
  • Validate stock symbols against a real financial API to catch typos early
  • Add timestamps to track when each stock was added

How I Made My Python Book Tracker Fully Customizable

Day 55 of 100 Days Coding Challenge: Python

Once upon a time—okay, a few days ago—I had my genre-color pairings carved in digital stone. Tucked inside a function like a squirrel’s hoard of acorns, the genres and their matching hues were hard-coded, like:

“Historical Fiction”: “sienna”,

“Fiction”: “gray”,

“Memoir”: “lightcoral”,

You get the idea.

Back then, it felt efficient. But let’s be honest: it was as user-friendly as a brick in a gift box. So I set out to give my humble book tracker a glow-up. I added functionality to let users add their own genres, pick colors from a GUI color chooser, save them in a JSON file, and even reorder or delete genres if needed. No more pre-determined palettes—now users can start with a clean slate.

With all those new powers in place, it became clear: the old load_genre_colors() hardcoded fallback was now the fossil in the room. So I yanked it out and simplified the codebase. And just to test it, I cleared out most of my book log entries too—leaving only a lean trio: Fantasy, Science Fiction, and Romance. The result? A slicker, cleaner, beginner-friendly tool. And no more assumptions about people loving “lightcoral.”

Today’s Motivation / Challenge

Today’s challenge was about trust. Not between people—but between me and my code. I wanted to trust my users enough to let them decide what genres they care about and what colors they want. The control panel is theirs now. My job? Just to make sure the wires behind the scenes don’t catch fire.

This was also a step toward user-friendliness. The kind that makes someone say, “Hey, I could actually use this!” rather than “What on earth is ‘slateblue’?”

Purpose of the Code (Object)

This program is a customizable book tracker. It lets users log what they read, track their reading progress over time, and visualize it through colorful charts. It also gives them complete control over how genres are defined and displayed—no default lists, no assumptions.

AI Prompt:

“Can I remove the hardcoded genre-color mapping and just let the user build their own?”

Yes. And I did.

Functions & Features

  • Add, edit, or delete book entries
  • Define custom genres and pick colors for each
  • Save genre-color preferences in a JSON file
  • View genre breakdowns via pie or bar charts
  • Reorder genre list and edit mappings interactively

Requirements / Setup

Install the essentials:

pip install pandas matplotlib

If using the color picker:

pip install tk

Tested with Python 3.10+

Minimal Code Sample

genre_color_dict = {

    ‘Fantasy’: ‘purple’,

    ‘Science Fiction’: ‘blue’,

    ‘Romance’: ‘red’

}

This is where your genre-color story begins—users can expand it from here.

Book Tracker App

Notes / Lessons Learned

Actually, for the first time in this series, I wrestled with my own AI prompt. You see, the chat history had gotten so long (we’ve been working on this file for over two weeks) that when I asked to “remove the hardcoded section,” it started offering way too much interpretation—like a method actor who wouldn’t stop improvising.

Eventually, I had to open a fresh chat in the same project folder and restate everything clearly. That’s when it hit me: AI is powerful, but not psychic. It only knows what you tell it. If you’re not precise with your wording, it’ll do what it thinks you mean, not what you actually mean.

Just like coding, AI prompting is a language of its own. Respect it. Be clear. And maybe don’t expect it to read your mind… yet.

Optional Ideas for Expansion

  • Add a “preview” button to visualize the genre-color palette before saving it
  • Let users export their reading stats as an image or PDF report
  • Build a tag system so one book can belong to multiple genres (for the indecisive types)

Let’s be honest, even Tolkien would’ve struggled choosing between “Fantasy” and “Adventure.”

Taming the Menu Beast: When Order Matters More Than Code

Day 54 of 100 Days Coding Challenge: Python

I’ve been dancing with this project for over two weeks now. And you know what? When your project involves books—the thing you’re borderline obsessed with—you start fussing over the little things. Like menus. Yes, menus.

Today was the day I finally tackled something that had been silently bothering me: the out-of-whack order of the main menu. I had “Exit” sitting at #7 like it owned the place, while other features awkwardly piled up from 8 to 12. Not exactly elegant. So I did what any self-respecting, slightly neurotic book tracker would do—I cleaned house.

I reorganized the main menu to follow a more logical and satisfying sequence. Something clean, orderly, and sometimes won’t drive future-me (or any poor GitHub visitor) up the wall.

Here’s the new lineup, alphabet soup no more:

  1. Add a book
  2. Edit or delete a book
  3. Show all books
  4. Import from CSV
  5. Show overall reading graph
  6. Show genre summary chart (Pie or Bar)
  7. Show filtered chart by year and quarter
  8. Show average pages per genre per quarter
  9. Add a new genre and color
  10. Rename or delete a genre
  11. Reorder genre list manually
  12. Exit

Take that, chaos.

Today’s Motivation / Challenge

The real motivation? Sanity—and a sprinkle of future-proofing. I want to post this project on GitHub when it’s done, and I figured any stranger poking around deserves a user-friendly menu. Think of it like alphabetizing your spice rack: not necessary, but undeniably satisfying.

Also, adding new functions is becoming easier. Which means cleaning up after myself is now the least I can do.

Purpose of the Code (Object)

This script tracks the books you’ve read and turns them into beautiful visual summaries. From adding titles to generating colorful graphs, it’s designed to help readers stay organized, reflect on their reading habits, and play with genre data like it’s LEGO.

Today’s focus? Making the main menu feel like a polished app, not a last-minute potluck.

AI Prompt:

“Reorder the menu options and update the corresponding elif statements so the user sees a more intuitive and logically grouped main menu.”

Functions & Features

  • Add, edit, or delete book entries
  • Import a list of books from a CSV
  • Display all books in a clean format
  • Visualize reading progress with graphs
  • Analyze reading trends by genre and quarter
  • Manage genres with custom colors and order

Requirements / Setup

pip install matplotlib

pip install pandas

tkinter (comes pre-installed with Python)

Tested with Python 3.10+

Minimal Code Sample

print(“12. Exit”)

elif choice == “12”:

    print(“Goodbye!”)

    break

Just update the number and make sure the function still points to the right feature. Think of it like updating the index in your table of contents—crucial if you don’t want your reader flipping to the wrong page.

Book Tracker

Notes / Lessons Learned

Basically, what you need to do is reassign the menu numbers in the order you want. Then, carefully adjust each elif block to reflect the new structure.

I had:

elif choice == “7”:

    print(“Goodbye!”)

    break

Now I want:

elif choice == “12”:

    print(“Goodbye!”)

    break

The actual task wasn’t hard. The challenge was not falling into a logic trap—accidentally assigning two features to the same number or skipping one entirely. I highly recommend using AI or a numbered to-do list when reordering more than a few options. Saves brain cells.

It’s funny how a simple reorder can make the whole project feel more finished, more elegant—even if no code logic changes at all.

Optional Ideas for Expansion

  • Let users “star” favorite genres for quick filtering
  • Add keyboard shortcuts for power users
  • Enable saving custom menu layouts as presets

Graphing My Way Through the Library

Day 52 of 100 Days Coding Challenge: Python

You know you’ve reached a new level of coding attachment when you start treating your genre list like a prized bonsai tree—snipping here, trimming there, fussing over every little branch of logic. After revamping the program so it could accept new genres and pretty colors via a palette (very fancy, I know), I realized there was no graceful way to unmake a genre. What if I added “Historicl Fiction” by mistake? What if I picked a color so hideous that even my pie chart looked like it wanted to gag?
Today was all about giving myself the power to fix those flubs. Rename it, delete it, clean up my genre garden—snip snip! Because frankly, if I don’t like the color, the genre might just have to go.

Today’s Motivation / Challenge

Every great coder hits that moment where they scream at the screen, “Why can I add but not delete?!” It’s like buying furniture without knowing how to return it. I wanted my program to feel flexible, like a well-organized closet—not a hoarder’s storage unit of genre typos and duplicate categories. And let’s be honest, sometimes “Fantasy” and “Science Fiction” are just playing dress-up in each other’s clothes. Merge, rename, delete, repeat.

Purpose of the Code (Object)

This update lets users do a little genre housekeeping. You can now clean up your list by renaming genres (in case of typos or re-categorizing) or deleting them completely. It helps keep your visualizations tidy and your data organized—without diving into the JSON file manually. Think of it like giving your genre system a tiny admin panel without the drama.

AI Prompt:


Add a feature to let users rename or delete genres from the saved genre-color dictionary and persist it using JSON.

Functions & Features

Add a new genre and assign it a color using a color picker
Save all genres and colors to a JSON file automatically
Rename existing genres in case of typos or reclassification
Delete genres that are no longer wanted
Keep your pie charts and reports squeaky clean

Requirements / Setup

Install required library: pip install matplotlib pandas
Python 3.9 or later recommended for date handling and plotting.
No external JSON library needed—just the built-in json and os modules
tkinter (comes with Python standard library)

Minimal Code Sample

def rename_or_delete_genre(genre_color_dict):
print(“\nCurrent Genres:”)
for genre in genre_color_dict:
print(f”- {genre}”)

choice = input("\nRename or Delete? (r/d): ").strip().lower()
if choice == 'r':
    old = input("Old genre name: ")
    new = input("New genre name: ")
    if old in genre_color_dict:
        genre_color_dict[new] = genre_color_dict.pop(old)
        print(f"Renamed '{old}' to '{new}'.")
    else:
        print("Genre not found.")
elif choice == 'd':
    target = input("Genre to delete: ")
    if target in genre_color_dict:
        del genre_color_dict[target]
        print(f"Deleted '{target}'.")
    else:
        print("Genre not found.")
save_genre_colors(genre_color_dict)

This snippet shows how to let users clean up the genre-color dictionary and save the changes.

Book Tracker

Notes / Lessons Learned

This might sound like a small tweak, but it was a surgical upgrade. I tested, tweaked, and made backup copies like I was preparing to launch a space probe, not a genre menu. And wow—what a difference it made. Now if I want to merge “Thriller” into “Mystery,” I don’t need to panic about breaking anything.
It also got me thinking about naming in general. Genres are a bit like moods—they shift. So it helps to keep things tidy and editable. Pro tip? Rename before deleting, just in case you regret it five seconds later.
Also, I’m now officially annoyed that my function menu jumps from 7 to 11. Time to refactor. Naming may be hard, but numbering is… even harder?

Optional Ideas for Expansion

  • Add a feature to merge two genres into one, including updating past entries
  • Include a log file that records changes to genres for version control
  • Let users reorder the genre list manually so the menu stays tidy and satisfying