I just wanted to gauge interest levels in an e-book that goes through building a complete web application using React and NodeJS?
It would explain how to:
- Create a webserver with user authentication - Hook up and work with databases via an ORM. - Generate API endpoints - Connect API Endpoints with a front-end framework like React - Explain how React and Flux works with APIs - Tips and Best Practices on building out a CRUD application using this framework - Security - Maintenance - Best practices in Production
Questions: 1) Would you be interested? 2) Would you pay for it if it was good, and had sample chapters? 3) Where do you get this information now?
Made it especially with you in mind. And it's free.
Section 6 & 7 - maybe this is what you are looking for?
Udemy frequently has sales on holidays and all courses are ~$15
Never understood what is so hard with user auth and why people need an example of a SPA with user auth. Your server is just a web API, so just use stateless authentication.
The reasons for these decisions would go a long way to addressing the concerns bitdeveloper has, too.
Python/Django, Scala/Play, Ruby/Rails, GOlang/X, Dart/X,Elixir/Phoenix? ...
The guidelines do not advise people not to downvote for disagreement. The guidelines do ask people not complain about them.
When someone makes a thread along the lines of "Non-NodeJS devs, what keeps you from using NodeJS?", this comment will be a welcome addition. I'd suggest that even there, you add something substantive. That the language is dynamic is probably not a good starting place given that dynamic languages run like half of the internet. Start with threading, the event loop, callbacks or swallowed errors - all ripe targets.
If you don't mind my asking, where did you come up with the idea that dynamic languages are unsuitable in this way?
[1] My reasons are many and varied, but largely come down to a matter of personal taste and bias due to long-ago experiences that soured me on JS.
I did build a complete web app (basically a Reddit clone) in NodeJs from scratch recently (though Angular2 instead of React), most of the things that you described in your book's contents were in the official documentation or tutorials (and Stack overflow).
Still, I don't know things like server-side rendering, and although I was able to configure SystemJs I have no idea how to configure it (or its de/merits over bable/webpack), 3rd party authentication (Google/FB login) was a pain, and now I realize I should have used the Flux architecture and also used TDD. But then all this is just a google search away anyway.
However, I would have paid for the book you describe if a) I wasn't broke, b) was just beginning with web dev, c) the book built a complete nontrivial app (something like the Meteor/Telescope).
PS: Which nodeJs framework would you suggest/use?
I believe they went through YC, actually.
Yes, after an introdutory free and useful by itself chapter/course.
Constantly looking for this kind of learning resource right now. I had a very good experience with this one: http://trysparkschool.com
In my personal case, as I'm learning to code from scratch, it is essential that the course do not assume too much about my previous knowledge. Check the Twitter course. It teaches me how to install everything from the most basic tools, like Terminal. It actually taught me what Terminal is.
I hope you do it, I very much need it. Get my email at the profile and please let me know if you do it. Good luck!
I've just been building stuff out in Node/JS-land for a while and just want to give something back to the community. So I'm thinking about starting an e-book or a series of blog posts to educate people in things that I've learned. Learning people's use cases gives me a better understanding of how I can write things that genuinely solve pain points.
I would really appreciate it if people could PM me some type of contact info so I can keep in touch with anyone who is interested. My email is tilomitra[at]gmail[dot]com.
A book is by definition 90+ pages long (probably a lot more). I will only want that much information if I'm completely new to the area.
I have never used Node.js nor React, but I did a fair amount of web design. A book will feel slow and repetitive.
Case in point: the last book I read was about Opencl. About a whole Chapter was dedicated to configuration parameters and C data types. I know that stuff has to be there in case the book is your only reference, but otherwise I can just check the Internet for that.
I know lots of people like technical books for pretty much the same reasons I don't, so keep that in mind too.
Most importantly, if there was a way for you to host the ebook online and provide a way for someone to type code into your website and mess around with the source code. Think like Codecademy, with code on one side and the result on the other.
