~rabbits/libreplanet2022

08743c718f42735eda3ff07e787ac0c5d25a9033 — rekkabell 2 years ago ae1cf31
*
1 files changed, 40 insertions(+), 66 deletions(-)

M slides
M slides => slides +40 -66
@@ 81,7 81,7 @@ TEXT We wanted to exit the wasteful loop of acquiring`the necessities of life ea
	- We also wanted to carry the tools we need to keep creating things.
		- Becoming nomads is fine and all, but we still love to paint and to compose music.

NAME [rek] 2.0 Power Preconceptions
NAME [rek] 2.0 Preconceptions
FILL 03
GOTO 00,08
PICT media/powerhungry.tga


@@ 90,6 90,7 @@ HEAD Software suddenly has a direct` impact on the way we work.
GOTO 08,12
TEXT We left with Macbooks, iPhones, and used tools like Photoshop and Xcode.

	- To give some context, this is how we started:
	- Left Canada, with 2 MacbookPros, 2 Iphones, 
		- Used MacOS.
		- PS for assets, built games with Xcode.


@@ 102,7 103,7 @@ TEXT We left with Macbooks, iPhones, and used tools like Photoshop and Xcode.
		- Appeared innacessible. 
		- Not known for art and games, we thought.

NAME [rek] 2.1 Power Preconceptions
NAME [rek] 2.1 Preconceptions
FILL 03
GOTO 00,00
PICT media/powerhungry2.tga


@@ 212,8 213,7 @@ HEAD Adapting our`projects to`available resources.
	- So we adapted the software we use to these new power requirements.
	- Decided that we were satisfied with the speed of our current devices.
	- But we were not satisfied with how software made use of that hardware.
	- We started to look into writing efficient software.
	- Calendars, TODOS, and daily maintenance tools have migrated to paper.
	- Like maps, calendars, TODOS, and daily maintenance tools have migrated to paper.
	- Like we changed halogens for LEDs, we replaced electron apps for native apps.
	- We prioritized foss programs so we could inspect their inner workings 
		and audit where they spent cycles.


@@ 255,7 255,6 @@ HEAD Connectivity`too became`an issue
		- Also struggling to download same 10G update.
		- We bonded over this struggle.
	- As speed slowed to painful crawl at the cafe, thought it ridiculous.
		- Began to question if making games on boat made sense anymore.

NAME [rek] 3.1 Internet problems
FILL 03


@@ 358,27 357,14 @@ TEXT No schedule.`Secure everything.
	- So, we don't have a schedule, and this is reflected with how we develop software.
		- In a way, weather has a direct impact on our roadmap and releases.
	
NAME [rek] 5.0 Learning to repair boat
FILL 03
GOTO 00,06
PICT media/parallels.tga
GOTO 07,05
HEAD Learning to maintain a boat has`advised how we build software.

	- Boat life forces us to fix things (parts not always available, neither is access to repair shops).
	- When we mend, we believe it makes us care. 
	- We make it our own. And are more likely to keep maintaining.
	- Everything comes at a cost. When sailing, when no one around depending on others for security is dangerous.
	- We like to think that things we learnt working on the boat, we can now carry with us into application development.

NAME [rek] 6.0 Resilience boat
GOTO 00,00
PICT media/grindereating.tga
GOTO 04,15
HEAD Have things work`when you need`them to

	- When working we want to have things work when we need them to.
	- On boat, less a matter of productivity/convenience, but as mentioned before, it is life/death.
	- When sailing we want to have things work when we need them to.
		- Boat life forces us to fix things (parts not always available, neither is access to repair shops).
	- Having redundancy=good.
	- Cooking on Pino
		- We have alcohol, wood and LPG.


@@ 387,31 373,27 @@ HEAD Have things work`when you need`them to
	- We're not fans of all-in-one tools. 
		- They are convenient. 
		- But there is more chance break, or get in the way.
	- A hand-operated grain mill is good example of a simple, one-purpose design.
	- A hand-operated grain mill is good example of a simple tool.
		- It grinds grains. That's all it does.
		- Doesn't beat dough or bake bread for you.
		- It's a time-tested design.
		- Does on thing well. 
		- Does one thing well. 
		- Easy to inspect, making replacement parts is possible.

NAME [rek] 6.1 Resilience boat
FILL 03
GOTO 00,00
PICT media/woodstove.tga
GOTO 04,0c
HEAD Woodstove vs diesel heater,`marine head vs dry toilet
GOTO 08,19
TEXT Few moving parts
GOTO 00,06
PICT media/parallels.tga
GOTO 07,05
HEAD Learning to maintain a boat has`advised how we build software.

	- On boat, if electric water pressure broken. 
		- Means you cannot drink water. Not good.
	- Woodstove vs diesel heater
		- Woodstove has simple, robust design. 
		- Few failure points.
	- Had many failures with marine head, switched to dry toilet.
		- Crazy how much complexity is required to move human shit from one side of the wall to the other. (from inside to outside the boat).
	- Best advice we got, is if leaving for a big sailing trip with spares, install the spare and keep the other one as the spare. 
	- Doing this, we learn how to change the part and what tools we need to do the job.
		- Means you cannot drink water. Not good. So use hand pumps
	- Or if can't heat space cause diesel heater failure, not good, woodstove.
	- We prioritize designs that are designed to be repaired.
	- When we mend, we believe it makes us care. 
		- And are more likely to keep maintaining.
	- We like to think that things we learnt working on the boat, we can now carry with us into application development.

NAME [toy] 6.2 Resilience computers
FILL 03


@@ 431,7 413,11 @@ HEAD Nothing should be`miniaturized.
	- We found that simple languages with a spec that fits on a few printed pages the best.
		- For example: We carried the whole of 6502 assembly documentation on a handful of printed pages.

	- Learning to repair, and maintain a boat has advised the way we build software now.
NAME [toy] 6.3 Resilience computers
FILL 03
GOTO 07,00
PICT media/grindereating.tga

	- We found endless parallels between software maintenance and sailboat maintenance.
	- Ideally hardware would come with a maintenance manual, not only a downloadable pdf
		- you never have the pdf when you need it, sometimes you need the computer to get to the pdf..


@@ 447,14 433,14 @@ GOTO 04,08
HEAD Context is the`connecting`thread.

	- Surrounded with ppl who know more.
	- Old salts are knowledgeable, curious people. 
	- Old salts are knowledgeable, and curious . 
		- Eager to share, teach & lend tools.
	- Sailor websites, esp older ones, collection of information.
	- Sailor websites, esp older ones, treasure trove of information.
		- Traveled with text documents, compendiums put together by hundreds of sailors over the years.
		- Updated every year, with every passing cohort.
		- Contain info on where to get parts, food, location of hospitals, nagivational hazards.
	- A lot of collaboration in long-distance sailors community.
		- Not hidden behind pay-walls.
	- A lot of collaboration in long-distance sailor community.
		- Info is available, not hidden behind pay-walls.

NAME [rek] 7.1 Documentation Projects
FILL 03


@@ 463,7 449,7 @@ PICT media/sailing2.tga
GOTO 28,05
HEAD Community.

	- To collect what we learned, we created knowledge base.
	- To collect what we learned, we created knowledge base, a wiki.
	- Every tool, book, story, everything we make is bound together
	- And the wiki serves as the connecting thread
	- Wiki also doubles as context for our work


@@ 498,8 484,8 @@ HEAD No roads to follow.
		- Limits the noise, by living at an arm's length from the internet.
		- Make time for slow activities.
	- We've adapted our software around the limitations of our vessel
		- instead of increasing the limits.
	- We learn to appreciate these limits and think that it makes our work better.
		- instead of increasing its limits.
	- We learn to appreciate these limits and think that they make our work better.
		- We often consider that using slow devices is a practical way to write efficient software.

NAME [toy] 9.0 Uxn


@@ 513,12 499,12 @@ TEXT Uxn is a virtual machine that allows us to bring software onto any platform
	- We found that writing graphical applications(even in C), has a lot of portability issues.
		- For example: One of our device is a plan 9 workstation.
	- But even beyond portability, building a C graphical applications is much heavier and slower 
		comparing to simply assembling rom.
		than simply assembling a rom.
	- After experimenting with virtual machines like Another World & Flash
		- and building games for the NES.
	- We decided to build our own little vm as a target to build our tools for.
	- It has 32 opcodes, it's implemented in about a 100 lines of C89.
		- The emulator front-end is about a thousand, we have emulator for nearly every portable handheld and system.
		- The emulator front-end is about a thousand, we have emulators for nearly every portable handheld and system.
	- It has only 64kb of memory, but we found that this is enough for most things
	- Small memory, means small assets, simple storage, easy versioning.



@@ 544,20 530,12 @@ PICT media/niche.tga
GOTO 04,18
HEAD A polyculture`of tools.

	- If have specific interest, chances are someone else shares this interest
	- Tempting to pursue popular interests.
	- Popularity = allure of success, guarantee of profits.
	- Too much competition in those spheres.
	- Difficult to stand out
	- Creates monoculture of apps
		- All taking ever-smaller bites out of the same piece.
	- Niche = less competition
		- Also creates diversity.
	- Encourage investing activities whoses value no depend on ability to make capital.
		- Road there not easy, building interest takes time.
	- Adapted our work to our situation.
	- Created playground, researching/documenting low-tech solutions.
	- With hope of building more resilient future
	- Our approach to software goes against the typical narrative of programming.
	- The sad thing is that attempts at creating new computing ecosystems is often discouraged and met with ridicule. 
		- The constant reliance on the modern tech stack creates programmers who can only stitch solutions together in frameworks, but not people who can directly solve problems.
		- This in turn, creates a vulnerable monoculture of tools.
	- A plurality of ways to use computers encourages investing in activities whoses value no depend on ability to make capital.
		- The road there not easy, but pursue popular interests, also means competing against everyone.

NAME [rek] Outro
FILL 03


@@ 568,10 546,6 @@ HEAD Liberating the imagination`by eliminating possibilities.
GOTO 04,18
TEXT Frustrated with software, we built our own`With limited internet, we became more independent`When hardware failed, we learned to repair,`Lacking power, we re-imagine our projects,`Calculated and optimized our usage to to more with less.

	- In 60's French writers (Oulipo) writing with constrained techniques.
	- (e.g, writing paragraphs or longer works in which a particular letter or group of letters is avoided)
	- This inspire ideas, creativity. 
		- Also fun.
	- Living/working from sailboat = constraint for us.
	- Liberated imagination by eliminating possibilities.
	- Work less, by keeping our needs small.


@@ 582,8 556,8 @@ TEXT Frustrated with software, we built our own`With limited internet, we became
	- Hardwaire failure => learn to fix
	- Lacking power, re-imagine studio/projects. 
		- Calculate/optimize usage to to more with less.
	- Transformative experience. 
	- Can be for you too if you try and work according to limited resources and the weather.
	- This led us to create a playground, and to research and document low-tech solutions.
	- With the hope of building a more resilient future.

NAME [toy] Credit slide
FILL 03