post-mortem: my presentation at impact hub

a portion of my tech-savvy friends give talks. software developers get together for show-and-tell sessions that serve as networking and hiring opportunities (the events that i have attended have been very casual). some friends give their talks at conferences (e.g. deconstruct conf), and others at meetups (like donut.js). one of the best talks i’ve seen was one in which the speaker showed us how they used code to create the most dissonant music possible. they were followed by a woman (a banker by day) who used code to sort through produce plu codes.

so talks are happening and they’re useful and cool – i wanted to get in on the hype. so i put together my presentation using what i had learned from interviewing folks on ‘the orbit’. i asked my contact at impact hub if they could fit me into the calendar, and they said yes. easy peasy.

the hard part was making / rehearsing the presentation. i really had no idea who would show up, which meant that i didn’t know if my talk about seem stupid or inaccessible. i figured it would be best to not overthink it, and just focus on the things i liked and thought were useful.

i outlined the presentation in notion several times, then put together a google slides document. i went through three drafts before i settled on the one i was going to give. i practiced out loud in front of my girlfriend, and then video’d myself and sent it to lito who has a lot of experience with giving talks. both of them gave me meaningful and constructive feedback, which helped me further tune in the talk.

eight people showed up (less than i expected but still good). this meant that i could get to know my audience deeply and learn about their businesses and what they were hoping to get out of my presentation. my favorite bit was hearing about their projects. i find that many folks are embarking on really interesting, individual projects and i am always happy to see ways i can help (usually it is recommending a tool or a book).

if i were to do this again, i would really want to lean into the data more. i want to show hard and true facts that will illustrate my point: the future of work is coming, and its for everyone. if we figure out how to adjust to sustainable work structures, we’ll be well positioned to have meaningful careers that are fueled by our individual interests, passions, and talents.

my friends inspire me

perry is a co-worker of mine. he’s in his twenties, and makes a living doing cafe maintenance. i asked him what he does for fun and he told me, “well, i’m building a boat.”

“what? how?”

perry laughed. “you can pretty much learn anything on the internet these days. sure, if i was formally trained i could probably do a better job and make less mistakes. but you can learn a lot of the basics on youtube.”

next, i talked to nelson, a friend who likes to talk about philosophy. “i know a lot of philosophy isn’t immediately useful, but i like learning about it because it’s stimulating.” nelson picks up dense philosophy books from the bookstore, and uses youtube and google to further research terms and concepts that he wants to know more about.

lastly, my friend nat tells me that they are so impressed by how much their friends know. “it seems like everyone knows so much stuff about random subjects. i want to be one of those people, but i don’t know where to get started.”

more and more, when i ask friends how they got good at their hobbies or work, they’ll tell me “youtube” or “google”. this is super exciting to me, and also checks out with how i’ve been learning to program. i embark on a project, get stuck, then google my problem. i look at other people’s code, watch people on youtube, then try again. soon, i am better than i was before without having to set foot in a physical classroom.

the people i want to help are the people like nat – they know they can learn anything but need someone to help them figure out their interests. cultivating curiosity, building your own curriculum, these things don’t necessarily come naturally to folks who are used to sitting in a classroom and having a teacher tell them what they need to learn. i am lucky to know so many interest-driven learners, and i am currently inspired to lend a hand to those who want to become one.

building a car as it is moving

this week i’ve released a couple experiments. one is web app, one is a video essay. neither is perfect, and that’s hard for me to deal with. however, i know i have more to lose by agonizing over the quality of my work than by actually sharing it and moving on.

in this video, i challenge some of cory doctorow’s ideas about copyright, based on my amateur understanding of how the internet works. i am fully aware that i am likely wrong on a lot of points here, and if anything this video is my best attempt at putting my interests into words. i hope to get some feedback or to do further research on copyright so that i can speak more eloquently on the subject. but, in the interest of posting videos weekly, i felt compelled to settle and say ‘welp, this is good enough for now’. it exists and it’s not terrible, and i know it can be better.

This is a screenshot. Check out the live app here.

secondly, this is an app that i made using glitch. it takes data from your most listened to song on spotify and makes guesses at your personality based on that song. it’s funny, not necessarily built out to its fullest, but it works. writing and learning code is hard, and the majority of the effort was figuring out how to get spotify data from individual users (‘authentication’ they call it). i managed to do it, and the app works for most of the people that try it out. i could have made it more expansive, deep, or user friendly, but again i hit the ‘good enough’ point and knew that i needed to move on to the next thing.

as a perfectionist and a performer, i am often uncomfortable with releasing half-baked work. but, i am putting my focus more on the process rather than the product, and i know by continuing to release my experiments into the world, i will get immediate feedback and learn ten times more than if i were to build private projects and theorize in private.

websites – who really needs them?

i have a vendetta against the personal website. i have one (it’s not this one) and i’m ready to get rid of it. i am told, for a business, you need to have a website. my question: do you really?

like, i understand for websites that sell products. you want to go to the site to investigate the brand, the products, and possibly purchase. but for many other folks, you visit the website once and never again. the page i go to the most is the company’s “about” page and then maybe their “pricing”. i rarely read their blogs or any of the body content on the site. maybe i’m alone in this, but i have a hunch i’m not.

considering my squarespace costs $18/mo and it does very little in terms of connecting me with an audience, i am planning to retire it. if anything, i am paying $18/mo for faux credibility. “oh he has a website, he must be legit” says the imaginary voice in my head. this is indeed a fantasy. you don’t need a website to be legit. you do, however, need an internet presence. and this can be done FOR FREE on facebook and instagram. you can even have a low cost blog (like this one) which yields much more engagement than a static site that serves as a $18/mo business card.

maybe one day i’ll hit the scale that i can afford a website. but as i am experimenting and trying to find out my niche, my customer base, and my services, i am not going to pay a recurring fee for a billboard that does nothing for me.

cool directory

to continue on yesterday’s post on focused play, i also have made it a point to just dig deep into my google docs. what’s funny is that when i am bored i will just poke around in my folders, organizing the files until i suddenly come up with an idea that excites me. and, i realized recently that you can create tiny websites for free with a tool called google sites. i made a small “cool directory” that you can see here.

this small website was a solution to my project problem: i have so many projects that i’ve completed and/or am working on, i realized i needed a google sheet to keep track of them all. the website serves as a more palatable way to navigate the most recent videos and streams i’ve published.

this and yesterday’s mother’s day card are both small, but i think it is important to show off the little things along with the big projects, just because it validates what you’re doing, and provides some momentum for doing more. i hope that by learning one hundred little things, it will make building the big thing that much easier.

toolbox / sandbox

right now i am using glitch, a website that allows its users to try out and edit small programming projects. i’ve been learning javascript and a little bit of vr. i’m a little embarrassed by it, but i made a small mother’s day card for my mom which you can see below.

my strategy has been to just spend time playing with the tools on glitch in order to see what is possible and what i like. i have limited resources (i’m working primarily from a chromebook and an iphone) so glitch works out really well for me because it is based online. i’ve been having a good time trying things out, even though i don’t have a clear idea of where it will lead me.

twitch hypothesis

i recently started streaming on twitch. this is a messy platform that reminds me of myspace, since it has a lot of room for interactive customization. in reading about twitch, i learned that there is a quieter side to the platform that is not entirely focused on gaming. some folks knit. others read. some draw. me? i’m seeing if i can collaboratively write a tv script via livestream.

it’s an experiment, and i don’t know how it’s going to pan out. i know i need my schedule to be consistent, and i know i have to work out some logistical problems with sharing what’s on my screen, but i love working on platforms that are still growing and figuring out what they are. because in a sense, so am i.