Do you want to learn how to write better React code, with proven principles like S.O.L.I.D, Separation of Concerns, and Design Patterns in your React? This is a book for you. More than that, this book teaches you how to become a more productive developer with over 16 Refactorings and 20 IDE Shortcuts you can use immediately in your project today.

 This book teaches you all the refactoring techniques you need in building React applications and will help you become a productive developer in general. It shows you 16 Refactorings you can use immediately in your project, more than 20 IDE Shortcuts that can boost your productivity, as well as design patterns you should consider in your design, how to apply object-oriented programming in your React and so on.

 In this small book, I plan to focus on several small but critical things for developers who want to write better React code and want to be more productive when doing it. On the surface, they may look like two different things, but they could be relevant when you think about them for a minute. I recently saw an interesting Twitter thread: Programming is thinking, not typing, and the author asked what people think about the line.

 For people who think “thinking” is more important than “typing”, I would say that may be the most misunderstanding in coding. And it sounds like an excuse why they are not good at thinking too. Those who are not good at typing are not good at programming either. And on the flip side, those who are good at not particular about typing but keyboard using overall (like keyboard shortcuts and other productive habits) tend to be good programmers too.

 I would not say there are some cause-and-affects in it, but there are some links there. All the good developers I’ve worked with are good at the keyboard (typing is just a subset of their skillset if it’s a skillset for a professional developer at all), with not even a single exception. Refactoring, a critical technique when you do clean code, consists of a few small moves, many of which are revertable (have an undo action). For example, Extract Function and Inline Function are a pair of refactorings. The simple fact is that the fast you can do either, the more confident you tend to do it.