Giter Site home page Giter Site logo

Comments (3)

QuickBASIC avatar QuickBASIC commented on May 8, 2024 1

No, I think it's fine now that I understand the intent. Why/How/What for the chapter order makes a lot of sense now that you put it this way. I know you said that the second chapter was going to be edited, but I was just concerned that even though the topics were not as complex as chapter 3, it was still a bit information dense because it listed all the command line options and started delving into the CLI.

I'm eager to see the updated chapter, so I can provide feedback though.

from monerobook.

xmrhaelan avatar xmrhaelan commented on May 8, 2024 1

Makes sense to me too, although part of me wonders if the How should be at the very end...

from monerobook.

serhack avatar serhack commented on May 8, 2024

Proofreader response

I removed a lot of the redundancy in the first two chapters already, and have a flow in mind for the third chapter that should smoothly conceptually transition.

As it stands, here is the approach I have been taking for key principals of each chapter:
Chapter 1) WHY to USE Monero (nontechnical, for general audience)
Chapter 2) HOW to USE Monero (nontechnical, for general audience)
~ somebody who has never heard of Monero prior to reading this book should be able to read up to this point and know everything about how to practical use Monero on a day-to-day basis ~
Chapter 3) HOW Monero WORKS (semi-technical, starting to dig into the crypto concepts)

You can see in my introduction of the second chapter that I use the first paragraph or two to help the reader orient where they are in the book and what they will learn from this chapter. By including the guideposts in each of the first three chapters, referencing the other three chapters, people who are already familiar with using Monero wallet should be able to see clearly that they can skip chapter 2.

I think it might be better to not flip the chapters, when I think about it from the perspective of both types of reader.

% Advanced reader - will easily know that they can skip over chapter 2, will not get confused.
% Novice/naive reader - will probably find the book more approachable in the current order, with easy concepts and practical tools before the complicated unnecessary cryptography information. If we switch the chapters, our novice readers may become overwhelmed by not understanding the cryptography details and may give up on Monero before getting to the easy wallet introduction. I like the current order because it allows us to make it very clear that you can use Monero without being a cryptography genius, which is a common misconception that scares a lot of people away.

from monerobook.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.