Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

could you make it any harder please? #11

Open
kimballjohnson opened this issue Aug 1, 2019 · 1 comment
Open

could you make it any harder please? #11

kimballjohnson opened this issue Aug 1, 2019 · 1 comment

Comments

@kimballjohnson
Copy link

kimballjohnson commented Aug 1, 2019

You know, it's very hard to jump back and forth between a book page on screen and the code and match up all the ways different authors refer to and explain away about tech issues using their own manner of speech and way of thinking.

But when they take the source and fragment it and stuff it into a hundred or more folders buried six and seven layers deep, it's really beyond understanding!

If you have to maintain every step as a separate branch rather than just building a single version of your example, layer by layer that matches the flow of the instructions in your book, then please keep your source in top-level folders only, each one containing the source for each branch (checkpoint? - you have to invent nomenclature?).
It took me over an hour to unwind it correctly!!

UnscrewedVersioning

@chandermani
Copy link
Owner

I agree with your problem @kimballjohnson. Single companion download does not work.
I would instead suggest you use the git repo with branches which does not come with these complexities.
The github branches (checkpoints) help the reader to compare and understand how the application has evolved, with the added bonus of starting afresh from a new checkpoint if one gets stuck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants