Design Patterns VS wtfjs

After that, more practice, and then Design Patterns (as in the famous book of the "Gang of Four": "Design Patterns: Elements of Reusable Object Oriented Software"). Here I'd recommend "Head First: Design Patterns" and Java Design Patterns as well as Refactoring Guru (the sites are more reference than course).

For Design Patterns - any resource recommendation that misses Java Design Patterns and Refactoring Guru (also for Refactoring) as well as *Head First: Design Patterns, has failed.

A massive list of design patterns and how they could be implemented (in Java) can be found here.

https://java-design-patterns.com/ has example code for things like object pools that can help with memory management.

Sidenote: I would not really use the GoF Design Patterns book anymore. Too dry. I would use "Head First: Design Patterns" - much more modern, much easier to read, or Refactoring Guru or Java Design Patterns (uses Java, but again, only for illustrations).

Also: https://java-design-patterns.com and https://refactoring.guru/design-patterns

Use either Java Design Patterns or Refactoring Guru. Both resources are far higher quality than yours.

Java Design Patterns

Java Design Patterns - IMO one of the most accessible sites with very easy explanations

A hint: go to Java Design Patterns and go through the patterns to figure what could fit.

Me in the interview: "Generally, no, a variable can only be assigned one numeric value at a time. However, Javascript is famous for unpredictable behaviors in variable comparison statements, for instance [] == ![]. There's actually a whole library built around documenting this type of behavior this for comedic value, and other more serious libraries geared towards solving the problem. So it's possible that some obscure variable assignment scenario would result in that line evaluating as true, but it's not something you'd expect to encounter in the real world. This has gotten a lot better with typescript and es2022, but still something you need to watch for a bit."

I do see that point of view, didn't think of that, there are some aspects of go which are a bit weird if you never touched lower abstraction languages, yet once you learn what they are, you are all set and you can code in anything. go has the least amount of gotchas I have seen in any programming language. compare it with loads of the weird stuff javascript does https://github.com/denysdovhan/wtfjs and go is like heavenly lol

Its a very poorly designed language. Its syntax and semantics are often confusing and unpredictable. There is no well defined mental model of how constructs work in this language.

WTF JS

😎 A great guide to Javascript that is both simple and wonderful, but also difficult and fun that seems like bullshit. -> wtfjs