You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/computationalThinking.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ Educators that can't actually build software tend to emphasis the wrong foundati
16
16
This leads to loss of trust (especially as learners become more advanced/capable in the later teenage years. They can sniff the bullshit and detach from education rather than just obeying continuous instructions).
17
17
I would wager that "Computational Thinking" has been responsible for increased disengagement with Computing.
18
18
I actually think it has done harm to the subject.
19
+
This is another example of how education is abstracted from the rest of the world.
19
20
20
21
I asked a table of professional developers, without context, "what is 'Computational Thinking'". None of them could answer. They got as far as "Thinking like a computer" and moved on to talking about the capabilities of AI.
* Discover how to create and use variables that aren't inside of an object hierarchy. Learn about "functions," which are like methods but more generally useful. Prerequisite: Any course that used the term "abstract base class."
7
+
* CSCI 3300: Classical Software Studies
8
+
* Discuss and dissect historically significant products, including VisiCalc, AppleWorks, Robot Odyssey, Zork, and MacPaint. Emphases are on user interface and creativity fostered by hardware limitations.
9
+
* CSCI 4020: Writing Fast Code in Slow Languages
10
+
* Analyze performance at a high level, writing interpreted Python that matches or beats typical C++ code while being less fragile and more fun to work with.
11
+
* CSCI 2170: User Experience of Command Line Tools
12
+
* An introduction to UX principles as applied to command line programs designed as class projects. Core focus is on output relevance, readability, and minimization. UNIX "ls" tool is a case study in excessive command line switches.
13
+
* PSYC 4410: Obsessions of the Programmer Mind
14
+
* Identify and understand tangential topics that software developers frequently fixate on: code formatting, taxonomy, type systems, splitting projects into too many files. Includes detailed study of knee-jerk criticism when exposed to unfamiliar systems.
The group need to appreciate and understand each others time and achivements. The outside world is of little consequence. The organisations approval is of little consiquence.
6
+
* The problem is all new young people will envisisage VR, AI, MMORPG's, Hacking. They don't get exited about 'binary to hex conversion'
Copy file name to clipboardExpand all lines: book/hackathon.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ This is my notes on what the pitfalls are and how to do it with some degree of s
9
9
* 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.
10
10
* Understand the skills your attendees will need in able to produce something meaningful (see curriculum below)
11
11
* Routes/Themes/Style
12
+
* (just having 'anything goes' is to vague. If groups are too disparate, Attendees will wonder about the value of the gathering and wonder if they should have just done it themselfs. There is no way for them to feel part of something bigger, or identify the skill that was demonstrated by the other teams because eveyone worked on very differnt domains.)
12
13
* Creative route
13
14
* Demo-scene Font greets
14
15
* Demo-group Team
@@ -48,11 +49,13 @@ This is my notes on what the pitfalls are and how to do it with some degree of s
48
49
* A related example
49
50
* ICT club for girls in 2004 was just an embarrassment - purple spreadsheets about ponies.
50
51
* If the event can run regularly for 3 years, you will have enough snowball momentum for work of mouth to attract more people. What could be important is the length of time the event has been established. Potentially you may have you first 2 years as a buildup for the 3rd+ year being productive.
51
-
* 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.
52
+
* You know the attends from last year (everyone wins some kind of special mention/award because you gave 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.
53
+
* The longer your event runs, the more meaningful and prestige the event holds (both internal and external). Organizations should be aware of the long term horizon can actively fight to keep the pattern/event going.
54
+
* Can the organization commit to minimum of 3 years? can the organization name and identify a member of staff to be responsible. If that member of staff leaves, ensure there is a plan to pass the torch.
52
55
* Publish the results and have awards
53
56
* 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)
54
57
* Have a plan for the long term support of these urls. It helps SEO and young people cite the achievement for years.
55
-
* When you judge the awards - it's not dragons den. Award creativity, skill, approach, passion
58
+
* When you judge the awards - it's not dragons den. Award creativity, skill, approach, passion. Make the special-mention/award/category mean something to the person receiving it.
56
59
* 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".
57
60
* Some ideas "Best Technology", "Best Team", "Local Hero's"
58
61
* (One of the prizes I won once was an engineering day where we build HexaYerts and GridBeam furniture to put in the yert, solar power wiring and a composting toilet. Can you create prizes that further engagement)
@@ -132,6 +135,8 @@ I've been criticized about being unrealistic or misaligned with my tech list abo
132
135
133
136
If you do not understand what the items are above, you will be at a disadvantage when recruiting the right people and you be in a weak position to help learners build the relevant skills in preparation for the event.
134
137
138
+
Whenever I see an event being advertised with well meaning people smiling and saying "You don't have to be technical to get involved" this just detracts from what the event is aiming to achieve. I see this, and it's the death knoll of the event. If you want excellence, you need to identify and appreciate excellence. If you want it to be a social, inclusive and fun with some free food, that is a reasonable goal, but don't expect excellence.
139
+
This attitude also detracts/devalues from the the young people that have put in significant effort to develop their skills, only to have a range of people just turn up and say "Anyone can do this and anyone can contribute". This undermines the significant difficulty and long term investment needed.
0 commit comments