Let’s Be Strict
Today I spent 30 mins pairing with one of the Learn instructors trying to work through some issues my Rails portfolio project has. Something I found out is that the project requirement to use a custom attribute writer instead of
has_nested_attributes actually removes some functionality from the final app. Because of this lack of Rails magic one of my problems is harder to fix than expected. The other one is just a more simple
Something that I ran across today in my IDE was a linting error from JSLint stating
Missing "use strict" pragma on one of my functions. So, like a good dev I Googled this (well DuckDuckGo’ed this). I came to a great post and discussion about this on Stack Overflow. My takeaways were that using
WHERE SHOULD I USE ‘USE STRICT’;?
'use strict';does not suddenly make your code better.
I plan to add
What do you think about
'use strict';? Leave it in the comments for me.
I also found out tonight from my Free Code Camp Nashville Co-Organizer Dave that he scored us a table at Music City Code 2017 which is pretty sweet. Not sure what we’re going to do with our table just yet so if you have ideas please let me know!
Time spent today: 3:07
Time spent total: 329:01
Lessons completed today: 5
Lessons completed total: 529
If you know someone that is thinking about doing an online coding bootcamp, please share this article on Facebook and Twitter.
And please click the 💚 below so that other people will see this here on Medium. Thank you for reading.
Originally published at itzsaga.github.io on May 25, 2017.