(Part 3) Top products from r/javascript

IBM?

Man, going from angular to dojo is going to be terrible.

Going from nothing to dojo this book was helpful. I can't say I came across any screencasts during my time with dojo. The docs and the getting started demos are probably the best help you are going to find on the net.

I honestly learned the most by reading the dojo and dijit source. I might be weird though.

Good luck!

ISO/OSI is a comprehensive architecture for networking. TCP/IP are the protocols that are actually used in the internet. One can view TCP/IP as a (partial) implementation of OSI/ISO, but, IMHO, while valuable conceptually I feel you're better off studying TCP/IP. In addition ISO/OSI doesn't specify an API like sockets which you need to write programs.

I'd suggest to work on analyzing and designing before coding.

Analysis is about breaking down the problem (the use cases the software needs to fill).

Design is about building a solution out of components, assigning responsibilities to those components and identifying their relationships.

My rule of thumb is: if what I'm about to code is complex enough that I have no idea how I'll piece it together, I'm not ready to code yet.

A whiteboard or a sketch pad and basic diagram drawing skills are really useful. The point isn't to draw a blue print, it's to sketch out ideas about how to articulate your components and to gain insight on the hard parts through visualization.

The challenge is structural (how many classes? whose method is this? composition or inheritance?) and dynamic (A calls C, which calls B, which asynchronously calls X… is this optimal?).

I've really enjoyed Larman's book on Object-Oriented Analysis and Design. The title sounds much more narrow than the actual subject matter.

Javascript: The Good Parts

and
Javascript: The Definitive Guide

I use the Definitive guide as a reference book, but if you have the patience and want to learn, definitely a good read.

Things may have advanced since I was doing it, but back then you would learn lex and yacc and then look at examples of existing code to figure out how to do things. I've never read "Structure and Interpretation of Computer Programs" (also known as "The Wizard Book"), but I have seen it get rave reviews decades after decade and it is still a popular book after more than 30 years so I would guess that would be a good one to start with if you want some more in-depth reading.

rjett's excellent list and

DOM Scripting really helped me get my head around JS and the DOM. Once I grokked all that book had to offer moving to and understanding jQuery was a snap.

Bulletproof Ajax was an excellent follow-up to Keith's DOM Scripting.

If you want to know how interpreters/compilers work:

• http://www.craftinginterpreters.com
  
  
• https://www.amazon.com/Compilers-Principles-Techniques-Tools-2nd/dp/0321486811
  
  
• https://github.com/jamiebuilds/the-super-tiny-compiler
  
  
• https://ruslanspivak.com/lsbasi-part1/
  
  Bonus: http://journal.stuffwithstuff.com/2011/03/19/pratt-parsers-expression-parsing-made-easy/
  
  Edit: have fun!

I'm in a similar boat to you. I studied Computer Science at university but it was a really watered down curriculum (we even did Excel as one of our first year modules for fuck's sake; I was so desperate to code that I made a VBA frontend haha), so there are many gaps in my theoretical knowledge.

I'm currently reading MIT's Structure and Interpretation of Computer Programs. It's based upon Scheme, a dialect of Lisp, but covers many important topics, such as:

• Tree recursion
  
• Hierarchical sequences
  
• State, mutability, and immutability
  
• Streams
  
• Compiler design
  
  Now I just need to find more time to read it!

If you're already an experienced programmer, then I recommend The C++ Programming Language by Bjarne Stroustrup. Stroustrup is the guy who created the language, so this book is the most comprehensive and most authoritative you'll find short of reading the language standard itself.

Or, if C++ feels just a bit too foreign, you could also read Programming: Principles and Practice Using C++, which is also by Stroustrup, but was written to be a college text. It takes its time a little more, and it includes drills and exercises... essentially self-study homework problems to help you get familiar with using the language well.

Refactoring: Improving the Design of Existing Code

Clean Code

The Clean Coder

Professional JavaScript for Web Developers. Zakas is one of the best.

I'm not a huge fan of Haskell. It's big features like laziness, "no side effects" (performUnsafeIO is everywhere), and (to a lesser extent) immutable everything are generally at odds with the real world. If you are willing to work through those, it makes fast code.

SML with mlton or similar is a better flagship for lambda calculus languages. Like all GC'd languages, it loses by a little to the low-level C ones in the general case. Compared to other GC languages, it's very competitive.

https://www.amazon.com/Implementation-Functional-Programming-Prentice-hall-International/dp/013453333X

Amos Haviv is releasing the second edition of MEAN Web Development on July 6th. I have the first edition, and it was terrific at teaching the basics plus CRUD modules, login/authentication, and Socket.IO. The first edition used Angular 1, and the second edition uses Angular 2. I'm assuming it will contain all of the same elements as the first edition, just using Angular 2 instead. Highly recommend!

Amazon

EDIT: This book doesn't have an example with different user roles, but it wouldn't be difficult to modify the project you make to include them.

Absolutely. I'd say learn programming first via Scheme or Ruby, then go back and learn JavaScript.

Though actually, "JavaScript, The Good Parts" is a pretty tough read even with a computer science background. Good book, but extremely terse. Expect to take half an hour to understand some of the pages...

Evaluating what we define as quality in software engineering is sadly not a single equation. There is a whole area of research around it: wikipedia https://en.wikipedia.org/wiki/Software_quality can give you a good introduction.

If you are passionate about software quality, you should totally investigate Kan's work, it is often cited as a reference book. https://www.amazon.com/Metrics-Models-Software-Quality-Engineering/dp/0201729156/ref=sr_1_1?s=books&ie=UTF8&qid=1519862842&sr=1-1&keywords=Metrics+and+Models+in+Software+Quality

It offers quite a lot of different metrics to consider.

This may sound old fashioned, but maybe this classical book "Introduction to Algorithms" by Cormen et al is the way to go.

I myself learned by another book, "Algorithms and Programming: Problems and Solutions" by Alexander Shen, which was way thinner. Just read it through and solved like 50% of the exercises in C, Java, or Perl.

i liked high performance javascript by nicholas c. zakas.

I'd like to add one: Test-Driven JavaScript Development

I would recommend looking into Domain Driven Design (DDD). A book a lot of people recommend is Domain Driven Design by Eric Evans but sometimes it's hard to translate the examples in the book to something you can apply in JavaScript. However you can probably find articles about DDD in JavaScript if you google for it.

The use of standard Alert/Confirm prompts is a crappy practice in itself. This just redesigns bad behavior. Nowadays is expected that an application can inform the user without disrupting his user experience; you can use a notification area, fading messages, or things like growl on the Mac. If you need confirmation to carry on an action (like delete) you can let the user do it without asking anything and give him an "Undo" feature. Users don't read dialogs anymore. A good read on this is the book "Don't make me think" by Steve Krug.