Principal engineer, twenty-five years in. These days I'm building an AI-native SDLC and the harnesses that keep the agents honest.
By Jordan PapaleoReno, NV
J.P., off the clock.
In the beginning, there was code
Well, not for me but I am sure there was some pretty serious engineering required to birth existence. I started my web path in 2005 while trying to make a career in the ski industry. Who knew the path to a software engineer would start by bumping chairs in Breckenridge, CO after dropping out of college. I mean, I just wanted to build a website for my dad, I had no clue this was coming.
Off the keyboard
Strength & science
I'm a NASM certified personal trainer and nutrition coach, and I'm working on my physique coach certificate. Same brain as the engineering side: form a hypothesis, build the protocol, measure what happens.
NASM Certified Personal TrainerCertified
NASM Certified Nutrition CoachCertified
Physique CoachIn progress
My other pet project, Reno Fitness Lab, is for creating protocols and testing outcomes.
Community
Beer, devs, and a stream that never worked
TahoeJS
I love code communities; I really do. The first JavaScript community I started eventually became TahoeJS but it did not start that way. Go back a few thousand years in developer time, way back to the days of angular 0.FML.whatevs. These were the days when you could email the angular team with questions. These were the days when Brad Green would send you official angular t-shirts for being an early adopter. I rallied a group of engineers to hang out in a conference room after work with some beers so we could watch Google's live stream of their angular meetup. Go figure, the live stream barely ever worked so we started learning and sharing what we learned with each other.
ProTip
Beer + Devs = Meetup
One day my dev buddy Garrett told me about BeerJS and I instantly "applied" for my very own repo under BeerJS. Somehow, BeerJS birthed a parent (very unnatural), you guessed it, TahoeJS. We made stickers (most important part of building community), got a few speakers, a beer sponsor (thank you FiftyFifty Brewing), and almost threw a conference. This really contributed to creating a tech community in Truckee, CA. After I moved to Reno, TahoeJS migrated to the south side of the lake.
BeerJS
I am the current curator (curator just sounds cool) of the entire BeerJS community. It may look just like a GitHub repo but it's actually a JavaScript community present in 50 cities around the world. Many moons ago there was a request for someone to take over running the community repos. I jumped at that chance and have been doing it since. It's totally a Dread Pirate Roberts thing. But let's be honest: good code and good beer, you can't beat that.
After moving to Reno and being the curator of BeerJS, I had no choice but to start one in Reno. This quickly turned into a revival movement for RenoJS too.
Lessons learned
Community before code. People need to feel accountable to the other people in your meetup. It's much easier to guilt people for missing a month.
Don't do it all yourself. You WILL burn out. Community is not a one-man show. Get everyone involved.