Sofus Albert Høgsbro Rose
bd6c8d859f
This is a cleanup to make the book ready to be widely worked on by a team. The sidebar was cleaned up, an intro page was written, and run.py app was fixed. |
||
|---|---|---|
| .. | ||
| README.md | ||
| conclusion.md | ||
| execute.md | ||
| files.md | ||
| foss.md | ||
| http.md | ||
| markdown.md | ||
| passwords.md | ||
README.md
To be written...
The purpose of this section is to give a quick, readable summary of all the "stuff any person who needs to use software as a tool should know", which is rarely (if ever) covered in one go.
- What's a file? What's a filesystem?
- What are the basic principles of keeping secret secret? Why do passwords suck? What can one do?
- What is a "binary"? What does "executing" mean? Why does Python not make "double-clickable" files? How does it work instead? What does that mean for sharing my code?
- What's an "IP"? What does it mean to "buy a website name"? What does "trust" mean when using the internet? What's an "HTTP", and what what are the basics of interacting with ex. remote data files?
- Who owns code, when? What does "own" even mean? If I want to use someone's code, when am I allowed to do that? When I use other's code, what do I have to do wrt. attribution, citation, etc.? Which general kinds of abilities / freedoms might I be interested in buying, or insisting on (if I got the software without paying), when using other's software?
- What does "text" mean, and what do you mean
.docxisn't text? What methods of formatting raw text can I use can I use to express myself using text? - What are some practical, career-boosting ways of thinking about software, when software isn't what I want to do with my life? What are some examples of non-obvious abilities I'll have, which my colleagues won't?