This is a technique I’ve been using for 3+ years and it’s a freaking golden.
Every morning I write two things:
1. Brain dump (all thoughts, feelings, and experiences I want to write down) 2. The goal for today (one main goal that I have to achieve today)
If you reflect and write everything you have on your mind (what you are stressing about) you will less procrastinate throughout the day and less thinking about *that one problem* you have.
This repository has practical content that covers all phases of a technical interview, from applying for a job to passing the interviews to offer negotiation.
The primary purpose of the code review is to make sure that the solution is solving the problem in the best possible way. From the code and product perspective.
But how do you determine if the solution you are reviewing is the best way to solve the problem? In other words, how to code review?
10 Interview Questions Every JavaScript Developer Should Know
🧵 Thread...
1. Name two programming paradigms important for JavaScript?
JavaScript is a multi-paradigm language, supporting imperative/procedural programming along with OOP (Object-Oriented Programming) and functional programming
2. What is functional programming?
Functional programming produces programs by composing mathematical functions and avoids shared state & mutable data
- The 7 Habits of Highly Effective People: Powerful Lessons in Personal Change
- Great at Work: How Top Performers Do Less, Work Better, and Achieve More
- The Checklist Manifesto: How to Get Things Right
2/ Writing Code
- Code Complete
- Clean Code: A Handbook of Agile Software Craftsmanship
- Code Simplicity: The Fundamentals of Software