Moving book bits about

calaldees · calaldees · commit 716053c18435 · 2025-08-19T15:34:42.000+01:00
Considering top level structure? This book is a long long long long way off
diff --git a/Makefile b/Makefile
@@ -1,16 +1,8 @@
-# TODO: BROKEN - REMOVE This trash
-
-#CI_COMMIT_REF_NAME   ?= $(shell git symbolic-ref --short -q HEAD)
-#CI_COMMIT_SHORT_SHA  ?= $(shell git rev-parse HEAD | cut -c 1-8)
-
-DOCKER_IMAGE:=teachprogramming:latest
-
-build:
-	docker build \
-		--tag ${DOCKER_IMAGE} \
-	.
-
-.PHONY: example
-example:
-	python3 teachprogramming/lib/make_ver.py teachprogramming/static/projects/game/tron.py --ver_name base4
-	python3 teachprogramming/lib/make_ver.py teachprogramming/static/projects/game/tron.py --ver_name base4 --ver_prev base3
+.PHONY: run
+run:
+	${MAKE} --directory teachprogramming/lib
+
+.PHONY: test
+test:
+	${MAKE} --directory teachprogramming/static/language_reference
+	${MAKE} --directory teachprogramming/lib/verify_snippets
diff --git a/book/ActualCode.md b/book/ActualCode.md
diff --git a/book/CodingTruths.md b/book/CodingTruths.md
@@ -4,7 +4,7 @@ Coding Truths
 * All computers can do is compare 2 numbers (or a single character)
     * Everything you ever write always comes down to this
 * Your confidence level wont change
-    * It's part of you. Every time you get more competent, you can now conceptualise the complexity of more complex stuff
+    * It's part of you. Every time you get more competent, you can now conceptualize the complexity of more complex stuff
     * [List of algorithms](https://en.wikipedia.org/wiki/List_of_algorithms)
 * You will code things 3 times
     * The first to understand the problem - The first time you solve anything it is rubbish
@@ -15,4 +15,4 @@ Coding Truths
 * You cant rush code
     * It's just impossible - it's not like an essay - you cant rush correctness
     * When you reach mental fatigue, more time wont solve the problem
-    * 4 times longer than your estimate
+    * Things take 4 times longer than your estimate
diff --git a/book/README.md b/book/README.md
diff --git a/book/_unsorted.md b/book/_unsorted.md
diff --git a/book/age.md b/book/age.md
@@ -1,5 +1,5 @@
 Age: When is too young?
-=======================
+-----------------------
 
 Summer code club workshops
 
diff --git a/book/autonomy.md b/book/autonomy.md
@@ -4,6 +4,15 @@ Learner Autonomy
 Largely the punchline of the BarCamp 2024 talk
 
 
+#### Game-ification is counter to autonomy
+
+* Game-ification of content erodes autonomy and should not be used
+  * > You get 50 stars if you complete this exercise - you have 279 stars currently - your next level of silver is at 300 stars
+  * This is not developing intrinsic motivation and puts the leaner as a controlled subject rather than developing there own autonomy
+  * I would consider this strategy over the long term dangerous.
+
+
+
 'Be creative' an art analogy
 ----------------------------
 
diff --git a/book/gamification.md b/book/gamification.md
@@ -1,6 +1,17 @@
 Gamification
 ============
 
+
+#### Game-ification is counter to autonomy
+
+* Game-ification of content erodes autonomy and should not be used
+  * > You get 50 stars if you complete this exercise - you have 279 stars currently - your next level of silver is at 300 stars
+  * This is not developing intrinsic motivation and puts the leaner as a controlled subject rather than developing there own autonomy
+  * I would consider this strategy over the long term dangerous.
+
+
+
+
 https://replicube.xyz/
 
 blooket
diff --git a/book/hackathon.md b/book/hackathon.md
@@ -5,7 +5,7 @@ I can't think of anything more human and amazing than a hack day. However; many
 This is my notes on what the pitfalls are and how to do it with some degree of success.
 
 * Prerequisites
-    * Before you decide to run one - go to one (if you are not a technologist but an organizer, still attend and observe the event) - preferably 3 of them and speak to some of the attendees and organizers.
+    * Before you decide to run one - go to one (if you are not a technologist but an organizer, still attend and observe the event) - preferably more than one of them and speak to some of the attendees and organizers.
     * If you don't understand the event, how will you convince people to attend? If you do convince people to attend, they will probably have the wrong skill-set because you did not understand the event yourself.
     * Understand the skills your attendees will need in able to produce something meaningful (see curriculum below)
 * Routes/Themes/Style
@@ -26,8 +26,8 @@ This is my notes on what the pitfalls are and how to do it with some degree of s
     * Social - food pizzas in the evening - present on Sunday lunchtime to a wider set of spectators
     * Stop the pests - don't let non skilled people wonder and distract the hackers from the focus of the event. Have the metal to ask people to move to the separate 'party room' or leave
 * Prerequisite skills of attendees
-    * Never processed data before, never created a dynamic webpage, never ...
-    * Demo
+    * If your attendees have never processed data before, never created a dynamic webpage, never xyz, then how will they learn all the skills to do that AND create something in the compressed time. It would be difficult to create the thing in that time period, let alone learn the skills as well
+    * Demo implementations (to convey tech and what is possible):
         * Heatmap on maps
         * Google sheets for storage
     * You may need multiple months of crash course session leading up to the event to demo and develop skills for processing real data
@@ -36,13 +36,13 @@ This is my notes on what the pitfalls are and how to do it with some degree of s
     * They need to see the output of a real hack day to see what's possible and whats expected
     * You need 20% of your attendees minimum to know what they are doing and be role models for what is possible and model the approach
     * The reality is that most young people (even studying computing) will not have the skills required for this by just attending their course. Actually producing something practically in a constrained time and in a team is not the same as passing an exam or doing coursework.
-    * The reason why people applaud and clap is because its genuinely impressive what people can do in 24 hours. If you don't have enough understanding of what development is, you won't know how amazing it is, you will just clap hollowly. There is a real difference of an audience in awe and and just some hollow noise
+    * The reason why people applaud and clap is because its genuinely impressive what people can do in 24 hours. If you don't have enough understanding of what development is, you won't know how amazing it is, you will just clap hollowly (or worse clap when the achievement is minimal). There is a real difference of an audience in awe and and just some hollow noise
     * Have a local community of people building projects (BarCamp)
-    * going from zero to hack day is not possible
+    * Going from zero to hack day is a recipe for problems
     * Quality - Your event is only as good as your attendees. Weak attendees == Weak event. This is not an event for "everyone". Trying to involve everyone blindly will create problems.
-    * Social media is good for raising the profile of your event, but it will not attract your skilled attendees. Your mindset should be a 'recruiting' skilled attendees. (look at the curriculum list below). If you can't find them, you need to make them, and that process could take years of support sessions before you run your first hackathon. Maybe your first hackathons are only with a small selected cohort of 12 people as a test?
+    * Social media is good for raising the profile of your event, but it will not attract your skilled attendees. Your mindset should be focused on 'recruiting' skilled attendees. (look at the curriculum list below). If you can't find them, you need to make them, and that process could take years of support sessions before you run your first hackathon. Maybe your first hackathons are only with a small selected cohort of 12 people as a test?
 * You can have good intentions and have an inverse effect
-    * coding is hard - "anyone can code" is bullshit. If you open up a hack day for everyone you could just demoralize the weak attendees
+    * coding is hard - "anyone can code" is bullshit. If you open up a hack day for everyone you could just demoralize the weak attendees as they wont be able to produce anything
     * Unskilled attendees hurt the event - they provide distractions
     * Anyone that thinks "just run a hack day" is going to have a disappointing event and even put people off attending any future hack days organized by other people that might be good. Beware of the damage you can cause.
     * A related example
@@ -51,6 +51,7 @@ This is my notes on what the pitfalls are and how to do it with some degree of s
     * You know the winners (everyone wins because you've got a great set of awards). Contact them individually about the next event. Show you're aware of the hack they did. Make them feel valued and remember and that their contribution was important. You can have a template and notes from the previous year and back these out in an hour to 30 people.
 * Publish the results and have awards
     * Many young people use these days as CV material. Have a public website that describes each of the hacks and showcases them. This leads to the value of years of accolades enshrined on a page that can be linked to for years (see length in the game above)
+        * Have a plan for the long term support of these urls. It helps SEO and young people cite the achievement for years.
     * When you judge the awards - it's not dragons den. Award creativity, skill, approach, passion
     * It is NOT competitive. Participation is the key. I advise against awards like "Best in Show". I also advice against meaningless awards "Most likely to go to the moon".
         * Some ideas "Best Technology", "Best Team", "Local Hero's"
@@ -114,7 +115,11 @@ With that in mind, here is a of core skills to allow that to happen.
     * pandoc (document conversion)
 * graph generation
     * on any platform (Plotly? Chart.js?)
+    * Put data on maps
 * bash ssh and understanding of commandline
+* Data handling
+    * Get data from non technical users (input) (Google sheets as datastore trick)
+
 
 ### Commentary
 
@@ -125,7 +130,7 @@ I would say that 50% of your attendees needs to have the capacity to create even
 
 Realize what is required.
 
-I you do not understand what the items are above, then you will not in a position to recruit the right people or be in position to help them build the relevant skills in preparation for the event.
+I you do not understand what the items are above, will you be able to recruit the right people or be in position to help them build the relevant skills in preparation for the event?
 
 
 ### Suggestion
@@ -140,8 +145,8 @@ I you do not understand what the items are above, then you will not in a positio
         * whenever anyone walks into a toilet it plays the mario bros entering a pipe sound effect
 
 
-References
-----------
+History
+-------
 
 * 2024? I was asked for advice on setting up a hackathon for girls with local schools and undergrads. I waxed lyrical about my advice and wrote this document.
 * 2025 I was asked about running a hackathon and significantly enhanced this document
diff --git a/book/identityComesBeforeSkill.md b/book/identityComesBeforeSkill.md
@@ -0,0 +1,14 @@
+Identity Comes Before Skill
+---------------------------
+
+
+
+From BarCamp 2024
+### Identity Comes before skill
+
+* Example: "The guitar kid"
+* We get satisfaction from doing things we are good at
+  * todo (cite job satisfaction survey/research) - compounding identity
+
+
+![[age]]
diff --git a/notes.txt b/notes.txt
diff --git a/requirements.txt b/requirements.txt
diff --git a/teachprogramming/static/language_reference/languages/javascript/files.js b/teachprogramming/static/language_reference/languages/javascript/files.js
@@ -0,0 +1,7 @@
+// TODO
+
+// caniuse.com - FileReader FileWriter
+
+//local file access
+//http://stackoverflow.com/questions/371875/local-file-access-with-javascript
+
diff --git a/teachprogramming/static/projects/language_features/python/data_containers.md b/teachprogramming/static/projects/language_features/python/data_containers.md
@@ -0,0 +1,13 @@
+
+
+TypeDict
+dataclass
+NamedTuple
+
+TypeDict
+[NotRequired](https://docs.python.org/3/library/typing.html#typing.NotRequired)
+
+[python dataclasses with optional attributes](https://stackoverflow.com/a/72582101/3356840)
+> It's not possible to use a dataclass to make an attribute that sometimes exists and sometimes doesn't because the generated __init__, __eq__, __repr__, etc hard-code which attributes they check.
+> However, it is possible to make a dataclass with an optional argument that uses a default value for an attribute (when it's not provided).
+
diff --git a/teachprogramming/static/projects/mini/isEven.md b/teachprogramming/static/projects/mini/isEven.md
@@ -0,0 +1,19 @@
+
+```python
+# This sucks
+def isEven(i: int) -> bool:
+    """
+    >>> isEven(1)
+    False
+    >>> isEven(2)
+    True
+    >>> isEven(3)
+    False
+    >>> isEven(4)
+    True
+    """
+    if i == 0: return True
+    else if i == 1: return False
+    else if i == 2: return True
+    else if i == 3: return False
+```
