What are your thoughts on Functions as a Service? Lambda seems to be falling a bit behind in terms of their modern-ness - they're still using early 4.x. Do you see Lambda-like services springing up, or will Lambda be where the majority of FaaS for Node.js lives?

What are your plans for Zeit moving into the future? 🕵️

Do you have any plans to bring Now, as a platform, (NaaP?) to a larger business audience - i.e. large companies and Enterprises?

I totally get what you mean about books for in-depth information - that's how I learn best as well, and frequently found free videos and courses to be heavily lacking. That said, it's incredibly hard to find good Node.js books because of how fast Node moves, in comparison with the writing and publishing process of an actual book - which is what it seems you discovered with Node Up and Running. Here's how I've seen others succeed, and have just started succeeding with myself: Think of a project you want to build. It doesn't matter what the project does (it could be a command line tool, a simple web app, or a REST API), as long as you decide on something that's simple, something basic. Then, start working on trying to build it. Figure out what aspects of it need to be built (do you need a CLI assistant to build the command line tool? Do you need web server, like Express, for the web app? What are you going to return from your API - JSON? XML? Images? And so on.) and then look for a tool to do it. Do this for all the aspects of your app - try to limit it to 2-4 aspects (three is probably the sweet spot - 2 will go fast, 4 may be a bit much). Then, start building your app. Taking this approach will allow you to go as deep or as shallow as you want into the different aspects, without a pre-defined guide that may leave you asking questions. It will also allow you to try different things out, instead of whatever is prescribed by the creator. Finally, it will allow you to learn what's happening at present , instead of what happened 3 months to 3 years ago. Good luck!

I'm not familiar with Composer at all, but it looks like there are similarities to Composer - such as the lockfiles.

Glad you liked it! It's amazing how many small things you'd never think of can be so completely disastrous.

Also, what kind of format would you like to see that reference material in? Would you be preferred to be taught or be shown? When you were a new programmer, how would you have been ideally taught production caching, scaling, transactions, queues, workflows, perf, microservices, and Docker?

Was the Pluralsight course by Kyle Simpson a former/current CodeSchool Course? (CodeSchool was acquired by Pluralsight a while ago.) If so, I also did that course and found it extremely frustrating - it didn't fit my learning style at all. I really didn't like that I modified one piece of code at a time, while the rest of the code was displayed but uneditable. Would have much preferred to write the whole thing step-by-step. What was your experience with that course?

Attempting to start a fresh Electron app client for a decentralized social networking protocol (not going amazing), and then working on transferring npm-gui to a packaged Electron app. That's going a bit rough, because it's an express app that needs to run locally. Trying to figure out how to run the Express app in a different process.