Max Perrin

• LinkedIn
• GitHub
• Discord

• Past work examples (Outdated)

• Back To Home

Reflection

Lessons learned:
I learned that estimates only work if your assumptions are clear, and the flowchart helped me keep the steps organized and catch mistakes.What I like:
It shows my thinking in a simple, visual way and someone else could follow it or reuse it with a different jet price.What I’d change:
I’d include a price range (low/medium/high) instead of one numberHow it helps me in the future:
It builds my skills for breaking down big problems, doing conversions carefully, and explaining my process clearly.

reflection

Lessons learned:
I learned how important planning is in Twine variables, conditions, and link structure matter a lot, and small logic mistakes can break the story flow.What I like:
I like the theme/atmosphere and how the choices make the story feel interactive. I’m happy that the player’s decisions actually affect what happens next.What I’d change:
I’d tighten the branching so it’s less confusing, add more consequences for choices, and do more playtesting to catch dead ends/grammar issues.How it helps me in the future:
This will help me with writing interactive stories, organizing complex logic, and building projects that need both creativity and debugging.

reflection

Lessons learned:
I learned how to turn a bunch of research into a few clear headline, and that layout/spacing matters as much as the information.What I like:
I like that the sections feel organized and easy to scan.What I’d change:
I’d tighten a couple of the stats with clearer context and make the sources match each stat more directly. I’d also adjust the bottom text so it’s a little shorter.How it helps me in the future:
This helps me practice research, summarizing, and visual communication.

reflection

Lessons learned:
I learned how important unit conversions and assumptions are. The biggest thing was realizing “perfect packing” isn’t realistic, so adding a packing efficiency made the estimate way more believable.What I like:
I like that it’s structured step by step and has a real comparison to an actual jetWhat I’d change:
I’d explain the packing efficiency choice a little more why 60% and what it represents, and more like comparing the weight of that many quarters to what a room/floor could physically hold.How this helps me in the future:
This helps me practice breaking down a real world question into math steps, supporting claims with sources, and communicating results clearly instead of just giving a number.

• Binary Game

reflection

Lessons Learned:
I learned how critical progressive difficulty is for keeping learners engaged without overwhelming them. The biggest thing was realizing immediate feedback matters more than I thoughtWhat I Like:
I like that it combines visual learning (toggling bits) with hands-on practice and has built-in hints that don't give away the answer immediately.What I'd Change:
I'd add sound effects for better feedback, make the bit toggles larger for mobile users, and include more game modesHow This Helps Me in the Future:
This helps me practice translating complex technical concepts into interactive experiences, using design psychology to motivate users, and building educational tools to help people.

• Budget Buddy (Python Project)

reflection

Lessons Learned:
I learned how important input validation and data organization are when building a menu-based program. The biggest thing was realizing that saving/loading data reliably (CSV/JSON) matters more than I thought..What I Like:
I like that Budget Buddy feels like a real, usable tool. The menu flow is straightforward, it supports adding/editing/deleting transactions, and exporting a report makes it feel complete instead of just a basic assignment.What I’d Change:
I’d improve the UI prompts to be cleaner and faster to use, add clearer error messages, and upgrade the reportsHow This Helps Me in the Future:
This helps me practice building larger programs with multiple features, managing persistent data

• MFA Sim (python project)

reflection

Lessons Learned:
I learned how useful randomness + lists are for simulating real security workflows. The biggest thing was realizing how important validation is.
What I Like:
I like that its easy to understand: it generates 10 backup codes, shows them, then simulates using one and removing it. Using a seed also makes the simulation repeatable, which is great for testing and grading.What I’d Change:
I’d prevent duplicate codes (so every backup code is unique), add input handling so non-integer entries don’t crash the program.How This Helps Me in the Future:
This helps me practice building small security related simulations, working with randomness and managing state with lists

reflection

Lessons Learned:
I learned how much planning it takes to turn a game idea into a working systemWhat I Like:
I like that FarmBlock is original and clearly different from “normal” gamemodes like OneBlock. I’m proud that it’s fully custom and coded in JavaWhat I’d Change:
I’d improve onboarding for new players (tutorial, clearer UI/menus), add more progression content (more upgrades/milestones)How This Helps Me in the Future:
This helps me practice real software development skills: designing systems from scratch, implementing them in Java, debugging complex behavior, and iterating based on player experiencefull src will not be provided for obvious reasons

• Back To Home