Days 91-96 | #100DaysOfCode More React practice with two games. tenzies-qqhy.onrender.com programming-language-hangman.onrender.com Try em out and lemme know what you think!

Days 90 | #100DaysOfCode Took a little break because of sick but I'm back at it again. - Coding challenge - More React practice, coding up a little game called Tenzies.

Days 85-89 | #100DaysOfCode Made an AI chef that gives you back a recipe after you tell it what ingredients you have on hand! Then I added a backend to protect my API key. Currently trying to figure out how to deploy it on render.

Days 81-84 | #100DaysOfCode - More React practice - Codewars

Day 79/80 | #100DaysOfCode - Code wars - Working my way through Scrimba React tutorial, created a static page.

Day 77/78 | #100DaysOfCode - Added week2week functionality in the form of: deleting old shifts / vaca / sick and creating new recurring shifts. - Minor cosmetic fixes (8.00 -> 8.0), and organizing my code. - Unified sick/vaca, one form, two buttons. Way more efficient than 2 forms/add functions.

Day 72-75 | #100DaysOfCode - Misc bug fixing - Refactoring code FINALLY to make use of the many schema changes I've made over the past two weeks. This ended up simplifying a lot of logic. Instead of doing convoluted time/date calcs, now I compare one schema field === another schema field.

Day 70&71 | #100DaysOfCode Because of the schema changes made yesterday, a bunch of things broke. Spent a bit debugging and changing things around. Something like vaca.map(d => //) becomes vaca.map(d.date => //). Just tedious really. Added blackout date functionality, time when nobody gets charged!

Day 68 & 69 | #100DaysOfCode Implemented Sick Time + refactored code so sick+vaca can be partial shifts. In the process added guardrails to prevent unintended behavior. For example, vaca checks if monitor is working that day, if they aren't then it skips. Also added snazzy hide/show buttons!

Day 66 & 67 | #100DaysOfCode - Coding Challenges - Doing a bit of thinking for once before moving forward, prepping how I'm going to implement these next functions into my app. Hopefully this saves me the headache and frustration of diving into things headfirst 😵‍💫

Day 65 | #100DaysOfCode - Built out week to week implementation finally. Now there's a way to update the DB between weeks, as well as adding post-week corrections. - Confirm box for large DB changing buttons. - Started on Alerts yday, didn't work. Did nothing. Now it works. 🤷‍♂️

Day 64 | #100DaysOfCode Starting on the scaffolding of updating the DB from week to week. - Implemented downloading/uploading mongoDB documents - Added a post-week correction page. The logic is complex and I can't cover every situation.

Day 62-63 | #100DaysOfCode I feel so slow at writing code sometimes. After wrestling with date objects (MY MORTAL NEMESIS) yet again I am happy to report that I've finished the first of my changes; hours are charged based upon the shortest shift possible and consider shift overlap.

Day 59-61 | #100DaysOfCode Styling improvements (navbar resizes to the content below!), refactoring and bug fixes. Additionally, I initially had some requirements for overtime hour charging incorrect. Redoing that is taking longer than expected. May or may not have forgor my own code 😅

Day 57&58 | #100DaysOfCode Nearing the end of my project... Two new HTML pages added! One is a quick tutorial meant to inform the user exactly how to use the webpage and the second is meant to be printed out. Now I just gotta figure out how to force each section to resize to fit on one page...

Day 56 | #100DaysOfCode Before you are two almost identical snippets of code. One will work while the other crashes and throws an error at you. Which is which?!? Today I learned all about brackets and how they require semi-colons for the parser to recognize. It only took like an hour of googling 😭😭

Day 55 | #100DaysOfCode Debugging Holidays today, specifically auto-creating overtime shifts on each holiday. Fixed one bug but another popped up!

Day 54 | #100DaysOfCode Coding challenges and figuring out the next steps for my app =]

Day 53 | #100DaysOfCode Realized what I was doing wrong yday - wasn't dates or booleans.I was adding the wrong two variables together (was adding 'later' instead of 'early')🤦‍♂️ Talk about tunnel visioning 😭 On the brightside, I know the rest of my code is rock solid!

I scored 10/28 on jsdate.wtf and all I got was this lousy text to share on social media.

Day 52 | #100DaysOfCode - Implemented new check for audit log, monitors no longer charged if they also bid on that overtime shift - Monitors can no longer work three shifts in a row - Lots of misc bug fixed, still have more. T_T - Confusing myself with booleans, one of my audit checks !works

Day 51 | #100DaysOfCode Working on implementing 'hour charging' to account for previous bids. Have a new variable to store history of 'passed over' bids, however I got sidetracked by another bug w/r/t assigning OT shifts. HMMMMMMMMMMMMMMMM

Day 50 | #100DaysOfCode Halfway through! Reflecting back, I've learned a lot and today's progress reflects that. - Finished implementing function that prevents three shifts in a row. - Overtime rankings now sort properly + handle dupes - Work any shift auto randomizes ALL rankings

Day 49 | #100DaysOfCode Tentatively solved, not sure if it's entirely working yet. I keep running into bugs and getting sidetracked. For example, I noticed overnight shifts weren't being correctly dated. The fix was to specify the timezone: "America/New_York". Apparently this works during DST too!

Day 48 | #100DaysOfCode Back at it! Struggling with additions to the overtime bids. Notably this requires me to change up my schema for it, which came surprisingly easy. All that debugging is paying dividends ✌️ It's a process!

Day 47 | #100DaysOfCode Took a break off my app today. Just did some coding challenges =]

Wavves | 7.10.25 | Sinclair

Day 46 | #100DaysOfCode It took a little finagling and moving around helper functions but it's done. On holidays, shifts automatically turn into overtime shifts. Before is on the left, after is on the right.

Day 45 | #100DaysOfCode Not every day is super productive and that's okay. I spent a lot of time trying to debug the schedule when the issue was me hard coding inconsistent dates. - Fixed a crash w/ empty overtime bids being pushed to the schedule, wrapping code in simple if(true){//do this}

Day 44 | #100DaysOfCode My changes were less robust than I initially thought. I changed the date manually to check if the function was working properly and got a whole host of errors! Turns out my schema values are entirely fixed. Spent my time today debugging and I'm still not done 😩😩😩

Day 43 | #100DaysOfCode - Finished holidayOvertimeCreator() By returning an array of objects, I can return every property required to create an overtime shift. - Revised date in overtimeSchema from mm/dd to mm/dd/yy. Spent an hr rewriting code to ensure the change didn't break anything 🫡

Day 42 | #100DaysOfCode Struggling to turn the image on the left into the image on the right. I'm very close to solving it. ATM I have an object (3rd img) to hold the day keyed to the corresponding shift IDs, but I think I need to include more info in the obj OR use one less function.

Day 41 | #100DaysOfCode Using the holidays implemented yesterday, working on a function to detect if next week contains a holiday so all the shifts on that day can be turned into overtime shifts. Writing pseudo code helps a lot but I ran into a roadblock during implementation. Need more planning🧠

Day 40 | #100DaysOfCode 🎵NOW ITS A HOLIDAY🎵 Today I implemented adding and deleting holidays. Went pretty smoothly, feel like I have a greater understanding of the MVC architecture now + familiarity with mongoDB/mongoose. Happy 4th yall!

Day 39 | #100DaysOfCode Yesterday was automatic addition, today is automatic deletion. I'm glad to report that the 'delete all' as well as the singular delete automagically remove entries from the schema. If you'd like to know more abt details, I'm posting right under!

Day 38 | #100DaysOfCode Adding vacation automatically creates an open shift! Took me way too long to do this. Had to create this helper function and ANOTHER helper to actually add an entry to the openShift schema. Learned a lot though! Broke many things with this change - something for tomorrow 😅

Day 37 | #100DaysOfCode 😮‍💨 Spent ~two hours debugging a new addition (all overtime shifts to the schema -> schedule) before realizing that simply adding the location id solved 99% of my problems and I didn't need to refactor / revise any of my current code. Now unfilled shifts display as OPEN

Day 36 | #100DaysOfCode Making use of my new vacation schema by listing people who are off. I've also highlighted assigned overtime shifts in the schedule, which makes me realize I need to filter out people who are on vacation!

Day 35 | #100DaysOfCode Created yet another schema, this time specifically for vacation. Maybe unneeded but the idea behind this is 1) deleting individual days 2) Flat structure for easy lookup later. Deleting mostly works, still need to iron out deleting empty dates.

Godspeed You! Black Emperor | 6.28.2025 | Roadrunner

Day 34 | #100DaysOfCode Not a lot of time today so not a lot of progress made. Just worked on some minor bug fixes - capitalizing the days in the html (it's easier if everything is lowercase in the backend)

Day 33 | #100DaysOfCode Continuing onward with CSS today, using Bootstrap to create tabs for another webpage. It looks MUCH cleaner this way. In the backend I fixed button redirects, learning a lot about how web and bootstrap APIs in the process. Made myself a nifty little helper function.

$1 wings wednesdays 😋 The green wings were my favorite by far even if I had no idea what it was. Very glad that the waiter told us about their new special!

$1 wings wednesdays 😋 Not sure what the green stuff but they were tastiest and it wasn't even close.

Day 32 | #100DaysOfCode Bootstrap and CSS! While not completely done w/ backend today I decided to give it a change of pace. - Created a navbar in header - Added tabs for adding/editing/deleting monitors/shifts/locations/vaca - Moved around buttons and made tables prettier. Lots more to do!

‪Day 31 | #100DaysOfCode Today was more experimenting than coding. - Fixed a couple of date range bugs (5/1 -> 5/8 is eight days!) - Researching best to download the table. Experimented with json, xlsx, but those seemed far too complex. Tentative plan is pdf.

Day 30 | #100DaysOfCode Can't believe it's already been a month! Time really flies by. Today I finished porting the other half of my calculations into the schema, albeit in a quite clumsy way. I converted it from an object to a map during calcs and then back to a plain object for the schema.

Day 29 | #100DaysOfCode - Added start hrs and total hrs to the audit log as well as showing change in hrs at each step. - OT calculations are pushed to the schema -> Doesn't have to recalculate on each page refresh. This required two new routes for each button.

Day 28 | #100DaysOfCode Fixed it! I knew I was overthinking things. Instead of casting the obj into an arr, I loop over Object.keys() to get the name, then loop obj[name] to get hours. To populate the shift header, I created a variable to increment when the above table of winners populates.

Day 27 | #100DaysOfCode Having a trail of receipts is important! That's why it's crucial that my app has a history of calculations. Got it semi-working but spent most of day rewriting code. I am definitely not writing efficient code, idt its best practice to reformat the same data multiple times.