This document is written to help JavaScript developers to understand JavaScript's weird parts deeply and to prepare for interviews, the following resources was really helpful to write this document:
So, are you building microservices? Take a look at a few of these symptoms, and decide for yourself:
- ❌ A change to one microservice often requires changes to other microservices
- ✅ Deploying one microservice requires other microservices to be deployed at the same time
- ❓ Your microservices are overly chatty
- ❌ The same developers work across a large number of microservices
- ✅ Many of your microservices share a datastore
- ✅ Your microservices share a lot of the same code or models
Don't do the crime, if you can't do the time.
-- Anthony Vincenzo "Tony" Baretta
Vim is an amazing text editor. I love it. Really, I wouldn't [organize][organize] a Vim advent calendar if I didn't. But, as amazing as it is, Vim is not for everyone. It can't solve all your problems, or be a TUI version of your favorite IDE, or make you a better programmer, or land you that dream job in the Bay Area. But Vim can help you be more mindful, focused, and efficient, as long as you approach it with the right mindset.
Don't get me wrong, I certainly welcome you to try Vim, but I'm not a proselyte. I don't thrive on newbies. I just want you to use the right tool for the job and not waste your—and anyone's—time on a fruitless quest.