#100DaysOfCode day 41:
I ran my app locally on my Mac today and fixed several bugs before deployment.
Also created the README because documentation is one of the more important aspects imo- Making sure everyone can always understand the code!
#codeEveryDay
#100DaysOfCode day 40:
The goal for this week is to deploy an AWS EC2 instance for my new automation at work.
So I spent today learning about EC2 and Flask Python apps on AWS
#codeEveryDay
#100DaysOfCode days 39:
Spent today setting up my mac for an upcoming project with frontend engineers at work. Also fixed some bugs in a project for work.
#codeEveryDay
#100DaysOfCode days 38:
Back at it after being out sick for several days.
Made several improvements to my @intercom & @SlackHQ bot following peer feedback:
Improved text now includes timestamps, and events only trigger during work hours
#codeEveryDay
#100DaysOfCode days 35-37:
Very close to solving Picking numbers from Hacker Rank. Will get there tomorrow
https://t.co/bNRg3RTRdR
Also going over algorithms course on Udemy
#codeEveryDay
#100DaysOfCode day 32:
Refactoring my fitness app after hitting a dead end.
I find that these are the most important moments, where I grow the most as a software developer
#100DaysOfCode days 31:
Back at is with JavaScript Algorithms and Data Structures Masterclass on Udemy.
I find it useful go bit by bit let the each concept sink in before moving on to the next one.
#codeEveryDay
#100DaysOfCode days 28:
Solved "Zig Zag Sequence" on Hacker Rank, in Python.
https://t.co/LUTEr52Qzo
I used the opportunity to learn more about sorting algorithms
#codeEveryDay
#100DaysOfCode days 27:
Solved Hacker Rank's "Maximum Perimeter Triangle" challenge.
This one was harder than I initially expected!
https://t.co/6xtK9hEmAU
#codeEveryDay