5 Different Ways You Can Make Money As A Developer While You Sleep
TL;DR: This is for Web Developers
Either be a content creator doing YouTube Videos / Livestream or a front end webdev selling sh*t on Codecanyon, Canva Creators, or some other place to sell essentially website templates you create.
Review: 5/10
This does thankfully avoid the trope of “become a Medium writer and start a YouTube channel and monetize your Twitter followers”, which I easily sum up as the Tech-Focused-Meta-Success-Guru-Micro-Celebrity.
Don’t do Code Review, try Mob instead
TL;DR: Try pair programming or up the ante (3+ people???) and do MOB PROGRAMMING
This is actually useful advice and I am exhausted of the Code Review Process, but I don’t know if I will adopt Mob Programming since in my previous life I was a cat which means I am hard to wrangle into doing almost anything with a bunch of people.
Review: 8/10
The main benefits here are vocalizing the pain points of the code review process. Like any “don’t do this, do that”, there are pros and cons to each way of doing things. Ultimately though, it can sometimes be difficult to accurately express why it feels like something is broken, and this piece does an excellent job of articulating the specific problems with code reviewing. And I think there is a benefit to Mob Programming if you are able to do what the author says and communicate effectively between a group of colleagues.
We abandoned npm install, maybe you should too
TL;DR: They switched to Rush.js
If you are working at a company with multiple packages written in JavaScript, consider using some kind of monorepo package manager such as Microsoft’s open source offering, Rush.js.
Review: 8/10
The author does a good job of laying out the problem an organization can run into when dealing with a bunch of packages they maintain separately, thus motivating the need for a monorepo package managing system.
Also the author uses the phrase, “Say no more, fam.”, which I highly approve of.
6 Algorithms Every Developer Should Know
TL;DR:
An Overview of the topics covered in most Introductory CS courses.
Review: 8/10
The author goes through the followings algos/datastructures:
- Sorting Algorithms (bubble sort, merge sort, quick sort, heap sort)
- Searching Algorithms (binary search, BFS, DFS)
- Dynamic Programming
- Recursion
- Divide and Conquer
- Hashing
I’m bookmarking this because it’s nice to have a succinct, well communicated overview of the key algorithms and data structures used in those little programming puzzles interviewers often like to use.
Microservices are Dead — Long Live Miniservices
TL;DR: I’ve never built a Microservice so glad they’re already dead. But apparently y’all are forgetting that they’re decoupled.
Honestly, I wonder what kind of developers are the ones building Microservices and Miniservices. Because I am not one of them.
Review: 8/10
I like how the author gave such a clickbaity title but backed it up with some serious knowledge. This seems to be a relevant clarification but only if you are a developer building out REST APIs and… microservices?
