Before diving into any of the data structures, readers should be reminded of two fundamental laws in software architecture:

1.Everything is a trade-ff
2."Why is more important than the how"

So, readers face the nuances and reality of these data structures from the beginning. These two laws are coined by two thought leaders in software architecture: Mark Richards and Neal Ford. They have explained these two laws in various conference talks and books. For example, here you can read about these two laws here:

https://www.infoq.com/podcasts/software-architecture-hard-parts/


Also, here is a book for reference:
https://a.co/d/fKOodW9

Co-authored-by: Oleksii Trekhleb <3000285+trekhleb@users.noreply.github.com>

Co-authored-by: Oleksii Trekhleb <3000285+trekhleb@users.noreply.github.com>

* Add ignore patterns to eslint config

* Improve UK translation for LinkedList

---------

Co-authored-by: Oleksii Trekhleb <3000285+trekhleb@users.noreply.github.com>

* feat: LRU cache translation in ko-KR

* chore: add readInAnotherLan for ko-KR

---------

Co-authored-by: Oleksii Trekhleb <3000285+trekhleb@users.noreply.github.com>

Co-authored-by: Oleksii Trekhleb <3000285+trekhleb@users.noreply.github.com>

Co-authored-by: Oleksii Trekhleb <3000285+trekhleb@users.noreply.github.com>

Co-authored-by: Oleksii Trekhleb <3000285+trekhleb@users.noreply.github.com>