Full description not available
M**Z
Great book!
This book is awesome, it includes an step by step guide to build and understand React with typescript from scratch. For sure, you have to study and go further beyond the book, but it’s a excellent for self-study and take as reference for real world projects.
G**I
Good
Good
F**D
Well structured and thought out
The book presents the topics well but a neophyte in API programming might not find it useful until after some studies. The author did a nifty job.
P**A
Great resource if are using .net core backend with React
Great resource if are using .net core backend with React
B**C
Clear, concise and well-written
This is my second read of this PacktPub author and I found this book equally accessible and thorough without boring me to tears. The audience is rather broader than declared, but that's a plus in the book's favor that brought it above-average because all skill levels will find a lot of useful content, if you don't mind picking through the parts you know for some TRUE gems.The author's talent shines further through here with his instructional "style" because he gets to business immediately with code. That's what developers want to read: code. And Mr. Rippon certainly delivers that without forcing us to go through all of the implementation details. He briefly reasons through his stack and design choices and moves on. Which brings me to a comment around using stored procedures left in another review here. I don't see that as a negative observation regarding the book. Stored procedures are EXACTLY what should be used because they are more secure and proven to defeat SQL injection attacks. The data I/O ops are happening in the database server and not going on between the front-end and database directly (they go through Node.js and Express, which in turn talks to the database). Then we have TypeScript helping us keep our data models clean and <i>statically</i> typed.Which leads me to how pleased I am the author brings TypeScript into the front-end pieces with React, a subject many authors in the field seem to treat with trepidation and avoidance.* I've been a software engineer for more than 20 years, and I've been reading texts like this nearly as long. I'd almost begun to give this book a 4-star rating; I rate very few books 5 stars. But I have to go with my gut on this and simply conclude with, "Well done."* If you want good product recommendations for more TypeScript, you can search Amazon for Adam Freeman (APress) or Boris Cherney (Manning). I've read the TypeScript books by both. Caveat emptor: read the TOC and sample chapters before you buy anything.
A**V
Plain and full of bad practices
Well, before I bought this book, I red another user review, he complained about the authors using store procedures , but I thought was an maybe wrong complaint, its nothing wrong with store procedures in a backend API book but... then I red the book.Lts talk first about the good things this book has because, it has some1. The approach is hands on2. The Backend/Frontend solution is simple enought so it wont take hours and hours to code3. The topics are relevant (specially the Auth0 part)Now the baddies1. The code has the worst practices of development, the Reac part has everything in one folder2. The Database uses Store procedures for CRUD operation (bad, bad BAD)3. The backend is using Drapper instead of EF (the superstar of .NET)I am very dissapointed (I asked for a refund) I hpped I will be founding best practices, architectures, best patterns, etc. but... no
V**N
Excellent book to get started
I really liked this book, because I am a mobile application developer and learning more about React and how this technology relates to ASP.NET Core is amazing.Honestly, this book is the one if you are looking to update yourself in Web development.
R**O
I cant take a book that recommends putting logic in the database seriously
I was just skimming through the book before actually investing time reading it to see how good the content was, to my horror, the database chapter uses stored procedures. This guy recommends using store procedures and putting logic in the database in 2020. Needless to say, I did not read the book. Even though I had already paid for the book, the time I was going to spend reading what probably is bad advice is worth much more. Look elsewhere.
Trustpilot
1 day ago
5 days ago