Hello, it’s been a while since my last devlog but the FuzzBuzz Engine has been getting steady updates, so here is everything that changed.

Developments : Input Validation

Last time I said the script was highly vulnerable to unhandled inputs commas, empty enters, random letters, all of it caused instant crashes. That’s fixed now. Every number input is wrapped in a while True + try/except ValueError loop, so instead of the program dying it just tells you to enter an integer and asks again, forever, until cooperation. I also added range validation on the print limits, so you can’t tell it to start printing from a number that isn’t even in your range. The program refuses.

New: Data Visualization

The counter engine from last time was just sitting there, so I thought I would make use of it. At the end of the run the program prints an ASCII bar chart of how many times FuzzBuzz, Fuzz, Buzz, and regular numbers showed up, built out of █ characters right in the terminal (inspired by terminal UIs like the one for Claude Code). The bars are scaled so large ranges stay readable. Each bar’s width is normalized against the most frequent category:

bar_width = (count / max_count) × max_width

with max_width capped at 25 characters. The biggest category always gets the full bar and everything else is proportional to it.

New: Statistics Report

Below the chart there is now a stats report showing each category as a percentage of the total numbers processed, formatted to two decimal places and aligned into columns with f-strings.

Next Steps

Letting the user choose what numbers Fuzz and Buzz are multiples of (custom divisors instead of the hardcoded 3 and 5), giving the user control over whether the bar chart prints and its max width, and testing for remaining edge cases.

Well that’s all from me,
Kamil

Hello, I built FuzzBuzz which other than being a glorified LeetCode easy question with a goofy name is a dynamic loop engine that prompts the user to define their own number ranges and constraints right in the terminal, then runs a substitution loop over those numbers. Specifically, it loops through a set of numbers and prints:

• “Fuzz” for multiples of 3
• “Buzz” for multiples of 5
• “FuzzBuzz” for multiples of 15 (both 3 and 5)
• The regular number itself if it doesn’t match any of those rules

It also tracks the total occurrences of each word in the background as it runs.

Mathematical Model

Since this is intrinsically mathematical I thought It would be fun to model the formal logic behind the loop’s domain and mapping rules.

Let the domain be a finite set of integers S, bounded by user inputs a and b (equation 1 in attached latex image)

The string substitution follows a piecewise mapping function f(x) for each element in the set (equation 2 in attached latex image)

Features & Updates

Case Insensitivity: Used the ‘.lower()’ method on the text inputs so choices like “Yes”, “yEs”, or “YES” work fine without breaking the execution flow.

Edge Cases & Vulnerabilities

Right now, there are still a lot of ways to game the system. The script is highly vulnerable to unhandled inputs that cause instant crashes:

• Typing a comma in a number field.
• Hitting the enter key on an empty input.
• Typing letters where the program expects numerical ranges.

Next Steps

I plan to add proper input validation. Instead of crashing on these edge cases, the program will catch the bad input, block the crash, and return a clean prompt telling the user to enter the data properly.

Final notes

The latex image might not be perfect but at lest I tried my best 🥲but I digress

Well that’s all from me,
Kamil