I was thinking it would be nice to have the whole "book" into one file.

What if we write a little script to go through a folder and pack all of the .mds into one master .md or a pdf of whatever else? We could even add that as a build task so for every build we export a new final version.

How do I actually get the epub version to download? The gitbook link requires an account AND a phone number. Is that the only option?

Links here are broken, nothing happens when you click them. Consecutively, pdf, mobi and ePub versions are only 13 pages long.

I asked this already in the calibre community:
isn't there a tools to compile the .md strukture as one ebook?

Hello! Thank you so much for open sourcing and maintaining this great guide!

The link on the README for PDF export appears to be broken and sends the user to the GitBook homepage.

Medium.com is the perfect place for this material to be. It has awesome reader experience and gives the ability to highlight and comment anything. You could provide a link to each medium post in the README.md

What do you think?

Currently we have 1.11 "How to Learn Design Skills", and I think getting an understanding of well-designed software is very important (especially as a beginner), but should we look to include a section later on (perhaps in Intermediate) on when to use (and not use) design patterns? Currently 1.11 makes no mention of them and even having an awareness of them can be beneficial.

Where appropriate, it will be worth including further reading/resources on a given topic

Most of the enterprises using the same technique to implement so don't you think we should add this section too?

Hello,

Even though this is still being worked on, I would love if there was a way for me to read this offline on my kindle.

Regards,
BRP

in 3-Advanced/Technical-Judgement/03-Choosing Languages.md
the phrase "Its possible that some of the modules are actually up-to-date." is very vague. Isn't it always possible they are up to date? What does language have to do with it?

In the intermittent bugs chapter, the name you called the tool you used -- the French stripper -- looks like an example of the kind of thing that, while it seems intended innocuously, could alienate women. This is otherwise an amazing introductory text, and our industry has a real problem with welcoming both women and men. Consider changing?

Hi, I think you can moveing you book to a GitBook version.

It will be more easier reading and writing:

https://github.com/GitbookIO/gitbook

It appears that a link was meant to be included in the section on Abstraction. This is denoted as [PGSite]

https://github.com/braydie/HowToBeAProgrammer/blob/master/2-Intermediate/Personal-Skills/05-How%20to%20Balance%20Brevity%20and%20Abstraction.md

As per @xmalinov - #45 (comment) for keeping translated versions of the guide in sync

HowToBeAProgrammer/2-Intermediate/Personal-Skills/02-How to be Widely Trusted.md

First line should read "To be trusted you must be trustworthy. You must also be visible. If no one knows about you, no trust will be invested in. Rather "To be trusted you must be trustworthy. You must also be visible. If know one knows about you, no trust will be invested in "

Love your stuff guys 👍 :)

Is that a good idea to translate it? IMHO, it would be interesting in Russian (or Chinese)

If not, then delete this issue-comment.

Change the title to HowToBeAnEmployee or even HowToBeAnEmployeeInCompaniesWithLargeGlassWallsForWhichThereAreNoPeopleButEitherResourcesOrClients

I have begginer so I learn to languages

Should there be a small note here that these systems are also called version control systems since this is in the beginner section and a beginner could be confused by the different naming conventions?

You don't need this much explanation for this xD, i cant stop laughing. I can tell 5 steps to be a programmer

1. Get familiar with a code editor
2. Learn a basic language fully if it's hard schedule it
3. Do a project yourself
4. Go outside 
5. Brag your a programmer

As mentioned from this(#45) comment, Korean translation exists already (https://wiki.kldp.org/wiki.php/HowToBeAProgrammer). It is stored in wiki page using Korean, however I believe that copying from it to here is valuable enough for everyone.

Only I worried is the copyright; it uses GFDL compared to the cc-by-sa used in here. Is this possible to copy to here?

This repository is a good idea ! I think you should add some examples to illustrate each chapters.

could you please convert all of the content into one single PDF file? thanks!

Give me some tips to gain an knowledge in the basics of programming that you know. Stay tuned !!

I was wondering why touch typing has been put in intermediate chapter. It's almost indispensible to be a touch typer regardless of whether you are a programmer or not. I have enough programming and interpersonal things to navigate as a newbie programmer, if touch typing was one of them then it would add to my burden.