Full Stack Developer | Co-Founder @IndyRedUltimate | Professional Athlete #33 @ny_gridlock | Pun Enthusiast | she/her/hers

Joined September 2019
Days 44-48/#100DaysOfCode Practice problems on practice problems on practice problems
1
3
5
Day 44/#100DaysOfCode Redux Store day! I had worked with existing Redux setups, but this was my first time working from scratch.
1
1
1
Day 43/#100DaysOfCode Another of @cassidoo's questions! This feels a littttttle messy. Limited to 8 decimal places because I didn't feel like implementing anything to deal with JS conversion to exponential. What edge cases did I miss? jsbin.com/januboguva/1/edit?…
3
6
21
Day 39/#100DaysOfCode Variations of the TwoSum problem. When in doubt: use a Map
1
3
Days 32-38/#100DaysOfCode I've been taking advantage of @LeetCode's Mock Interview feature to prep for interviews & staying off Twitter. Definitely slow to start some of them but can usually depend on a lightbulb moment to finish after some false starts.
1
2
1
Day 31/#100DaysOfCode Practice problems using binary search. Implemented it recursively yesterday but finding iterative to be more useful in problem solving (i.e. being able to track lo/hi bounds of the search & getting an index)
1
2
Day 31/#100DaysOfCode Searching algorithms (aka: binary) + learned about the summation formula Gist: gist.github.com/piontekle/0d…
1
1
1
Day 30/#100DaysOfCode Revisiting sorting algorithms. Used @freeCodeCamp for a reference & did my best to implement Insertion, Selection, Bubble, Quick, & Merge Sorts. Saved them + some testing in this gist (need to beef up testing): gist.github.com/piontekle/41…
1
2
3
Day 29/#100DaysOfCode Learned about property-based testing. I love finding new ways to break my code to make it better
1
1
Day 28/#100DaysOfCode Read more about system design, specifically load balancer vs. reverse proxy
1
2
1
Day 27/#100DaysOfCode Finished chapter 2 of Pragmatic Programmer - I'm excited to work on estimating and my understanding of domain languages
2
1
2
Day 26/#100DaysOfCode Built a card component for my FitFeel app after not touching it for a few weeks. It was an easy way to re-familiarize what I'd already done & what my goals were
1
1
Day 23/#100DaysOfCode Reviewing time complexity, data structures, & algorithms to stay sharp for interviews
1
2