100 Days Of Code - Log
Day 1: December 12, Thursday
Today’s Progress: I’ve been working on the Roller Blinds Wifi project, investigating why does my stepper motor (BYJ48) always spin in the same direction using J5. I found that the problem is related to the sequence of the motors, J5 is using a different from the one that specify the builder, here is the documentation about it. What I tried:
- Rebuild from scrath the Stepper library using J5.Pin, but for a strange reason that I didn’t have much time to see it doesn’t like moving the stepper with Arduino’s code.
- Create a new issue in J5’s repository to see if anyone had this trouble and how I can manage to solve this problem. I looked up in the codebase of the framework but I didn’t find anything related to the sequence.
Overall status: Good
Link(s) to work
Day 2: December 13, Wednesday
Today’s Progress: I’ve been working with Cato trying to understand J5’s code of Stepper class and see how we can change the sequence of the stepper. To do this we clone J5 repo and add a simple test connection file in order to be able to debug it. Sadly, we didn’t find anything … Right now there are 2 reasonable possibilities:
- Keep looking in the Stepper class code, there are strange variables like
this.iothat I think that has the magic inside. - Implement another driver (fisically) that works with 2 pin so we don’t have this Direction problem anymore, to do that I have a Pololu driver but it works with 9V so we need a power supply to make it work.
Overall status: Bad
Link(s) to work
Day 3: December 14, Thursday
Today’s Progress: Tired of working with the blinds project I decided to create a new repo in order to test how integration tests could be done. I’m following this article which at first sight seems really cool. So, I started working on a Weather Application that make a fetch when the component mount on the DOM, dispatch some actions, reducers take that aciton’s types and then with some selectors I get the values that will be using my component. The idea is to see how far I can get to test this small application and also, see if give value for the application.
Overall status: Good
Link(s) to work
Day 4: December 15, Friday
Today’s Progress: So after having a lot of troubles with CORS calling the weather API of Open Weather, I decided to move foward to another onen and it was the best decition I took today. It has the ability to get the forecast with latitude and longitude, which is great because I star the project with that idea. Also I can get many forecast that I want, but I think I’ll keep with 6. Next steps are:
- Adding Weather Cards with CSS Grid
- Adding Location Bar
- Add the posibility to refresh the weather
- Finally and the more important is to start making integration testing with cosmos!
Overall status: Good
Link(s) to work
Day 5: December 16, Saturday
Today’s Progress: I started coding at 3 pm and finished at 3 am of Sunday, so today was really heavy! The most important thing that I’ve done was be able to change the sequence when moving steps with the Stepper library of J5, that took almost the whole day ( I had ot fork ConfigurableFirmata repository in order to be able to debug it) but it’s working excellent :) Another thing was to advance with the server:
- It has the possibilty to communicate with socket (using Socket.IO)
- It is saving the position on a Local Database (using NeBD)
Overall status: Good
Link(s) to work
Day 6: December 17, Sunday
Today’s Progress: I started learning CSS grid to implement it on the weather-react-cosmos app just to give it responsive design. Also made some change sin order to have icons representing the waether, my idea is using icons that have a bit of movement just to make it nicer :)
Overall status: Regular
Link(s) to work
Day 7: December 18, Monday
Today’s Progress: I worked on impementing enviroment variables on roller-blinds-server and also adding async/await in order to avoid using promises. Also, I made the first iteration to integrate Redux with Socket.IO and work very well there are some issues and error handling that I have to take care of but fortunatetly the socket itself is working for more than one client.
Overall status: Good
Link(s) to work
Day 8: December 19, Tuesday
Today’s Progress: I added error handling on the server side (it will return an action with the type ‘SERVER_ERROR’ with the message), then on the client I added a notification system so when it received an errror it will show a notification on the left bottom corner.
Overall status: Good
Link(s) to work
Day 9: December 20, Wednesday
Today’s Progress: With the team we did the integration of the apps with the roller blinds server. It’s working pretty well but we’re having some troubles connecting to the server from our client (Marcos computer).
Overall status: Good
Link(s) to work
Day 10: December 21, Thursday
Today’s Progress: We add validation to the roller blinds in order to prevent from moving if the server doesn’t respond with a succesfull response. After doing this, we kind of broke the whole server/application and also there are some strang behaviour inside the server. Besides that, we did the presentation talking about the scope of the project, architechture and communication between all the parts of it.
Overall status: Regular
Link(s) to work
Day 11: December 22, Friday
Today’s Progress: I add HMR to the roller-blinds project on the server side, but I have a lot of questions how it works due to I just copy and paste the webpack.config from a post that I saw on stack overflow. Besides that I have an express server rocking!
Overall status: Good
Link(s) to work
Day 12: December 23, Saturday
Today’s Progress: I continue investigating the magic of webpack and endup checking the difference between webpack-dev-server, webpack-hot-reload, webpack-zarlanga, etc. There a lot of those, I’ll keep with my webpack config on the project I think is running great, but there a few problems with variables that in node works but here it doesnt like _dirname.
Overall status: Regular
Link(s) to work
Day 13: December 25, Monday
Today’s Progress: I finally made socket IO with express to work with the HMR of webpack in same server. The problem was that if both frameworks shared port for a strange reason when one of those reload because of a change in the code (in this case was express), an error message appear on the console saying that the headers can’t be replace for a strange error code that I obviously why was happenning. So after lookin for 2 hours on Google, downloading a bunch of repository that people said that they have a server with HMR on it (obviously any of those have a working HMR), I encounter the page that a guy said “That kind of problem is always because they shared port, so change it and it will work”. So I did, and instantly HMR reload was working like a charm! :love:
Overall status: Good
Link(s) to work
Day 14: December 26, Thursday
Today’s Progress: I start doing programming exercise in a platform called Codility due to I have a job interview and the guys from that company will send a few exercise to see if I can do them. I was really rusty on those subject, for example: data structure and complex algorith in which ones you have to take in consideration the space complexity and time complexity. So I create a repository to keep a track of them and did a pair of it. My idea is to keep practicing in order to get to the test in the best shape that I can.
Overall status: Regular
Link(s) to work
Day 15: December 27, Wednesday
Today’s Progress: In my job I had a task to add integration to our project and also write documentation about it on a README.md, which kept for a lot of hour making that, and endup creating a repository when I can do a simple integration test with a Counter component which basically when the user click on it, it will increase by one a counter, that’s it. I did it with redux otherwise the integration test won’t be suitable (in that case I would go with Unit test). I like starting a new demo project and finishing in 2 hours, it feels really great! :D
Overall status: Good
Link(s) to work
Day 16: December 29, Friday
Today’s Progress: In my job, I had a task to improve the performance of specifics popups that we have on the application. So I start by looking at the container and check why they are rendering. I had to go deepper and check the function that do the shallow comparison between mapStateToProsp and previous stateToProps, and I learned that if you create an object/array inside the mapStateToProps then your component will always refresh.
Overall status: Regular
Link(s) to work
Day 17: December 31, Sunday
Today’s Progress: I read a post on medimum saying the advantages of parcel, which I already knew but never tried. Well it works pretty well and also the good part is really lightweight :D So I think that I will create a boilerplate for every app that I will create for this challenge :D
Overall status: Good
Link(s) to work
Day 18: January 1, Monday
Today’s Progress: Today I implemented animated weather icons with styled-components, fortunately the person who did the icons on codepen did a great job separating each css class so the task of creating each component was really easy. I did in total 3 weather which can be changed by props and then each prop is passed to the styled components, which finally change its css. Also, I added responsiveness to the application with CSS-grid and its awesome, totally love it!
Overall status: Good
Link(s) to work