Cover image for Dec. 20, 2019: What did you learn this week?

Dec. 20, 2019: What did you learn this week?

nickytonline profile image Nick Taylor (he/him) Updated on ・1 min read

Weekly Learnings 2019 (6 Part Series)

1) Nov. 24, 2019: What did you learn this week? 2) Nov. 29, 2019: What did you learn this week? 3 ... 4 3) Dec. 6, 2019: What did you learn this week? 4) Dec. 13, 2019: What did you learn this week? 5) Dec. 20, 2019: What did you learn this week? 6) Dec. 27, 2019: What did you learn this week?

It's that time of the week again. So wonderful devs, what did you learn this week? It could be programming tips, career advice etc.

Deadpool and his cohorts chatting

Feel free to comment with what you learnt and/or reference your TIL post to give it some more exposure.


Summarize a concept that is new to you.

And remember, if something you learnt was a big win for you, then you know where to drop it as well.πŸ‘‡πŸ‘‡πŸ»πŸ‘‡πŸΌπŸ‘‡πŸ½πŸ‘‡πŸΎπŸ‘‡πŸΏ

Big win. Danny Devito walking away from a huge explosion


markdown guide

I learned how to translate a program into 42 different languages in less than 4 seconds. Literally 1 week ago, I was totally clueless as to how I was going to do this (you can see the bumpy road in my git history lol). (Future article may be on its way).

(And, although not this week...I did learn a few years ago that Danny Devito likes cars. I met him after the Barrett Jackson car show out here, twice. Nice guy)


It will probably be in this series. The first article describes the CLI tool. The next one will probably describe the translation (a newcomer may think it is straightforward, but there are some gotchas to be aware of)


Learned how to do a release on the open source product I'm maintaining! It's not the first release ever on the project but it's the first one I've administered and a good learning experience 😁 github.com/unmock/unmock-js/commit...


I learned that things are not always what they say they are.

This is probably a lesson I should have learned long ago, but... Don't trust software documentations.

They just lie to you.

I didn't want to fill my code with try catches, so I implemented it exactly as the documentation told me. I'm now filling my code with try catches after things didn't come the way they told me they would.


I learned that having a technical debt is an awful thing (the hard way, of course) when we couldn't deliver every feature we developed because the code was awfully intertwined and we had a really hard time merging everything together.


Learnt how Event Loop, Timers Works in Node.js and will be deep diving in to it with real life examples.

[I'm an inline link]nodejs.org/en/docs/guides/event-lo...


I also like this video on the subject. It's nice to see the nodejs docs discuss it!


Se que no es mucho pero en esta semana aprendΓ­ a aΓ±adir detalles en una fila usando datatables. -_-


Awesome that you learnt about data tables. πŸ‘


Finally went through some Ruby basics after passively using it for a while πŸ€“
Here's my findings so far


How to successfully schedule, record, and edit my first podcast across multiple countries πŸŽ‰πŸŽ‰