1. Play this music...
SAMPLES ERIK SATIE'S “FIRST GYMNOPÉDIE” (1888)
2. Press this button to watch...
▷ launch slideshow
Dear friends of fruitful.school,
This Sunday from 4-6pm we're having a happy hour to celebrate the end of Fruitful School. If you can, please stop by.
John & Laurel
Like Fruitful School, Code Societies is a code-related learning initiative happening concurrently this Winter 2020. While the specific programs of our schools are quite different, we wanted to learn more about Code Societies and how it has changed over time, now in its third iteration.
The following conversation was transcribed and edited from a phone call.
Can you tell me a little about your Code Societies’ graphic? How has it evolved over the three years?
The current graphic reads almost like an illusion. At first it looks like a tangle of knots, but then you realize you can read it… We were thinking about entanglements in society and programming loops—which are all relevant material for Code Societies.
Code Societies is the School for Poetic Computation’s three week program about how code and society are coproduced. It’s a balanced, interwoven study of critical theory and hands-on coding workshops. In the graphic, the breathing, animated purple is feminine-feeling, which in a computational setting has political implications. Purple also symbolizes magic, like in our recent class exploring computation through magical and divinatory language by our teacher Allison Parrish.
Since our graphic could attract potential students, we had a responsibility to visually represent our program accurately. We didn’t want students to apply thinking it’ll be a coding bootcamp. This is about theoretical code, and through our choice of visual language, we wanted to be upfront about that as much as possible.
The woven knot graphic was created by Lisa Larson-Walker. Lisa is a brilliant illustrator and was also one of the students in the very first Code Societies during summer 2018.
Lisa made many variations, and you can see it changed slightly from Winter 2019 to 2020. But what stayed the same was the dark background and white text. This is because of American Artist’s influence. American taught at Code Societies now each iteration (Summer 2018, Winter 2019, Winter 2020) and wrote Black Gooey Universe, which charts how computer terminals changed from default black to white background, which charts how computer terminals changed from default black to white background, and how this is an expression of white supremacy, or to quote a current Code Societies student, Char Jeré, “white inferiority.” What does it mean when a large group of people assumes that a white background is default, or an empty space ready to be imprinted on, when other colors such as black and blue are just as easily marked? We should remember that on a screen, pixels can be any color. Defaults from another medium such as the printing press, for example, shouldn’t necessarily become screen defaults.
For the very first Code Societies in summer 2018, I hand-painted small glyphs during one sleepless night. I knew I wanted lots of symbols without meaning attached to them already, which felt like a good foundation for beginning.
I noticed this first iteration was during the summer. And the second and third (going on now) have been during the winters. What’s it like to teach in these extreme seasons?
During that first summer, it was very hot. Our building in NYC’s West Village doesn’t have air-conditioning. We had a loud, not very effective AC in the room with about ten fans going. To be heard over the fan sounds, every teacher had to speak into a mic. And then when it was time for discussions, students passed around the mic to participate. It wasn’t very natural.
Then in our first winter, there was a problem with the building’s heating system. So instead of ten fans, we had ten heaters. Thankfully the heaters were quiet. But with all the wires running everywhere, sometimes we would blow a fuse. Thankfully in our second winter (right now, 2020), there is heat in the building. The room is comfortable without any alterations.
I actually think summer suits Code Societies quite well. So much of Code Societies is about unlearning patterns of what education is, what it looks like, what it feels like—building new structures, like weaving cloth, and how we want to co-learn and co-teach with each other. Summertime is traditionally the only time when students who participate in traditional US education have an explicit break from that structure. So mentally a summer feels more “chaotic good” in an educational sense.
Anything you’re especially excited about for this Winter 2020 iteration?
Code Societies is such an intensive project, and this is the first time I’ve had a whole year between iterations, which has allowed me to the time and space to grow as an organizer and teacher. I’m excited to bring that to the project.
This year in particular, we are trying out a new organizational structure...
In the first two iterations, I had TA’s (teaching assistants). It soon became clear to me that TA’s contributed so much to the program—it’s an important role. So in this iteration, there are no TA’s, but instead “co-organizers,” which feels more accurate and respectful for the type of work involved.
Right now, I’m working with Neta Bomani and Emma Rae-Norton as a team of three co-organizers. I’m excited about the affordances this new organization structure allows, as Neta is leading an oral history project and Emma is publishing Code Societies’ new website with blogs.
Code Societies is really about technology as a social idea. To propose that you “only learn a technical thing” apart from a social history of that thing is false. At Code Societies, we believe there is no computational education without a critical (anti-racist, anti-sexist, and environmentally conscious) theory of computation. The teachers, students, and organizational structure of Code Societies, this iteration especially, all reflect this.
Melanie Hoff is the lead organizer of Code Societies—a three-week intensive educational program at the School for Poetic Computation, now in its third iteration.
The Student Showcase will be on January 25, 2020, which you can find out more about here.
Fruitful School started just recently—
In the first two sessions, we introduced foundational languages for making websites—HTML and CSS, along with some historical context surrounding the web’s beginnings...
We’ve also been thinking about our own formation as a school. How should we introduce our way of relating and working together? We decided to draft our own Code of Conduct, as you can see here...
We are indebted to the School for Poetic Computation’s Code of Conduct, which they’ve generously shared here. We used it as a basis for our own.
We also took some inspiration from the guiding rules of a “Bohm Dialogue,” a type of nonjudgemental, generative group exchange started by physicist David Bohm that is essentially sitting in a circle and talking in a group, with a few important rules...
We learned about Bohm Dialogue from Cab, via his Are.na blog post.
Note that our conduct guide is a work in progress. We hope to edit it as time goes on, after living by it more and seeing how it feels...
The other day I saw Elliott tweet...
websites that we need in 2020:— elliott's company 2 (@elliottsphone) December 21, 2019
- small community social networks
- video sites that feel like vimeo/youtube 1.0
- music sites that feel like <audio>
- micro blogging website that feels like .txt
And found myself thinking that a great solution to “micro blogging .txt” might be simply displaying the files on your website via Apache DirectoryIndex.
In fact, right now, Elliott (http://elliott.computer) has something like this going on...
To tell your Apache server to display your files, you need to create a special
.htaccess file. (Note that it has a dot in front of its name, meaning it is typically invisible.) You will tell it something like this. This tells
your webserver to display its files...
Then you place this
.htaccess in your server’s root directory, letting visitors see and browse your website’s files. I like this because it highlights what a website is... simply a collection of files.
We are currently in progress with something similar, a simple file directory. Some snippets...
As you can tell, we styled our index! We added yellow background and some custom icons. Here is a peek into our
In addition to telling our server to display the index (line 1) we also told it to do this in a “fancy” way... displaying of additional file information than is default (line 2), and after that, we specify a header and footer file that are
inside of a (not-shown) folder that we named
_ (underscore). The header has a little CSS inside, which is giving the page the yellow background. And line 14 onwards is specifying custom icons, overriding the defaults! Of course
we chose fruit...
We learned all this from a very helpful blog post.
🍐 seasons greetings, scroll up.
Why did you make Mysterious Fruit? Or how did it come to be?
As I said the other time you interviewed me, I like fruits.
They’re delicious, healthy, and also good looking. When traveling in other countries, I like eating fruits I’ve never seen before. I like to imagine their flavor before visiting and tasting.
It was not easy to imagine their flavor. But by surfing the web, I can get a little closer.
Wow, reminds me of that documentary “Fruit Hunters” about rare fruits and the people who chase them.
Can you tell me about your favorite lines of code from this project?
<ul class="mysterious-fruit"> <li class="piece"></li> <li class="piece"></li> <li class="piece"></li> <li class="piece"></li> </ul>
It’s fun to think about which HTML elements to use. This part shows the four pieces of Apple Emoji fruits. As you can see, I used
<ul> tag instead of
<ol> tag or
<div> tag because it’s a
list, and there’s no clear order in it. Since I like both literature and computers, sometimes such a list looks like a mysterious poem.
var fruits = [ 'assets/images/avocado.png', 'assets/images/banana.png', 'assets/images/cherries.png', 'assets/images/coconut.png', 'assets/images/grapes.png', 'assets/images/green-apple.png', 'assets/images/kiwi.png', 'assets/images/lemon.png', 'assets/images/mango.png', 'assets/images/melon.png', 'assets/images/peach.png', 'assets/images/pear.png', 'assets/images/pineapple.png', 'assets/images/red-apple.png', 'assets/images/strawberry.png', 'assets/images/tangerine.png', 'assets/images/tomato.png', 'assets/images/watermelon.png', ];
Good question. Some people say tomato is a fruit, others say it is not. Some people say both.
Whatever the truth is, when I believe that tomato is fruit, it becomes a fruit for me.
Can the web be fruitful? Can the web make us happy? The answer is the same. I believe that the important thing is to believe.
Happy Cyber Monday! Today we are launching “Fruitful School”, our first independently-run teaching initiative. We were inspired by a few poet friends who offered simple classes from their apartments or via Skype.
If any of you know John or my previous teaching work, this school differs in that participants must apply with a specific idea proposal — a “seed.” Maybe this seed is an idea about a website container, like a compelling URL or website name. Or maybe it’s a specific piece of content to publish online, but how or in what form is still up in the air. Or maybe it is a totally fully-fledged concept with content and container working together harmoniously, and it’s more about the details of publishing online.
We are excited to know participants’ motivations from the very beginning. Each week, we’ll explore a specific aspect of web markup and programming, and each week participants will try manifesting their seed using this aspect. We’ll also have some lectures, demos, sharing, critiques, and mentorship. By the end of the workshop, hopefully all seeds will sprout, or maybe even produce fruit, whatever it means…
See you next in 2020,