![]() I think EJS does a good job of walking you though the thinking part, even though the “what you build” stuff isn’t really that great or impressive. sometimes there’s “real math” (which is often done by someone smarter than you and you just have to leverage/understand the math) and then you have to think about “the edge cases”, etc. there’s “the stated problem”, then there’s “the constraints” or limitations of the environment, there’s the “input data” and you have to figure out what the “output data” should be. The way that engineers have to solve problems is often complicated. It is, however, a good book on introducing an “engineering mindset”. It’s not (strictly speaking) a book on how to use the JavaScript syntax, nor is it really a book on how to build web applications. Personal blog posts that are relevant to the subreddit's stated subject matter don't need prior approval (and are encouraged!). ![]() If you want to post something self-promotional, please message the mods first. ![]() Titles that begin with "hey guys" will be removed. If you're in doubt, message the mods first. The following are not allowed: Requests for subscribers, asking for "test users" for your new JS course, offering paid mentorships, and/or premium courses. If you’re asking for help, include enough information for others to recreate your problem. With a nod to practicality, questions and posts about HTML, CSS, and web developer tools are also encouraged. Everyone should feel comfortable asking any and all JavaScript questions they have here. ![]() This subreddit is a place for people to learn JavaScript together. ![]()
0 Comments
Leave a Reply. |