Photo by Roman Mager on Unsplash
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.
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.👇👇🏻👇🏼👇🏽👇🏾👇🏿
Top comments (28)
Got to learn about GitHub Actions and I'm using it in one of the repo I'm collaborating one (A Chrome Extension 😉)
Of course, what I learned, I made an article on it!
Your guide to GitHub Actions in 5 steps 📚
Vaibhav Khulbe ・ May 21 ・ 5 min read
Nice!
Okay...but I wanted this GIF:
:(
TIL @nickytonline has exactly the same exact discussion question on Friday mornings as me, except his has next level gif responses.
This week I actually launched my newsletter, like actually send something out to the whole list. I learned a lot about newsletters and getting them going isn't quite as trivial as I had thought. From the suggestion of @chrisachard I started off with emailoctopus. It seemed like the easiest way to get things off the ground for free.
Chris runs a service makde.dev that I signed up for. If you want help trying to build your product/brand in any way check it out. It helped me get going.
You can sign up here waylonwalker.com/newsletter
Congrats on launching your newsletter! 🎉
(The site is: make.dev - looks like you have a typo there :) )
I learned that I can create multiple files or directories at once in the command line by putting spaces between them.
mkdir hello worldwould create ahelloandworldfolders in one go. It's command line magic.This week I learned how to create an Angular component and it has been really fun. After learning something about React, Preact and Vue now I know something about Angular too.
It's something, now tsParticles can be easily used in all this frameworks!
I tried Deno too but I need to be more focused, maybe next week.
ElasticSearch, within a Laravel project. Great technology, well designed and "it just works" (without too many surprises, that is).
We use ElasticSearch at DEV. Previously we were using Algolia. You might find this post by @molly_struve interesting.
Algolia is OUT! Elasticsearch is IN!
Molly Struve (she/her) ・ Apr 30 ・ 1 min read
Enjoy the weekend!
Cool, I saw the docs: docs.dev.to/backend/elasticsearch ... what I still need to do is delve into the whole devops/deployment/optimization side of Elasticsearch - how to configure it, monitor it, scale it (if needed), find out how much memory/CPU do I need to run it optimally, yada yada yada ... haven't really looked at that yet but at some point I should.
I have a couple of posts on scaling too that you might find useful. Elasticsearch is so easy to get going but scaling can be a PITA sometimes. But once you get it, oh man is it worth it! Good luck!
Scaling Elasticsearch Part 1: How to Speed Up Indexing
Molly Struve (she/her) ・ Apr 3 '19 ・ 6 min read
Scaling Elasticsearch Part 2: How to Speed Up Search
Molly Struve (she/her) ・ Apr 10 '19 ・ 5 min read
Thanks, that's great, I'm going to check it out!
I got to know that the following program is a valid C code
It automatically concatenates so the output would be
Hello World.It's a foot gun in some cases (like forgetting a comma between strings) but I get a lot of use from this feature when writing macros
That's awesome! 🔥
Yeah but it's really weird and confusing imo.
Sounds like it would make for a good post on DEV. 😉
It is really small so I don't think it's worth an article.
Playing Age of empires is not in line with what I want in life. Better go back to coding.
I learn CSS variables, media queries, the importance of fonts and shape-outside.
I learned about gitignore.io/ which makes it super simple to generate a gitignore file for your project.
Noice!
I learned about docker swarm and how if one node dies out, the swarm automatically publishes the copies in order to maintain the service.