design-patterns-for-humans VS Java

2. Design patterns for humans

For the first point, what really helped me is taking a look at the various design patterns that are usually used. However, do not force a design pattern into code, it should come naturally to you which pattern fits to a problem. A great resource I can recommend is the README.md file on this GitHub project.

I'd recommend reading gang of four design patterns https://github.com/kamranahmedse/design-patterns-for-humans

If you want to learn more about design patterns, don't forget to take a look at Design Patterns for Humans, it's an incredible repository with many interesting examples that you can apply when you want to use a design pattern to solve a specific problem.

Ideally, we would write a facade for those methods and provide an API like:

https://github.com/kamranahmedse/design-patterns-for-humans#-singleton

yeah I agree. I think it's because they pretty much allow contributions of algorithms from various people and the code review standards are not super high. I recall at one point the BFS algorithm in Java actually used an ArrayList (roughly equivalent to std::vector) for the queue, which is silly because popping from the front is O(N), so I had to submit a fix for that:

https://github.com/TheAlgorithms/Java/pull/3231

but I agree that basic low-hanging issues like this (and the exponential-time fibonacci that another commenter pointed out) really prevents me from taking this repo very seriously

here you can use of the ciphers

I would start by learning about base class libraries: What is java and then study how some algorithms might be implemented by looking at this repository