• Tech for Good?

    Friday Morning Hope: See more products that put us back in touch with ourselves, each other, and the world around us. Thanks Humane team, for being persistent and rethinking Human-Computer Interaction.

    Friday Evening Pessimism: I don’t think your first product (ai pin*) will take off. 🙁

    *In Brazil, Aipim means Cassava Root. I used to plant on my front yard, I miss that.

  • The Founder’s Dilemmas by Noam Wasserman

    Just finished reading “The Founder’s Dilemmas” by Noam Wasserman and wow, it’s a rollercoaster of insights! 💡🎢

    1️⃣ First up, the book dives into the murky waters of hiring. Ever thought your COO was redundant? Well, this book suggests that sometimes, having a COO in a early stage startup is a big red flag – or is your COO the real CEO? Tough pill to swallow for some! 💊

    2️⃣ Next, it hits where it hurts – dealing with underperformers. The dilemma? Keeping them might preserve team morale and knowledge, but at what cost to your startup’s growth and efficiency? It’s a high-stakes game of balancing growth with loyalty. 🤔⚖️

    3️⃣ And the most controversial of all – founding with friends. Sounds like a dream, right? Not so fast! The book suggests you’re likely to lose either your company, your friends, or both. Friendship and business, a volatile mix?

    There are a bunch of other hot takes. Here are all my highlights.

  • Digital Toxic Shock

    Reflecting on the thought-provoking work1 of Sharra Vostral, it’s intriguing to explore how her concept of “BIOLOGICALLY INCOMPATIBLE TECHNOLOGY” can be applied in the current digital age.

    In the ’80s, an innovative product was launched amid much fanfare – a smaller, lighter, and super absorbent tampon.

    Unfortunately, this new product led to an outbreak of Toxic Shock Syndrome (TSS), especially among young women. The company said that the product itself was harmful, but in a complex interplay of variables, it enabled Staphylococcus aureus to reproduce rapidly, producing a deadly toxin. This concept has since been recast as “biocatalyst technologies” in her latest book, “Toxic Shock,” which has truly captured my attention.

    Ultimately, that particular tampon was removed from the market, but its users were blamed for using it “incorrectly,” a notion that persists and contributes to the stigma surrounding TSS today. The prevailing sentiment seems to be that if someone suffers from TSS, it’s her fault.

    Fast forward to the present day, we are surrounded by new digital projects, many of which have unanticipated outcomes. Social media has often been implicated in a rise in depression and anxiety², and thousands of novel digital solutions are emerging. Particularly alarming is the sharp increase in suicides among young women², which brings to mind the young women affected by TSS decades ago.

    These parallels lead me to ask:
    – Are we, as product innovators and leaders, unintentionally developing what could be deemed “psychologically incompatible technology?”
    – Are we fostering an era of anxiety and depression-catalyst technologies? Like a Digital Toxic Shock?
    – Will we blame the users (again) if something unexpected happens?

    We must remember to keep human well-being at the heart of technological advancement.

    For a deeper dive, here are the articles that helped me connect these ideas:

    1. Rely and Toxic Shock Syndrome: A Technological Health Crisis
    2. Jonathan Haidt and Zach Rausch‘s research on the teen mental health crisis
    3. Almost a Third of High-School Girls Considered Suicide in 2021

  • SF2.LA: Part 1

    Diego from 2 months ago:

    “No-code platforms are BS.”

    Diego from today:

    “No-code platforms are mostly BS. Except one, which is now my new BFF. 😉”

    I once firmly believed that low/no-code platforms couldn’t create novel technologies. However, I had the opportunity to challenge this belief while developing a solution for a non-profit campaign.

    The goal was ambitious: to connect the Strava and DonorDrive APIs to boost AIDS/LifeCycle participants’ campaigns by automatically sharing their training efforts and helping with their fundraising goals. This was something I had already been doing manually for my campaign, and friends were curious about how they could do the same.

    After exploring various no/low-code platforms, I discovered FlutterFlow, which perfectly fit my needs. It offers a comprehensive Cloud IDE, encompassing UI, Design System, Database, Authentication, Frontend, Backend, Webhooks, Version Control and more.


    Initially, I struggled to grasp some concepts and could have had a better experience. However, the FlutterFlow community was incredibly supportive, and after four very long weekends, I had a solution ready for all 2500+ participants. It’s still a work in progress but is already assisting other AIDS/Lifecycle participants.

    I hope it will make a significant difference for the organizations behind the event.
    I’m immensely grateful for the support and feedback from the cycling and tech communities. Your encouragement has been pivotal in this journey. This project marks just the beginning. I now see these solutions as catalysts for change, inspiring more tech-driven initiatives for social causes.

    If you’re a participant (or thinking about becoming one), I’d love to hear your feedback and your experience using it: https://sf2.la/