flythereddflagg / flythereddflagg.github.io Goto Github PK

Current projects include the Redd Python book

Home Page: https://flythereddflagg.github.io//python_book/site/

HTML 80.12% Python 1.85% Jupyter Notebook 14.31% Makefile 0.14% TeX 1.03% JavaScript 2.53% Batchfile 0.01% PowerShell 0.02%

python learning-python learning-by-doing book computer-science-education introduction-to-programming introduction

flythereddflagg.github.io's Introduction

flythereddflagg.github.io

I am Mark Edward Redd. Below are links to information about some of the open-source projects I am working on.

Projects

Mark Redd's CV: A website showing my CV
The Redd Python Book: A free book to teach beginners about Python and introductory computer science
The Python and C implementations of the Leapfrogging Optimization Algorithm published by Dr. R. Russell Rhinehart
TBA

flythereddflagg.github.io's People

Contributors

Stargazers

Watchers

Forkers

jhogge

flythereddflagg.github.io's Issues

Add PEP 8 info to names and variables

https://www.python.org/dev/peps/pep-0008/#naming-conventions

add naming conventions reference to names and variables section

minor discrepancy between code and print-out in chapter 7

Minor issue, but there's a discrepancy between the code and the print-out of chapter 7 "Escape Characters." Specifically, the code says:

print("Here is a greek eta character: \u03b7")

But the print out reads:

Here is a funny character: η

Math not rendering

https://flythereddflagg.github.io//python_book/site/12-Math-and-Data/#hone-your-skills

inline math does not render on second exercise

Remove dashes between navigation on each page.

there are dashes on each page that must be removed so the viewer sees

Previous: 09 Variables and Memory | Table of Contents | Next: 11 Input and Output

in stead of, currently:

Previous: 09-Variables-and-Memory | Table of Contents | Next: 11-Input-and-Output

ch. 10 - needs more explanation before the code

Ch. 10 - Better String Formatting jumps into the code very quickly. I recommend adding another sentence or two before the code to help the reader know what you mean and what to look for in the code.

Shorten all code blocks so that any line does not exceed 72 characters in length

Shorten all code blocks so that any line does not exceed 72 characters in length
Also ensure all line numbers are working.

I'm not sure if there's an easy way to do this in github.io, but you might consider adding a glossary for terms that could help readers understand Python-specific (and even programming-specific) terms. Words like "concatenate", etc.

I'd recommend the same, but for acronyms as well.

ch. 14 - vague advanced mastery exercise

I would recommend giving the reader some more guidance for the ch. 14 advanced mastery exercise than "There is a problem in the above script if_else.py that can cause errors if we're not careful." This implies that you purposely put a faulty script up there, which may reduce reader confidence in the author? I don't know, it just seemed kinda vague when there could be a really powerful lesson to be learned. Maybe give a hint?

General: add links to ch. 4 throughout the book

Since the assumption is that the reader is new to Python, I recommend adding links to ch. 4 (writing your first script) throughout the book, especially near exercises where you ask the reader to write a script.

Something like: "Stuck? Refer to Chapter 4-hyperlinked for writing and running a script."

There may be other exercises later in the book where you could really help the reader out by encouraging them to revisit previous chapters.