Edward
@edwardcodes.bsky.social
Fullstack Software Engineer | Boston | CLAM CHOWDA | #100Devs
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!
More React practice with two games.
tenzies-qqhy.onrender.com
programming-language-hangman.onrender.com
Try em out and lemme know what you think!
September 11, 2025 at 1:58 AM
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!
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.
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.
September 1, 2025 at 11:29 PM
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.
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.
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.
August 21, 2025 at 10:27 PM
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.
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.
August 18, 2025 at 7:28 PM
Day 79/80 | #100DaysOfCode
- Code wars
- Working my way through Scrimba React tutorial, created a static page.
- Code wars
- Working my way through Scrimba React tutorial, created a static page.
August 15, 2025 at 12:03 AM
Day 79/80 | #100DaysOfCode
- Code wars
- Working my way through Scrimba React tutorial, created a static page.
- 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.
- 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.
August 13, 2025 at 12:08 AM
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.
- 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.
- 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.
August 10, 2025 at 4:30 PM
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.
- 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!
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!
August 8, 2025 at 1:20 AM
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!
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!
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!
August 6, 2025 at 4:18 AM
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!
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 😵💫
- 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 😵💫
August 4, 2025 at 4:13 AM
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 😵💫
- 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. 🤷♂️
- 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. 🤷♂️
August 1, 2025 at 10:07 PM
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. 🤷♂️
- 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.
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.
August 1, 2025 at 1:40 AM
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.
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.
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.
July 31, 2025 at 2:21 AM
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.
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 😅
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 😅
July 29, 2025 at 3:20 AM
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 😅
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...
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...
July 25, 2025 at 3:03 AM
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...
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 😭😭
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 😭😭
July 22, 2025 at 10:39 PM
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 😭😭
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!
Debugging Holidays today, specifically auto-creating overtime shifts on each holiday. Fixed one bug but another popped up!
July 22, 2025 at 4:30 AM
Day 55 | #100DaysOfCode
Debugging Holidays today, specifically auto-creating overtime shifts on each holiday. Fixed one bug but another popped up!
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 =]
Coding challenges and figuring out the next steps for my app =]
July 21, 2025 at 3:52 AM
Day 54 | #100DaysOfCode
Coding challenges and figuring out the next steps for my app =]
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!
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!
July 20, 2025 at 3:45 AM
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!
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.
new Date("wtf")
How well do you know JavaScript's Date class?
jsdate.wtf
July 19, 2025 at 5:34 PM
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
- 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
July 19, 2025 at 2:46 AM
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
- 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
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
![Nullish coalescing operator. If the current monitor Id does not exist / undefined / null, then it's initialized to an empty array. I.E. {'0d73bb73f6f94f7fab': [] }
Then the ranking's openShift ID is pushed into that array. No if statements required!](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:4btavlqvfwkwzzkaj26qceiq/bafkreibvyug3mhqfzfe2mbyeyleyi3jwedclibw5quhyjqlc3m7c4ctmcy@jpeg)
July 18, 2025 at 4:41 AM
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
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
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
July 17, 2025 at 4:08 AM
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
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!
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!
July 16, 2025 at 3:08 AM
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!
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!
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!
July 15, 2025 at 3:28 AM
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!
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!