DEV Community

loading...
Cover image for February 11th, 2021: What did you learn this week?

February 11th, 2021: What did you learn this week?

nickytonline profile image Nick Taylor (he/him) ・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.

Dog lying back and typing on a computer

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

#todayilearned

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

A show host dancing a winning in their seat

Discussion (21)

pic
Editor guide
Collapse
pankajpatel profile image
Pankaj Patel

I attended my first GoLang Essentials course on LinkedInLearning.

Being a FE Dev I am delighted to see the power of Go and motivated to do some experiments with it.

I hope one day I would be able to write my serverless functions in Go as well

Collapse
nickytonline profile image
Collapse
pankajpatel profile image
Collapse
jasonf profile image
Jason F

I learned how useful git stash save and git stash apply can be.

Collapse
saurabhnigam profile image
saurabhnigam • Edited

Is git stash different from git stash save?

Collapse
jasonf profile image
Jason F

With git stash save you are able to add a message to your stash, almost like a commit message. It would like something like git stash save "stashing my changes". This makes it easier to know which stash is which when you run git stash list. You can then pick which stash to use with the git stash apply command. You would just need to provide which stash from the list using syntax like git stash apply stash@{2}. The 2 is the id of the stash, which you can see when you run git stash list.

Collapse
nickytonline profile image
Collapse
markokoh profile image
Mark Okoh

This week I learned how useful it is, posting and commenting on Dev.to.

Collapse
nickytonline profile image
Collapse
mse99 profile image
Mohamed Edrah

Studied the node event loop in greater depth and how es modules and common js modules are loaded and executed differently by node

Collapse
tamj0rd2 profile image
Tamara Jordan

Care to share any resources you looked at?

Collapse
mse99 profile image
Mohamed Edrah

I'm reading a book called node js design patterns the first few chapters disect the internal architecture of node, I also watched a free 1.5h workshop on YouTube called broken promises

Collapse
nickytonline profile image
Collapse
wolfhoundjesse profile image
Jesse M. Holmes

I learned that I enjoy take-home assessments way too much. Also, Ruby on Rails! I wish I had picked it up earlier. It has everything.

Collapse
nickytonline profile image
Collapse
cooltea713705 profile image
cooltea713705

Today I learned that GitHub does not use the PR title as commit message (when using β€œSquash and merge”) if there is only one commit in the PR (it uses the commit message instead). Broke the build :-(

Collapse
nickytonline profile image
Collapse
thuangempage profile image
thuan-gempage

This week I learnt Nestjs by making simple authenticate API

Collapse
nickytonline profile image
Collapse
nald_dev profile image
Nald Dev

Doing some maintenance for client's old project, figuring out how to build the project, and it was using gulp. So i learnt gulp this week

Collapse
nickytonline profile image