Cover image for Jan. 24, 2020: What did you learn this week?

Jan. 24, 2020: What did you learn this week?

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

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.

It’s time to get your learn on

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.πŸ‘‡πŸ‘‡πŸ»πŸ‘‡πŸΌπŸ‘‡πŸ½πŸ‘‡πŸΎπŸ‘‡πŸΏ

Someone feeling like "Yaaas!"


Editor guide

This week, I learned about this app called Muzzle, which hides on-screen notifications while I'm screensharing :)



Holy moly, thank you for this!


I learned a lot about surrogate keys in edge caching.

Alongside @rhymes and co we're getting a better handle on the caching infrastructure we use at DEV.



🌼🌳🌱🌍I learned about the impact of digital services on the environment (us), and what I can do about it. I learned that majority of the impact is coming from building new devices (phones, PCs, tablets, connected cars) and that the way to reduce that impact is to design digital services which are optimized so that renewing a device because it is slow can be delayed.


I learned how to build React with Parcel!

I wrote about the journey here.


I recently started a new job at a site you may have heard of, and have learned so much about their codebase and processes!


that's sound great, congratulations.


dev.to seems like a dream place to work!


I learned about C++ template specialization:

I learn something new about C++ damn near every coding session, it seems. Huge language.


I've been working with BDD (Behavior-driven development) this week and I learned how to run e2e tests for an Angular app using Gherkin syntax. For this purpose I had to setup Protractor + Cucumber-js + Chai. At the end everything worked which was amazing πŸ˜€


I learned that you can hide a parent element with visibility: hidden but still show its children with visibility: visible.


I learned that if you inline

apt-get update -y && apt-get install -y ...

in your docker build script, you may miss these errors

E: Release file for ... is not valid yet (invalid for another 22h 2min 28s). Updates for this repository will not be applied.

Which leads to other potential other issues.

So from now on, I'll put them on a separate lines.

apt-get update -y
apt-get install -y ...

This week, I got introduced to Elixir programming language and I wrote a function to calculate the factorial of a number.

I expressed my surprise at how you can calculate the factorial of 10_000 very fast on the post How to Calculate the Factorial of 10_000 - Elixir.

This is not possible in many other languages by the way... So it was a good lesson!


Sounds really cool. I haven't done any Elixir myself, but I know the folks at Infinite Red led by Jamon Holmgren do quite a bit of it. I found a brief post from him about moving to Elixir, shift.infinite.red/the-rails-doctr....

He's on DEV, but not really active at @jamonholmgren . He Tweets a lot, so give him a follow there too if you want.


Wow! Thanks.Will definitely follow him.


I took things lightly and made a simple meme maker application with React. Earlier I was using some fancy technologies/libraries in my e-comm project, this time around, I made this meme project with just React.

Sometimes using less is good!


I learned that Tailwind CSS exists, and that it's fairly easy to set up, but that I probably need to practice UI/UX skills a bit more to make effective use of it.

But I'm excited to try! BootstrapVue works great for me when I'm not concerned about building a unique UX, but it never feels easy to customize Bootstrap to give a unique look and feel, even though I know it's possible.

It seems like Tailwind solves that problem, allowing you to gradually build your way up to reusable components over time.

If anyone here has good learning resources about Tailwind that they'd recommend checking out, I'd love to hear about them.


I too have been wondering if tailwind is worth the time investment for me to learn. I have the Tailwind playground bookmarked which seems useful because of the intellisense. I'm in the same boat in that I think a lot in terms of BootstrapVue and native CSS3, and I'm not sure how much I would have to unlearn things before I fully understand tailwind. And it's not completely clear to me if the benefit Tailwind provides is worth the benefits it throws away: like, I can use a class "border-purple-100" but not "border-purple-150"? Whatever used to be a laundry list in css just got moved into a laundry list of class names in the HTML. Also, the other big tradeoff to me appears that changing the entire theme of a given page will become much more challenging when using utility-first framework (i.e., the class names of each element will have to be tweaked). Maybe someone can convince me otherwise.


About changing the theme of a whole page, I mostly assume that I would be using utility classes to build reusable components in Vue, rather than directly using the utility classes everywhere.

So taking that approach, rewriting the theme for each component would then apply the styling wherever it is used.


I did a lot of react since last week!

And I discovered, since last year , React has changed a lot...

Everything in react is now a hook, and redux is not completed as I taught it’s!

I learn also about how to use docker to generate SSL certificates and how to use cronjobs in windows....


Nice Espoir! Yes, there are a lot of new things in React. One great article I'd recommend if you're new to hooks is this one by @wattenberger . Sidenote, great work on this article Amelia! πŸ”₯

Thinking in React Hooks


Let me check it out...


I learned how to combine markdown and Vue markup together into my storybooking module nuxt-stories. You can check it out here! The same markdown component can easily be reused anywhere in the Nuxt app. This means your stories or your vue templates can be written like this:

  * Here is story 1
  * Here is story 2
  * This is the logo component:

  A table would be here:
  | Header 1 | Header 2 |
  | --- | --- |
  | Data1 | Data 2 |

The markdown will be compiled into beautiful mark*up*. And the <logo> will be a fully functioning Vue component! The markdown renderer is extensible and in my demo, you'll see the bootstrap table-striped being used, but never in my template do I have to write class="table table-striped". So, this makes it far easier now to write notes, gameplans, stories, whatever!

Only caveat: while it can be re-used in a Nuxt app, since the HTML is being re-compiled, Vue will complain that "server-side rendering doesn't match...". That just means <markdown> needs to be wrapped in a <client-only> tag.


This week I've been learning how to use Konva, which is proving to be a really nifty library for interacting with the <canvas />. Has been especially nice paired with react-konva.

Building something with this that I should have available soon!


I've learned about the importance and how to mesure Key Devops metrics.
I've also worked with Jenkins for CI.


This week I learned that there's a difference between ROWS BETWEEN and RANGE BETWEEN in the partition clause of window functions in SQL. And different engines have different levels of support for the two.


Hello there! this week has been all about getting my hand dirty with nodeJS + Express JS.

For node I have been learning about Node Modules, NPM, etc.

On the express side I was able to to create my first server... Trying to understand router/routes, Middle wares, CRUD operations.

The back-end is really exciting :D !!


The Python/C API, tough and still trying to grasp it but I've started at least.


Mainly I have been learning about Node.js, and creating basic RESTful Web Services


An in-depth read through of official Kotlin coroutines guide.


I learned about Jupyter Notebooks, Cloud architecture and Python language.

I'm following this path in pluralsigth


I learned what an API gateway is after my boss did a demo using Kong! Thinking about writing something about it now... πŸ€”πŸ€¨πŸ§


Learn RxJava. Dagger2 is next


Last week (because sorry I'm late) I learned GraphQL :) and what a fantastic discovery and feeling !


I learned what is Angular Universal maybe next week i try use that.


I have been splitting my attention between getting started with azure and getting better at automated testing.


I learnt about the network library in Java and how to do socket programming and writing your own server and client.


I learned about how much faith my team mates have in my technical abilities. While I just feel like an ordinary Joe. So now I am pumped up to be better.


learned graphene for python( django)

actually looking for graphql python and some best practice


How to use Composer/npm with Docker finally clicked and it's like my whole world just got shook, lol.


I learnt that you can name loops and blocks in JavaScript and how to tackle bugs that don't throw any errors to the console.


I have been deep diving in some MySQL and discovering some... let’s say... limitations... of 5.7 vs newer versions and other DB platforms... but I survived!!


This week, I learned python and wrote api calls to Spotify to return information on artists such as top 20 songs.