DEV Community

Lucas Schiavini
Lucas Schiavini

Posted on • Originally published at lucas-schiavini.com on

📖 How to Read a Book

📖 How to Read a Book

Some tips I've gathered along my way:

  • From The Boron Letters: Read a book first for the enjoyment of it(which means if you lose curiosity with it as time goes on, just drop the book and pick it up later if that curiosity ever comes back).
  • The second read of the book means taking notes along the way, I use the Zettelkasten Method for that and put on my second brain on Obsidian.
  • As you take notes, feel free to write important lessons from the book into a blog post or notepad, even if you never publish it.
  • If the book Blew your Mind, reread it every couple of years. Compare your understanding of the previous reads with the new ones(notes help with this).

That's it so far, but I'll have more tips after I read "How to Read a Book" by Mortimer J. Adler.

That is it and I will see you at the next one 😁

Image of Datadog

The Future of AI, LLMs, and Observability on Google Cloud

Datadog sat down with Google’s Director of AI to discuss the current and future states of AI, ML, and LLMs on Google Cloud. Discover 7 key insights for technical leaders, covering everything from upskilling teams to observability best practices

Learn More

Top comments (0)

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay