- Our tools
- A dead Macbook
- what is the 100r tools ecosystem?
- Problems with Xcode and Photoshop
- The solution
- What's next
How did the Hundredrabbits ecosystem come into being? It's a long story, but here's a summary.
In 2016, we left Canada, armed with our two iPhones and 2 MacBooks Pros. We didn't know the wattage of any of the devices we owned, and even less about the amount of solar needed to power them. When living on land we didn't pay attention to how many amps our devices required daily. Electricity felt limitless.
When we started sailing in BC, we had no dinghy and so we'd go from dock to dock. When we purchased Iggy in Nanaimo, we spent more days on the hook. The first anchorage we went to was a small bight east of Eagle Point, it offered a great view of metro Vancouver. From that point on we spent more and more time at anchor, moving every 5 days or so. We had no power concerns because our route always included marinas, or guest slips at yacht clubs. Our batteries were always topped up.
Life off-grid was new to us then, as was spending lots of time outdoors. We liked it, a lot. When at anchor we'd go explore, spend a few hours working, cooking, then we'd read or play card games in evenings. When living on land, we'd work from 8h-19h, sitting in front of our respective screens, but now things were different. We wanted to do less of that, to take long bike ride around islands or to sit on the deck in evenings to watch the sun set. Then, at marinas where we had both power and internet, we'd go back to working longer hours to get things done. This was a fine setup, we thought, but, there was problem: what happens when we start living AND working at anchor full time? We liked being outdoors, but that's not all we wanted to do. We're creatives, and we need to make things. We were relying on powered docks to work, and so we never got to test our current power setup off-grid. If we had spent a month or so away from civilization, we would have learnt that we had to change something.
And so, to continue with the story, we left Canada and cruised down the coast of the US. True to our old habits, we continued to alternate between staying in a marina and at anchor. The longest we spent off-grid during that time was 3 weeks in San Francisco, anchored off Treasure Island. During that time we discovered that working aboard, running two Macbook Pros, a refrigerator and our phones was not possible. To save on power, we started turning the fridge off at night, and taking trips into town during the day to work from cafes. SF was grey on most days, our solar couldn't keep up with our demanding work schedules. Going to work from cafes in town worked well for us, most had outlets we could use. Our routine started with working from cafes until lunch, then wandering around in the afternoons. We would return home before dark to turn the fridge off, but doing it didn't make sense because the constant shifts in temperatures produced too much moisture. Moisture meant rot and mold. We decided that keeping it off was a better idea for both our batteries and our produce. With the fridge out of the equation, we figured that we'd have more power left-over for our laptops.
A dead Macbook
We experienced time at anchor again in San Diego, with Pino finding a cosy spot near Coronado island. All convenient anchorages were full because of the Baha Haha, an annual regatta of boats that sail down the coast to Mexico. Being near Coronado wasn't too bad, but our spot was far from the public dock. We didn't have an outboard motor then and had to row everywhere. Rowing wasn't easy in an inflatable. We wanted to bring our bikes onto shore, so we could cycle around San Diego, but the nearest drop off was a golf course. We rowed our bikes onto the shore, dropped them off and Devine sneaked them across the greens and into town while I rowed to the public dock. Everyday we'd row our laptops into town to work on our game Markl, trying to solve problems we had with the design of the game. At that point, we'd hit a wall with this project. We pushed on anyway, but could only work on it for 2 weeks because after that, we had to make our way south across the border.
The sail was nice and short, we arrived near Ensenada in the dark with plans to anchor off Islas de Todos Santos, a set of offshore islands. Anchoring anywhere in the dark is foolish, we knew it when we did it the first time in San Luis Obispo, and again that day. As we neared our anchoring spot, shapes began to appear in the dark. They were annoying to us because our guide told us they weren't supposed to be there, important to note that our Charlie's Charts guide was from the 70's and that even if landmasses don't move, human constructions spawn in and out of existence. The bay had aquaculture pens in it. Loads of them. This is something we would have seen had we looked at satellite images of the islands, but we didn't do this. We couldn't stay here, so we turned around and headed to Ensenada to find a place to anchor. We dropped anchor in another spot recommended by the ancient wisdom of Charlie's Charts, and so having struck nothing, we thought it safe and went to sleep.
We woke up the next morning with someone knocking on the hull. We climbed out, hair dishevelled, to see who it was, and saw 3 men in a power boat with 'policía' written on its side. Written Spanish is not too hard to decipher for French speakers like us, but verbal Spanish is something else entirely. I caught bits of what they were trying to communicate to us. Words like 'hora', which in my mind sounded like 'hours' which meant they were asking us about the time? What they were actually saying was 'ahora', meaning 'now', as in... we have to move NOW because a large cruiseship is coming and we're anchored in its path. 70's Charlie's Charts did not take this into account. Shame on them. How dare they not know the future?
We found a spot at Baja Naval, a marina with power on the dock. After spending 3 days there, we decided to book it for a month so we could have time to work on projects. The timing was impeccable, because my Macbook Pro started having logic board issues. We had few options for repair at the time, and we couldn't afford to replace it. We had a Chromebook aboard Pino, a laptop we bought to use as a media station. Since we were a laptop short, Devine decided to try and use ChromeOS for development. During this transition, Devine developed the first version of Ronin. I didn't have Photoshop to work with, but we wondered if we could fashion a replacement for it ourselves. Ambitious, I know. Our thinking was that we could only implement the features we needed. Devine used PS for simple photo manipulation like color correction, and I needed brush tools and layering. We didn't use most of the features included with the software, so building a lean graphics editor would be easy... right?
The early version of Ronin we designed was functional, but it couldn't serve as a replacement for Photoshop. Not yet. We still had too much to learn.
At this point, we were in trouble. A friend in SF heard about our problems and sent us an old disused 17' Macbook. We couldn't believe it. I could use it while we worked at improving Ronin. This gratious donation solved our problem.
We sailed around Baja California and over to La Paz in the Sea of Cortez. The marinas in La Paz, like the ones in San Diego, were full-up because of the same people. People sail down to Mexico, find a spot and stay there forever. We had no choice then, we started to live at anchor full time. We anchored off La Paz in the main anchorage, a short dinghy ride away from shore. This new setup worked for a while, but my new-to-me laptop was a battery-draining vampire, drawing ~8ah per hour. We couldn't work from Pino. We had to go back to old habits and seek help in the form of a coffee shop. This strategy worked in most places we'd been so far, but in La Paz, we found no cafe with both outlets and internet. We needed both to work, my hungry Macbook demanded it. To offer our solar panels some relief, we got a gas generator. Not the greenest of options, but it was the only way we'd found to keep working aboard Pino. Also, we figured it could be handy if ever we needed to use power tools at anchor. The gas generator combined with our engine's alternator worked for us. We'd sail to far away anchorages in Mexico and could stay working there for days and days without worry. The only reason we'd go back to town was to get food.
what is the 100r tools ecosystem?
It is a set of tools that we made, and that we use on a daily basis to do art, music and writing.
- ORCA, an experimental live-coding environment.
- Dotgrid, a simple vector line tool
- Left, a simple minimalist text editor.
- Ronin, a graphic design terminal
Problems with Xcode and Photoshop
As months passed, we experienced frequent failures with our devices and apps. Most times, I could not charge my laptop up to full battery, which means that it drew a LOT of power all the time. On a laptop the last few percentage points are much lower wattage to float/top it off, but, I never got there with my Mac. To add to our growing list of difficulties, our resident vampire's battery stopped holding a charge. We couldn't use it.
When we arrived in the Marquesas, our problems only worsened. Our house batteries and solar couldn't keep up with the combined thirst of our computers. I could only use my computer when the sun was highest in the sky, for short periods of time. It proved to be impractical. We couldn't use Photoshop or Xcode, two softwares we needed to make our games. Our generator was a big help, but we didn't want to run it all the time. We used it every couple of days, ignoring the sound, smell and vibration. Not an ideal situation.
In Nuku Hiva we had no internet on the boat. If we wanted to do anything online, we had to take the dinghy to shore to work from an outdoor cafe. This place had bananas hanging from the ceiling, the air was thick with flies and the was floor covered in sleeping hounds. The internet connection was slow, faster in the morning when there were less people around using it, but still damned slow. One morning Devine was sitting at the cafe, struggling to update Xcode again. Discouraged. Across the table sat another person, another demoralized soul. This, was Herbert.
Herbert, sweat at his brow, glared at the screen of his laptop. Devine sat across from him, beads of sweat trickling down as the speed of the internet slowed to a painful crawl. They sat there together, unaware that they shared a problem. Herbert, was a developer/sailor too, and was trying to download the same updates to Xcode. Both bonded over this struggle, which persisted throughout the South Pacific.
Making apps and games from an island in the Marquesas sounds idyllic. It's easy to imagine a developer smiling, one hand on the keyboard and the other holding a perspiring glass of pamplemousse juice, so pleased with his choices. 'AH! Dee-li-cious!' In truth, the developer can't enjoy his pamplemousse juice because he's too busy swearing at faraway bodies in Silicon Valley who think 10 G software updates are perfectly reasonable.
I remember us thinking then that our idea to work and travel was silly, impossible even, but we didn't give up. We had to find a way to continue to make things.
One night in Tahiti, we were sitting on deck, watching the Island of Moorea in the distance. We talked about expectations versus reality, and made a list of things we could improve on. I wasn't working much, due to my laptop's faulty battery, but this wasn't all bad... it allowed for more swimming, and to dive back into former interests, like writing. I began to write more during that time, using the Chromebook because it was low-power. The Chromebook only had Caret as a writing tool, which I was fine with, but Devine wasn't having it. The next day, he was hard at work making me a writing tool, something basic. The more I was writing, the more we improved it. Overtime, we added a synonyms dictionary, auto-complete and many other basic features, while keeping it lean. This, was our writing tool Left.
When we arrived in New Zealand, even if we were near a big city, with resources, we still didn't have access to power. We would have to continue to rely completely on solar. We invested in Raspberry Pi hardware, to replace the ChromeBook. Our new Pi setup was low-power and low-cost, perfect for writing. I decided to no longer use the 17' Macbook, even with a replacement 3rd-party battery (which also failed us later on). The device was still a crazy power-hungry beast. We couldn't use devices like that on Pino, not anymore. It was at that time that we received yet another disused Macbook to add to our growing collection. This 2010 model was less power-demanding, and would help keep me keep working.
We knew then already, that we didn't want to buy a new-anything from Apple ever again. Combining parts to create a good-working computer was, at the time, our only viable option. We would keep using these laptops, repairing them any way we can until we could find them suitable homes. An estimated 130,000 computers end up in the garbage annually, we didn't want to add to those statistics. Greenhouse emissions in production are far higher than from several years worth of usage by customers. This is why we've been holding off on purchasing new devices (in an attempt at reducing our broader environmental impact). In today's climate, it is far better to re-use, than to buy. After these events, we became aware — and concerned — over our power consumption. Just like how we calculate our water intake with a foot pump (1/4 cup per push), we would start to monitor our power usage, and to try and find ways to lessen it. This, was beneficial to the environment, but also, our situation required it. With limitations comes creativity.
We too, began talking about our vision of the future, about what working on Pino could be like if we could lessen our dependence on software and hardware we couldn't fix ourselves.
As we pushed further and further west with Pino, we accumulated both miles and problems, strengthening our desire to be self-sufficient.
Another downside we discovered, was that many tools and operating software need to call home eventually. It isn't uncommon for an iPhone to lock up, due to a prolonged period of no-internet. Many sailors we met also had that same problem. It's dangerous. Especially considering that many, like us, navigate using their phones. It's how we get our weather and communicate with others. We can view messages and weather downloaded with the SAT phone via an app on our cellphones.
We had a clear view of what we wanted then.
We had to adapt, to change our workflow. One big decision, was to scale our projects to the amount of energy we had available on the boat. This translates to shorter work hours, smaller projects (books, music etc) and making our own tools.
We made software that work offline, that use little power and that are good at doing one thing. This, recently, has evolved into coding our websites in C99, a language that is more resilient and light. We're also learning to code in Assembly, with the hope of making our games playable on older hardware like the NES and famicom.
All in all, we want everything we do to be open-source, so that if something breaks, we can easily fix it.
In an ideal world, we'd also have devices of our own design which follow these same rules. For now though, re-using old existing hardware is a good solution. We are thinking about this a lot, but this requires more resources and planning. This is an insight of what we have planned for the future!
Ronin, our graphic design terminal, is almost ready for release, we'll announce it here once it's out. In the meantime, enjoy this concept of these rabbit-like characters that Rekka designed to personify each tool! You'll be seeing a lot more of these guys around~
- What can a technologist do about climate change?
- Solar Punk: Notes toward a manifesto
- Design life cycle
- The Right to Repair
- Reduction Revolution
- What progress means
- Low tech magazine