Chris Fischer

Archive

Everything, in order. Companies, races, houses, people, wins, misses, and whatever I was trying to figure out at the time.

  1. The Long Way HereI build technology companies, work with startups, run and ride bikes, fix old houses, and start more side projects than I need.
  2. Help Needed a HomeThe Goodword help center needed its own address, even though Intercom still hosted the support articles behind it.
  3. Onboarding, AgainGoodword's revised application went live with a new onboarding path that began after the paywall.
  4. Who Am I Missing?The inbox knew people the address book had forgotten, so we tested whether two-way conversations could find the gaps.
  5. Katonah on Two WheelsNeutral Ground came back to Katonah for a fourth year of road routes, gravel, and a cycling expo afterward.
  6. IRL ModeThe meetup was over, so the follow-up shared the recording and gave everybody a reason to try Goodword's IRL Mode.
  7. Android, FinallyGoodword finally reached Google Play, giving the Android application a public store listing and download path.
  8. Please List Our MCPGoodword's Claude connection was working. Getting it into the MCP directory meant another submission and review queue.
  9. Your Network, On StageAn April 30 Betaworks event listing put Goodword into a public discussion about networks and startup distribution.
  10. Too Many ToolsA new teammate needed the honest tour of every service Goodword used across product, marketing, and operations.
  11. Unofficial Means BetterAn informal meetup built around live Claude demos needed hosts, and my name ended up on the list.
  12. Claude Found the Right PersonA relationship question inside Claude became a live test of whether Goodword's MCP connection could find the right person.
  13. All My AI Tools, One DoorI had too many AI tools, too many separate connections, and one web portal trying to put them behind the same door.
  14. Meetings Need a DebriefAn AI meeting notetaker could capture the call. Goodword still needed to turn that record into a useful debrief.
  15. Where's the Login?Goodword's public homepage had no obvious way back into the product, even for people who already had accounts.
  16. Hunting Product HuntA Product Hunt launch added screenshots, copy, timing, and one more public door into Goodword.
  17. Contacts, ConnectedA broken connector was keeping selected Goodword contacts out of the team's research system, so I repaired the path.
  18. The KICKR Went QuietAn indoor trainer connected normally but stopped broadcasting power data.
  19. Three Addresses, One InboxSupport, feedback, and general Goodword email all needed to land somewhere the team would actually see it.
  20. The Smoke TestWe walked through Goodword and wrote down the paths every release had to pass before it could surprise us again.
  21. Fine, Another ComputerI ordered a Raspberry Pi 5, more parts than the little computer needed, and another project for the pile.
  22. One List, Too Many ToolsAn opted-in email list needed a reliable trip from Google Sheets through cleanup and into Goodword's working CRM.
  23. Goodword Is LiveGoodword launched publicly after a year of building, several months of controlled beta work, and a lot of unfinished lists.
  24. What Should I Do Next?Goodword could find useful context, but the harder product question was what it should suggest somebody do next.
  25. You're InvitedThe Goodword beta was live. The invitation still had to make people want to connect their real accounts and try it.
  26. The Web VersionGoodword's early web version was almost ready for real people, which meant it finally needed a real test plan.
  27. Ship First. Email Later.The Goodword update had to be live and checked before the announcement sent people looking for it.
  28. Do Not Sort AirtableA routine list cleanup produced one blunt rule: do not edit imported Airtable records while the table is sorted.
  29. Zapier, Meet the TerminalA few signup automations turned into an experiment with running and managing Zapier workflows from the command line.
  30. Who Gets In?An app-store listing was not an invitation for everybody, and Goodword still needed a clean gate around the mobile beta.
  31. Google Wanted a VideoGoogle wanted proof before approving broader calendar access, so we made the short product video its review required.
  32. CSV or Google Sheet?One working list needed two exits: a plain CSV file and a Google Sheet people could use immediately.
  33. Start With the ProductThe product list kept growing, so we cut it back to one working baseline and the professional-network connection it needed.
  34. Please Deliver the EmailGoodword's email needed another pass through authentication and delivery before I trusted it to reach an inbox.
  35. Beta, SoonThe Goodword beta was close enough that we needed an announcement, an invitation, and a useful welcome flow.
  36. @goodword.comGoodword work was spread across old accounts, so we started moving the company and its shared tools onto one email domain.
  37. First EmailA May test message marked the beginning of a new company email setup before the Goodword beta announcement.
  38. Apply Took DUMBOThe Apply team was together in DUMBO while several people were visiting New York.
  39. Now What?An April product discussion defined what the app should show after a person had gone through every available recommendation.
  40. LinkedIn, Meet GoodwordA March product session worked through the language for connecting LinkedIn and improving relationship recommendations.
  41. Hello, Support?A March email checked whether the first support ticket and reply path worked from end to end.
  42. Design FirstA late-February product discussion focused on the user journey and getting important screens clear before more development began.
  43. Both Bikes, NaturallyA February maintenance note covered a new bike build, an older road bike, shifting, the drivetrain, and a saddle swap.
  44. Book the DemoA February note recorded a basic part of startup work: finding another product, booking a demo, and seeing how it handled a problem.
  45. Real Email AddressesA small startup team started moving from personal accounts to company email.
  46. Demo by PhoneAn iPhone mirroring feature became a practical way to show an early mobile product without passing a device around the room.
  47. The Calendar Finally ConnectedThe first product check of 2025 was a calendar integration that had started working but still needed a real walkthrough.
  48. Email Chris@Loop's Alpha reached outside users, which meant TestFlight permissions, Chrome allowlists, refresh bugs, screen shares, and a support plan that mostly ended with emailing me.
  49. Remove, Reinstall, Try AgainLoop's early Alpha was in outside hands, which meant backend maintenance, extension reinstalls, and manual onboarding support.
  50. Launching Soon, Still LoadingI told my network that Loop was launching soon, then sent Alpha testers a four-step checklist for the Thanksgiving deadline.
  51. Every Dollar MattersLoop needed a raw Alpha in ten days, so I hired engineering help, handed out repository access, and joined a very small team sprinting through the product gaps.
  52. Not Quite There YetI signed off on Loop's first Alpha, wrote down exactly what still did not work, and asked my running club to help me find a React Native engineer.
  53. Good Week, Weird WeekWe signed Loop's term sheet, I went to LA Tech Week for fundraising, celebrated at home and on a bike, and finished with another investor no.
  54. The Pitch and Run I MissedA flat city-bike tire made me miss an investor run while Loop was still asking people to bet on an Alpha they could not test.
  55. Ten Miles, 60:53I ran 60:53 at the 2024 South Nyack 10-Miler, finished ninth overall, and won the men's 40–44 age group.
  56. Thirteen Before LunchI ran 13.6 hilly miles through the Hudson Valley, then got on the bike for another 48.2.
  57. Over 300 Up BearSix days after my derailleur went into the spokes, I returned to Bear Mountain and set two climbing PRs.
  58. Thirty-Three Hours, Three LegsA 12-person Wild West Relay team ran 200 miles from Fort Collins to Steamboat Springs while I covered three legs and 19.7 miles across Colorado.
  59. What If the App Knows Nothing?Loop's first alpha scope turned a relationship-management idea into hard questions about imports, context, closeness, and what a brand-new user would actually see.
  60. Eight Weeks, Then LoopI left a new full-time CPTO job at Pinata to cofound Loop and start building an AI professional-networking product from scratch.
  61. 18:44 in McCarrenI ran 18:44.86 at the 2024 Dime McCarren 5K and finished second in the men's 40–49 age group.
  62. Can We Be Both?A cofounder conversation about Loop became a real negotiation over ownership, pay, Pinata, Amanda, and where we could build the company.
  63. Potential Co-FounderLoop moved from product collaboration into mutual references, working-style diligence, and an email subject that finally said the quiet part out loud.
  64. We Were Calling It LoopA relationship digest, a pile of prototype prompts, and a designer kickoff turned a loose RelateAI idea into something we were calling Loop.
  65. The Grill Learned BreakfastA new propane burner and three attachments turned one patio grill into a searing box, pizza oven, and flat-top breakfast station.
  66. We Agreed Not to RaceThree of us started the NYCRUNS Brooklyn Half with a no-drop plan. It became the most fun I had ever had in a race.
  67. The Car Grew a RoofI replaced the closed carrier on my Mini with an open cargo cage, then immediately started planning what could go on top of it.
  68. I Signed ItNine days after telling people I would probably pass on Pinata, I accepted the Chief Product and Technology Officer role and signed the offer.
  69. Forty, Phoenix, and an OfferI turned 40, flew to Arizona to help Mom with Dad's estate, and negotiated a startup offer from the other side of the country.
  70. Ninety-Four Floors UpA short Chicago weekend moved from the Adler Planetarium to sunset drinks above Lake Michigan.
  71. The Couch Finally ArrivedRockaway finally had a real couch, a pullout bed, and one less reason to call the condo unfinished.
  72. So Silly to Say Out LoudA scooter accident tore my rotator cuff just as two final interview tracks and the USOPC search reached decision week.
  73. My Ramen Got ColdA month into my New York job search, interviews, closets, dog-sitting, and a bike rebuild had filled every supposedly free day.
  74. By the End of Q1I moved back to New York, started a serious job search, and gave myself one quarter to find the next product and technology role.
  75. The Test Said Zone 2A Boston lab put numbers on my plan to get back into racing shape, including a 275-watt FTP, limited mobility, and a lot more easy work.
  76. Can You Limp to Worlds?A bad ankle turned the USA Triathlon Long Course Duathlon National Championship into a half-marathon limp, but the Team USA spot survived.
  77. Does Thanksgiving Need a Couch?The Rockaway condo was still half moved-in, but Thanksgiving was coming anyway.
  78. The Whole Bike Came Down to a ClampA missing seatpost clamp turned my older Pinarello Montello FM1 and an approaching Florida race into a search for one obsolete piece of metal.
  79. Not Bored Enough for the Wrong ThingAfter the cross-country ride and an overseas trip, I came back to New York, finished an Apply handoff, moved into Rockaway, and started looking for the right next project.
  80. The Bike Boom EndedWahoo closed RGT on October 31, 2023 after a difficult period for connected fitness and the indoor cycling market.
  81. We BackThree riders came home after 29 days, 13 states, 3,000 miles, 25 flats, two falls, and no days off.
  82. The Last StateNew Jersey was the last state before home, which meant one more day of bad jokes, tired legs, and getting the bikes to New York.
  83. The First RainWe crossed the Mississippi, found an Illinois rail trail, and finally got properly wet at the Wabash Cannonball Bridge.
  84. Arkansas Gets One PostTwo days in Arkansas included hay, rolling roads, attack dogs, an armadiller, night riding, and one combined update from Missouri.
  85. The SAG AwardBig Ted drove the little MINI, made the sandwiches, and kept our rolling circus moving across Texas and Oklahoma.
  86. Dead Biker PassNew Mexico gave us art, hot springs, Taos, the Rockies, and a road sign with an aggressively specific warning.
  87. America's Greatest Bike TrailArizona gave us red rocks, rough roads, Winslow, the Continental Divide, and a 75-mile-an-hour bicycle trail called Interstate 40.
  88. We Don't Talk About Day 5The first five days brought desert heat, strangers, Route 66, a night ride, and enough mechanical trouble to earn one very short update.
  89. 2,913 Miles to GoWe left the Pacific in Santa Monica with two bikes, one very long route, and most of the country still in front of us.
  90. The Bike Was Still in the OfficeI exited Wahoo, asked for a few extra days of badge access to retrieve my bike, and started recruiting support for a ride across the United States.
  91. Where Did the Shoe Go?A hard turn on a descent tore the cleat plate out of a cycling shoe and left the cleat attached to the pedal.
  92. How Many Bikes Fit?An early River Road personal best ended at a Piermont deck where bicycles outnumbered chairs and number 1,426 still counted.
  93. My Job Moved FirstWahoo wanted my role in Atlanta, so a two-week stretch began with H2 planning, canceled meetings, and an indoor bike because it was 91 degrees.
  94. Thanks for the Reserve PoursA west-coast vacation produced a winery photo, two PEJU receipts, and one thank-you note for the extra tasting.
  95. Simplifying, ApparentlyA Rockaway closing, a cash offer in Cornwall, two Highland land plots, and one small balcony went into the same July spreadsheet.
  96. I Missed the ContractThe Rockaway closing packet had contracts, riders, disclosures, wire instructions, and one completely unsigned contract.
  97. The Fire Pit StaysA verbal Rockaway offer came with nine patio items, one mortgage contingency, and a spreadsheet for what stayed.
  98. How Long Until Zillow?A two-night Rockaway Beach weekend turned into open houses, neighborhood research, and a 70-page park plan.
  99. It Looked ReadyGetting the Cornwall house ready for short-term rentals meant paint touchups, spring cleanup, a bounced bulk-pickup request, and too many appointments.
  100. Which Part Was the Art?A free Sunday at the Getty Center left three photos, all of Robert Irwin's Central Garden and none from inside the galleries.
  101. Mom Gets the DaySanta Monica moved Apply cofounder work to 7 a.m. Pacific and pushed a Wahoo standup aside for Gisi's birthday.
  102. 718-400-WOLFA Shopify login, a Printful account, one vanity phone number, and the old coffee-drinking wolf became a real side-project stack.
  103. A Kind Man in BlackA 17:24 5K, a 2:59 Boston Marathon, and the last 800 meters I did not expect to run with somebody else.
  104. The Houses Dad BuiltA 68-page scan of old construction photos arrived just before Norm Fischer died, then came back into view at his celebration of life.
  105. I Need GitHub AccessA one-line access request put Wahoo's code repositories, my existing GitHub account, and a very Wahoo workstation in the same afternoon.
  106. What Is That Ruin?A run to the south end of Roosevelt Island stopped at the roofless Smallpox Hospital beside the East River.
  107. Who Signed This?Banksy in New York put an unauthorized exhibition, a map of city works, and a room full of stencils at 378 Broadway.
  108. Poughkeepsie or West?A Hudson Valley rental search and a possible move West were both real plans during the same week back in New York.
  109. The Time Zone ChangeAn unexpected family week, Wahoo user research, and a long-planned trip to Switzerland all met in the same inbox.
  110. The Vet NoteEva's vet note arrived while Wahoo, Apply, travel, and the first workweek of the year were all starting up again.
  111. My Next Profession?A Red Hook pizzeria near a new running track briefly looked like a runner's bar, pizza place, and entirely reasonable next business.
  112. Napa, Then Back to the GrindA five-person wine tasting at Turnbull turned one Monday in California into a short Napa itinerary.
  113. Fifth, Then FirstI ran a half marathon PR, handed the CIM relay to Ted in fifth, and watched him bring us home first out of 418 teams.
  114. Thanksgiving Is Just a Lot of WorkThe turkey needed a brine, a wire rack, a plan, and more coordination than anything else on the Thanksgiving table.
  115. Can We Enable AirPlay?NYC Marathon weekend ran straight into an Atlanta Wahoo trip, two Apple TVs, SYSTM testing, group rides, and an indoor invitation back in Manhattan.
  116. Both Screens OnWahoo X launch week moved from a team note and bundle copy to RGT on the television and SYSTM on a tablet at home.
  117. A Little BreakAmanda's birthday and our ten-year anniversary took us to Cusco and Machu Picchu after a week of Wahoo travel and Apply work.
  118. Open the Next Line SheetApply launched a LACMA collaboration while museum wholesale, production files, and my new Wahoo job all kept moving in the same week.
  119. Not Much of a BedroomA new KICKR turned one corner of the New York apartment into the place for early rides before work.
  120. Lewis and Clark AdventureA Saturday ride found train tracks, mud, lily pads, and a route that made more sense after Strava drew the line.
  121. I'm on PTOA Colorado trip with Amanda and Eva still found room for Wahoo's new sports science center, an all-black logo, and cheap pizza.
  122. This Week Is a Little NutsA first real Atlanta work trip landed between product teardowns, Apply reports, a hot long-run idea, and another bike problem.
  123. Achievement UnlockedWeek two at Wahoo mixed subscription and running-product work with a stuck Apply marketplace integration and plans to crew the Leadville 100.
  124. Welcome Home. Get to Work.I picked up keys to an Atlanta apartment, started leading Wahoo's subscription business, chased my moving truck, and kept Apply moving too.
  125. The House Came With a ListThe first weekend at the Cornwall house included a couch, a grilled dinner, a rainstorm, and a project list before most boxes were open.
  126. Launch. Chapter 11. One Year.TRX Training Club launched on June 8, 2021. One year later, the company announced Chapter 11. Both dates belong in the story.
  127. Soon to Be an Official WahooliganI signed the Wahoo agreement, then went straight back into RGT to build a route, find its riders, and test the no-drop feature.
  128. Burying the Lead a BitI applied to Chicago Booth without an undergraduate degree while a Wahoo offer, a house purchase, and Apply all kept moving.
  129. Potentially Bringing a BikeA Wahoo visit in Atlanta collided with a house purchase in Cornwall, Apply work, and one very important packing question.
  130. Not Out, But Mostly EmptyA 65-mile ride to Cold Spring led into a storage pod, movers, and one weekend spent consolidating the house without quite finishing the move.
  131. Cycling Cycling CyclingTesting power pedals and Wahoo SYSTM made the product questions inside an active Wahoo interview process much less theoretical.
  132. Thread the NeedleA TRX work week in California ran directly into two days of Wahoo interviews in Atlanta, with one narrow travel handoff between them.
  133. The House Still WorkedCalifornia work kept pulling harder, forcing a choice between ending a Cold Spring rental I loved or finding a careful way to keep it.
  134. Just Coming Back From VacationA California weekend with Amanda ended in a week of Apply production, Wahoo interviews, new startup conversations, and a house that fell through.
  135. One Twenty, Then Strategy DayAmanda and I ran New Orleans, then Apply went straight back to museums, licensing reports, and a Friday strategy day at WeWork.
  136. The Peugeot Got WeirdAn old steel Peugeot frame, a modern one-by drivetrain, and two sets of pedals became my January bike project.
  137. Sorry for the Long DelayApply had licensed art, partner payouts, and more than a year of reporting I needed to get squared away.
  138. It Is Not ITTRX and Apply were in their holiday push when a restaurant concept asked me to help define and vet its first real technology leader.
  139. The Fun HouseA rushed Hudson Valley house offer pulled Amanda, Eva, lender paperwork, and a possible new version of home into the same three days.
  140. Confirmed Turkeys ExistThanksgiving required a turkey, Apply was testing sticker NFTs, and TRX version 10.1.1 kept moving through TestFlight.
  141. Pumped to Meet YaApply hired somebody to own fulfillment just as a 45-order weekend hit, while TRX builds and the Newport Beach commute kept moving.
  142. The Crew Side of the CourseA Javelina race weekend began with last-minute errands and became a long day among tents, cactus hills, and waiting.
  143. Forget the TimeAt the 2021 Chicago Marathon, I changed my goal and stayed with a teammate who was having a hard day.
  144. A Solid Race, Then SpamThe long-course bike leg was honest about my preparation. The next start line depended on recovering a registration email from spam.
  145. The Bike Came TooA work apartment in Newport Beach needed lights and furniture, but I unpacked the race bike and put it on a trainer first.
  146. Is There a Red Kit?USA Triathlon made my All-American status official, and I spent four emails trying to find out whether a national champion kit came with it.
  147. 10.0.7 to 10.0.10Four TRX app versions moved through Apple while I flew from New York to Newport Beach, sorted product details, and tried to keep one foot in Apply.
  148. No Apps Available to TestThe first weeks at TRX included an App Store approval, an empty TestFlight screen, a first digital operating review, and a new commute to Newport Beach.
  149. LIVE Was Too LiveTRX spent money making live classes that disappeared when the stream ended, so a short product brief grew into the Replay feature.
  150. Really Anything Would HelpI rented a Newport Beach apartment I had not seen while TRX product briefs and fourteen-hour meeting days filled the week before move-in.
  151. Are We Done?!Five years after buying a damaged Poughkeepsie Victorian, the permits cleared, the final papers were signed, and the house finally closed.
  152. Woah, Shit's BrokeTesting the TRX class flow produced an error screen and two very direct product alerts in under two minutes.
  153. Newport Pool PartyA Newport Beach apartment turned the new TRX job into a real split-coast routine while Apply and New York kept moving.
  154. Wonky MarathonsPPTC's marathon group came back with three mileage plans, Discord channels, virtual office hours, and no official group runs.
  155. I Won NationalsI finished the sprint duathlon in 1:05:58 and won the men's 35–39 draft-legal national title in Tuscaloosa.
  156. Far Beyond ExpectationsAn egress window, rebuilt porch footings, a full trash-out, and an impressed inspector pushed the Poughkeepsie house toward one more showing.
  157. Good Feels All AroundI signed the TRX offer, asked for a May 10 start, then sent a six-part getting-started list three minutes later.
  158. The Offer and the DumpsterThe TRX offer arrived while I was packing the Poughkeepsie house, comparing movers and storage units, and trying to put Apply's value proposition into plain English.
  159. Amazing Team, A Lot of WorkA visit with the TRX team in Newport Beach left me excited about the brand, clear about the hard parts, and ready to talk through the offer with Amanda.
  160. Maine Wanted Wet InkThe sale of my first Portland apartment needed a physical deed, a second notary run, and an Apply call moved at the last minute.
  161. A Miserable WeekTwo home sales ate the week while Apply kept moving and a late Rapchat proposal pulled me back toward music and startup work.
  162. They Hadn't Seen ItThe Poughkeepsie house got an offer three days after listing, before the buyers had walked through it and before the permit mess was finished.
  163. The House Was Mostly EmptyAfter years rebuilding a wrecked Poughkeepsie Victorian, I cleared it out, argued for the simplest permit path, and booked the listing photos.
  164. The Product Test Was a WorkoutApply was launching, I was moving apartments, and my TRX homework involved live classes, sore muscles, and a lot of product notes.
  165. Someday Never ComesA Rapchat architecture review found an old stack, a future rewrite, and a team trying to grow the system it already had.
  166. Thirty Minutes BeforeI broke my hand on a trail run half an hour before a TRX conversation, then had to ask how the workout product handled one usable hand.
  167. 318 Active DaysStrava counted 4,573 miles in a year with almost no racing, while I arranged two moves and started new conversations with a Brooklyn run team, TRX, and Cutback Coach.
  168. 1,153 Beta FormsApply Stickers opened a six-day beta signup, collected more than a thousand mailing addresses, and turned my inbox into a Typeform notification machine.
  169. A Lot of HoursApply was busy, the Poughkeepsie house had a leak and ancient wiring, and I still said yes to helping Rapchat and Cutback Coach. COVID had left a lot of hours in the day.
  170. Tempted (Joking)A wholesale coordinator job at the Poughkeepsie Farm Project landed in my inbox while I was building Apply. The joke was that I might want it. I sort of did.
  171. I Picked a Bad MorningElection stress sent me out for a Thursday bike ride. A few hours later I was in the ER, apologizing in advance for concussion typos.
  172. All Hands on StickersApply launched into an ecommerce order spike, a broken payment method, finished financing, and a bubble-mailer shipment waiting on customs.
  173. We Are OfficialApply launched its 2020 voting-sticker campaign, then the founders stayed close to the support inbox and the first shipping questions.
  174. First, Fix the DuctsTwo weeks before Apply's launch, I turned an old house's HVAC work into three phases so one expensive problem did not stop everything else.
  175. Pumped To Have You AboardOne early believer decided to back Apply, and the company moved one step closer to turning a very fun deck into a funded business.
  176. It Looked RejectedApply had products, a live Instagram account, and a store nearing launch. The connection between all of them still refused to work.
  177. Averages Won't WorkA clean churn chart hid the real questions about who was exercising, who was renewing, and whether the product had become a habit.
  178. A Pretty Big LiftI had wanted to ride across America for years. COVID turned the supported version into a much stranger solo plan.
  179. No D1 Athletes From TexasThe Plague Games turned four canceled-race months into track time trials with GPS proof, tiny groups, pizza, and very specific anti-stacking rules.
  180. The Database Was a SpreadsheetApply needed to turn a growing pile of art files into a beta-ready reporting system, so the first database started in Google Sheets.
  181. Order #1001Apply's first Shopify order was mine: three stickers, two notification emails, and a launch still a few weeks away.
  182. Mail Back the Bike KeyCOVID put me in the old Poughkeepsie house for real. A few days later Aaptiv asked for the bike-locker key and a decision about whatever was still on my desk.
  183. A Ridiculous MonthPart of the ceiling came down, the repairs became my job, and our temporary move to Poughkeepsie stopped feeling very temporary.
  184. One Hundred Percent ApplyI passed on the safer job, stopped treating Apply like a side project, and started building the company full time.
  185. Aaptiv, From HomeAaptiv's at-home fitness use jumped, and the company opened a new enterprise and API channel.
  186. The Gutters Fell InThe Poughkeepsie Victorian started leaking during lockdown while I finished references, left Aaptiv, and weighed a CPO offer from Equinox Media.
  187. Pack Up And Price UpApply Stickers had a bright yellow financial model, a two-to-five-dollar fulfillment problem, and a lot of COVID assumptions to test.
  188. The Training Sheet Just StopsA 2020 race plan recorded illness, a sore Achilles, and several target races before the schedule stopped during COVID.
  189. Every Rep Leaned LeftA 16-by-400 workout looked fast and consistent, but every repeat showed the same small pacing mistake.
  190. Only One HundredA leadership search wanted someone who had managed 200 to 500 engineers. My org was only about 100, which was suddenly a small number.
  191. Finish Interviews. Learn Stickers.After arranging a possible Aaptiv transition, I planned to finish a few big-tech interviews and learn enough about Apply to decide whether stickers were next.
  192. Two Titles, Both Question MarksA working note reduced a new opportunity to two possible roles and a longer list of questions about people, economics, and the work itself.
  193. The Side CompanyApply Stickers started as a small side business while I was still working full time at Aaptiv.
  194. Two Broken TreadmillsA messy California International Marathon taper ended with a handmade 2:47:30 pace band and a 2:47:55 finish.
  195. Skip That Bachelor'sCornell encouraged me to apply for its Executive MBA Metro NY program even though I never finished college. I got excited before I got careful.
  196. Tell Me the Truth, LinkedInAfter years of building startup teams, I started asking what a much larger technology company might offer and what I would have to give up.
  197. Twenty-One, Then WorkThe New York City Marathon became a 21-mile training run. I paced a struggling friend, stopped before the finish, and kept the next workweek intact.
  198. Nobody Feels PerfectThe night before the Chicago Marathon, I was calming down the runners I coached while rebuilding my own fitness after six weeks in a boot.
  199. Nine Out of TenA recruiter suggested I talk to a venture firm. I explained the unfinished degree, years inside startups, and why most firms might still say no.
  200. The Wrong Kind of UnicornThree recruiters pitched senior engineering roles at giant companies. I sent them the same answer: impact, ownership, and an interesting problem.
  201. God Awful, Works GreatA torn plantar plate put me in a boot. The ugly shoe balancer fixed my hip while I coached 187 runners from the sideline.
  202. The MRI Voted NoThe MRI found a chronic partial tear in my right forefoot, so I deferred Berlin, got a boot, and asked if swimming still counted.
  203. Great. Over One Hundred Bats.An inspection found more than 100 bats in the Poughkeepsie attic. I called the exclusion plan reasonable and told the contractor to start.
  204. Finish, Not TimeThe Vermont 100 was crazy hot. I stopped chasing the clock, finished in 27:13, and went back to writing Tuesday's workout.
  205. Not Allowed to QuitThe crew plan for my first Vermont 100 was simple: bring food, track the math, and do not let me make bad decisions.
  206. One Hundred Eighty-SevenThe PPTC Marathon Training Group had 187 runners, one volunteer coaching crew, and a lot of TrainingPeaks accounts to load.
  207. Two Forty-Five, PleaseI bought a marathon plan from Brad Hudson, marked it up, then brought the questions straight into Aaptiv.
  208. No Tricks. No Shortcuts.We built a twelve-week Aaptiv running plan with base miles, hills, tempo work, long runs, recovery, and a taper before race day.
  209. A Party With Long RunsI joined PPTC's 2019 marathon training group as a coach and found a signup list with a lot of different times and experience.
  210. The Foot Did ThirteenLess than six weeks after my first Alter-G run, the Brooklyn Half put 13.3 GPS miles on the foot that had stopped my spring.
  211. Chili, Recovery Socks, Hair MetalRock The Ridge started as a completely unreasonable podium attempt and became 50 excellent miles of bad math, aid-station chili and survival.
  212. No Worlds. Maybe Fifty Miles.A healing foot took the duathlon world championship away, while I tried to make a 50-mile qualifier sound like the sensible alternative.
  213. Sixty PercentMy first run after the NYC Half lasted 30 minutes on an Alter-G treadmill at 60 percent body weight.
  214. The Book Was Too BigI finished the RRCA coaching course in Poughkeepsie, then immediately asked if the giant manual came in an iPad version.
  215. One Eighteen, Blown FootI ran 1:18:23 at the 2019 New York City Half, hit the time I wanted, and wrecked my right foot doing it.
  216. Three Out of FourI ran for the Prospect Park Track Club board with a phone-typed pitch for our great, wild and weird club.
  217. Thirty-One Miles, Then EvaI ran a low-key 50K with friends as early training for two ultras, then recovered on the couch with Eva.
  218. Stop NoahOur Cherry Tree relay team ran 54:44 in Prospect Park. My leg averaged 5:29 and gave me the 17:01 I had been looking for.
  219. No Code, Still InCyral asked me to advise on database security. I wanted the work, but first I sent Aaptiv a plain conflict check.
  220. It Needed Two HandsProspect Park Track Club won the NYRR Open Men B division, so twenty of us put on suits and collected a very large glass trophy.
  221. Still Alive, Mostly RunningWork, the loft, and basic life admin were a mess. Early runs, commute miles, the Armory, and a winter trail day were still happening.
  222. Dingleberry Was My Favorite WordAmanda and I brought party rollups to Harry's Handicap, where start times were staggered and the potluck included a contest for the best word.
  223. Fifty-Four Fifty-ThreeA cold Ted Corbitt 15K put me on the PPTC record list, then the week went straight back to club runs and volunteer points.
  224. Course Map, IshA Zipcar, a guessed-at Strava route, and a muddy 10K with the Prospect Park Track Club crew.
  225. Five Miles, Not Twenty-FiveA bitter-cold forecast had runners dropping from five miles to two. I asked about moving up to 25K, stayed in the five, and ran 30:42.
  226. Three Minutes to SpareI needed 2:59:59 in my first New York City Marathon. I finished in 2:56:51, twenty seconds slower than Chicago and safely under the line.
  227. GAP at SixI went looking for three winter running partners at Grand Army Plaza and accidentally found a group.
  228. Two Fifty-Six and an Ice BathI ran 2:56:31 at the 2018 Chicago Marathon, then sat in a hotel bathtub trying to get my legs back.
  229. No Day Pass. Still Ran.A Paris gym would not sell me a day pass, so I found a 400-meter track and ran five mile repeats while keeping an eye on a sore foot.
  230. Runner to Runner :)I wanted old NYRR data for a Prospect Park Track Club side project, so I emailed the runner who built RunGraphs and asked for his scraper.
  231. Second Was the PlanI traded the Fifth Avenue Mile for a small Peekskill 5K near the house, brought a faster friend, and aimed for second overall.
  232. The Bib Arrived EarlyI thought my Brooklyn Half time was for 2019. Prospect Park Track Club found me a 2018 New York City Marathon bib instead.
  233. Twenty-Eight Miles, Fifteen PoundsI carried a fifteen-pound pack through a wet 28-mile Catskills weekend with 6,500 feet of climbing.
  234. The Race Stayed in BedI asked how hard to ride Staten Island's 20K bike, then decided at 5:45 a.m. that staying in bed was the better plan.
  235. The Race I Blew, We WonA bad five-miler in 97 percent humidity became a team championship, then forced a harder question about work stress, a sick friend, and what the body carries.
  236. Second Fastest, Still TrainingA 17:56 5K landed in the middle of a heavy run-and-bike block, complete with tired legs, bad fueling, and a map of the miles it took just to leave New York.
  237. Twenty-Two Million, Then the WoodsAaptiv's Series C was public. I carried 35 pounds into Echo Lake, ran a ridge in absurd rain, and got the mental escape I needed.
  238. Second by Four SecondsI had the fastest bike split at the Tri One On duathlon, then ran an extra 300 meters and missed the overall win by four seconds.
  239. I Nearly Melted DownA month of 12-to-14-hour startup days left me exhausted and injured, even while I ran a marathon qualifier and a 17:45 road 5K.
  240. My Laptop Ran the 5KI jogged to the Al Goldstein 5K carrying work clothes and a laptop, then looked back at the year that made running feel like a team sport again.
  241. The Leg HeldA questionable leg, a borrowed bib pickup, cold rain, and a 1:20:44 Brooklyn Half that put me under the New York City Marathon time standard.
  242. The Thirty-Minute Coaching CallA call with world champion triathlete Lesley Paterson became both a real attempt to improve my duathlon training and a premium-coaching product example for Aaptiv.
  243. 375 Miles, Then the PlaneSeven days at Trek Travel's South Carolina Ride Camp put 375 cycling miles and 20 running miles into my legs. The flight home was the part that caused trouble.
  244. Fourth, Then Team USAI finished fourth in my age group at the national draft-legal sprint duathlon and earned a Team USA slot.
  245. One Hundred Twenty EggsI bought 120 eggs and hosted the dyeing crew for Prospect Park Track Club's Easter egg hunt.
  246. Odd Hours in IcelandFour nights, four stops, two South Coast routes, and a work call I was still trying to coordinate from Iceland.
  247. Good Idea or Crutch?A slow-healing calf took the Snickers Marathon off my calendar. I had a pair of inserts, a bike, and a new half-marathon target.
  248. Users Don't Want to SearchA friend asked why Aaptiv had no search box just as we were rebuilding the home feed and onboarding around a different idea: help people browse.
  249. One Day Between TenantsThe old tenant, the new tenant, one service elevator, a missing form, a missing key, and a very small window to turn over my Williamsburg loft.
  250. Run, Eat, Drink, OrganizeThree months after joining PPTC, I moved from morning and weekend group runs onto the club's Social Committee.
  251. Nine in the Storm, Seven AfterI ran nine miles during New York's bomb cyclone, then went back out at 6:00 the next morning for seven more.
  252. Do I Buy Two Bibs?Running both Cocoa Classic distances was the plan until snow converted the races, just as a 50-mile training plan arrived.
  253. List the Loft ImmediatelyAn early lease exit turned my 60 Broadway loft into a fast listing, showing, application, and lease sprint while the building was wrapped in construction plastic.
  254. Nowhere Near EitherI wanted a sub-17 5K and a sub-2:54 marathon. My current times, irregular schedule, and old training calendar showed the gap.
  255. Find a Workout, Miss a RaceI wrote five ways to get new Aaptiv members into a first class while working late kept me out of the OSR10K.
  256. Very Close, FinallyThe Poughkeepsie rehabilitation was nearly ready for bank sign-off after an unexpected drainage problem held up the work.
  257. Better Than the SubwayAt Aaptiv, I could run or bike to the office, train with coworkers, and work on a fitness product I used myself.
  258. Sixty People, Two Hundred ThousandAaptiv had reached about 60 people and 200,000 paying members. I was recruiting, reviewing Peloton, and logging searches that returned nothing.
  259. The Result Was WrongMy race-day email said 41:15 and sixth place. The official result said 41:47 and tenth, and my left leg still needed a doctor.
  260. Five Twenty-NineI ran 5:29 at the New Balance Fifth Avenue Mile, less than two months after my first 5K back.
  261. The Battery Door BrokeA broken battery door put my Stages power meter out of service until a replacement cover and O-rings arrived.
  262. Take the Cassette ApartI signed up to learn bicycle maintenance, pulled apart a rear wheel, and ended the day debugging a power-meter update.
  263. My Cell Worked InternationallyAmanda and I moved through Berlin, Prague, and Warsaw while Aaptiv hiring and a half-renovated Poughkeepsie house kept reaching me.
  264. Twenty Forty-FiveFive months after a stress fracture put running on hold, I raced a Prospect Park 5K in 20:45.
  265. Seventeen CSVs LaterI turned Aaptiv activity data into seventeen queries covering the path from the home screen to a completed class.
  266. 44:04Forty-four minutes and four seconds put a number on my PPTC Al Goldstein Summer Speed Series 5K finish, with an early cycling slot two days later.
  267. The Tub Was on the WayA bathtub, a vanity, one tile measurement, and a scheduled power restoration moved the Poughkeepsie Victorian past another planning phase.
  268. Make It SleepableI could not finish planning the Poughkeepsie house from New York. First it needed water, heat, one bathroom, and somewhere to sleep.
  269. Open the Door RemotelyA possible leak below my old Portland loft turned into a fast remote response while I was living in New York.
  270. The Network Kept WorkingA recruiter from Reonomy, a product colleague from Peek, and friends from the Shutterstock years all resurfaced while I built the team around Aaptiv.
  271. Find the CapitalThe Midwest housing project needed cash, so I started asking whether old startup equity could fund the next thing I wanted to build.
  272. The New Job Was RecruitingJoining Aaptiv meant building the team, and I needed people who could help me find engineering, technology, operations, and business leaders.
  273. Champagne and Big Buck HunterI gave a short-notice night with friends and colleagues two goals: a giant bottle of champagne and a round of Big Buck Hunter.
  274. After Work Kept GoingMy move to Aaptiv happened faster than I planned, while spinning, a stress fracture, apartment repairs, and friends' startup questions filled the edges.
  275. Thirty Calls This WeekI went straight from joining Aaptiv into board prep, thirty recruiting calls, and two nights a week in Python class.
  276. Cancel the ContractMonths of diligence changed the economics at Rustic Meadows. The seller rejected our new position, so we ended the deal and protected our earnest money.
  277. Find Bus OneAmanda and I went to Washington with friends for the Women's March, then spent the evening getting four people off a delayed Metro and back to Bus One.
  278. I Feel Fucking GreatI resigned from Reonomy, accepted Aaptiv's CTO and VP Product role, and started learning the mobile stack before my first day.
  279. What Do I Do Today?While I was considering a role at Aaptiv, I tried the workouts and wrote Ethan about navigation, training plans, class data, and recommendations.
  280. I Hired No ManagersAt Reonomy, I hired individual contributors with room to grow and promoted managers from the product and engineering team.
  281. I Needed a Peaceful NightAfter thinking nonstop about an offer from Aaptiv, I declined because I still wanted to build a company from the beginning.
  282. The Gear Was GoneA Catskills camping weekend ended with a stolen phone, tent, sleeping bag, and the start of replacing what had disappeared.
  283. Our Side Was SignedAfter months of park visits, documents, and diligence, we sent the seller a signed purchase agreement before Thanksgiving.
  284. The Tank Was the ProblemA tight powder room turned one toilet into a week of measurements, water-pressure questions, and old commercial plumbing.
  285. Something More RewardingReonomy had become hard enough that I stopped casually wondering about other jobs and started a real search.
  286. Measure the Concrete PadsBlue Sky's first mobile-home-park site visit meant flying to Missouri, interviewing the manager, checking the records, and measuring concrete pads.
  287. I Put in NoticeI put in notice at Reonomy, watched the organization change around me, then chose to stay long enough to protect the mobile-home-park deal before flying to Paris.
  288. A Little Out of Left FieldMy work had widened from technology into designers, product owners, and business models, so I asked InVision for a product conversation too.
  289. Two TracksA request for IT leadership candidates became a wider conversation about the work, the team, and whether I might want in.
  290. Morning, Twilight, MorningA Cozumel dive weekend had one simple rhythm, plus a night dive that never fit neatly into the schedule.
  291. Still OutsideA Catskills backpacking return and an all-day Habitat for Humanity shift kept the week's plans moving around.
  292. The Park Got RealA rejected Indiana mobile-home-park inquiry led my partners and me to Missouri, a property visit, and a much more serious side project.
  293. Continuously Shipping ValueA newly created engineering-director role recognized the kind of cross-team leadership Reonomy needed next.
  294. What Else Do You Need?After weeks of closing paperwork, the Poughkeepsie conversation finally changed to permits, power, and what the contractor needed to begin.
  295. Like Learning a New SportI sent a friend my plainest advice for learning to code: start with a reason, choose Python, save the work, and keep trying.
  296. Hyper MinimalMy favorite one-on-one format used five repeated questions, fifteen minutes of discussion, and very little ceremony.
  297. The Last Thing for UnderwritingA missing title company, another contract extension, and one final bank request kept the Poughkeepsie house almost ready to close.
  298. Forty-Eight WeeksReonomy was looking beyond the usual recruiting channels, and a nearby startup pointed me to a full-year engineering internship program from NUS.
  299. Already Under ContractMy partners and I found a mobile-home park in Fort Wayne that matched our plan almost exactly. Somebody else had reached it first.
  300. The Beam Was CutThe inspection on the Poughkeepsie Victorian found a cut basement beam, a sagging floor, and a renovation list that kept getting longer.
  301. More Interesting Than ExpectedA short conversation with Vimeo left important questions untouched, but the company itself gave me a reason to keep talking.
  302. A Lot of HorsepowerMy answer about Reonomy was short: I loved the team, the work was expanding, and the next few months would tell us a lot.
  303. Almost Ready to ShowThe side project had moved from an idea I kept describing to something I hoped a trusted friend could try within weeks.
  304. Too Much for One CallA conversation about my Shutterstock years made one thing clear: I still wanted the mess and momentum of building early.
  305. Buy the Router That WorksBetter Wi-Fi and a connected lock turned a small network problem into a short list: test it, pick it, and move on.
  306. I Wanted Better Work ToolsThe software I kept thinking about was simple to describe: tools that helped people and managers do better work together.
  307. Clear the DesksOneButton Studios turned its Brooklyn office into a small Friday-night venue for drinks and a live set by Spider.
  308. Same Flights, Same CampA group of friends booked a week of road riding in South Carolina, giving the spring training calendar a real shape.
  309. One or Two ParksI was looking at mobile-home parks across the Midwest and wanted to understand why the market felt so inefficient.
  310. I Need a ManagerI had let the management system slip while Reonomy grew, and the number of direct relationships was no longer workable.
  311. Two Days of ScalaA private Scala workshop gave the Reonomy engineers a common place to start, even though they came in with very different experience.
  312. Four Buttons, Somehow ImpossibleLoft 2.0 had smart bulbs, a mounted television, and new audio, but the custom light-and-shade remotes took an entire day to find.
  313. Can We Just Kill It?Two low-value Reonomy features needed different shutdown plans because one was written into contracts and the other still had a few users.
  314. Toilets Would Be a Huge WinChristmas break at my childhood home meant exposed plumbing, gas-line work, bathroom floors, and an ambitious hope to install the fixtures.
  315. The Offer LandedA December engineering offer moved through questions, missed calls, and benefit details before the candidate chose to join Reonomy.
  316. Nine Months, Crazy ShitA year-old introduction resurfaced after nine months at Reonomy, and the company already felt both brand new and a decade old.
  317. The Hole Before the RoadNine months after I joined Reonomy, a long onboarding email showed why new engineers needed the product history as much as the preferred architecture.
  318. The Director Search Woke UpAfter pausing the role in September, I spent early December turning engineering-leadership referrals into calls, breakfasts, and real conversations.
  319. Bourbon and Trailer ParksA Thanksgiving trip to inspect mobile-home parks turned into an introduction for bourbon, space landings, and another strange business conversation.
  320. Sunday at Noon, AutomaticallyThe manual Mixpanel usage check became a weekly CSV report that would arrive automatically every Sunday.
  321. Twelve Miles to a 5KAmanda and I registered for a Thanksgiving 5K in Colorado Springs after confirming the race was only about twelve miles away.
  322. Medium Data, Not Big DataDinner with startup friends turned into a late-night note about hiring, users, APIs, and why their business did not need a giant data stack yet.
  323. Address In, Property ID OutA custom address translator was nearly ready to connect a customer's loan system with Reonomy's property data.
  324. A Few Days LateA former employee asked to exercise vested options just after the window lapsed, and I argued that being legally clear did not settle the fairness question.
  325. Scala Goes to LAReonomy was finishing a rebuilt data-processing pipeline for Los Angeles while I looked for temporary help to expand the ingestion team.
  326. The Map Became TreesAfter two weeks of deed and easement research, I finally walked the wooded Hudson Valley parcel I was considering for a vacation place.
  327. CTOs, Tech, Then a DateA portfolio CTO gathering in New York was good enough that I asked the hosts to connect everybody after I left early for a date.
  328. Ownership, Meet SalesforceReonomy's first ownership-data integration needed a thin API layer, a property ID, and a useful object inside the customer's CRM.
  329. Right of Way, Not RefusalA possible vacation-home parcel near Woodstock sent me into deeds, easements, flood maps, liens, and one quick real-estate vocabulary correction.
  330. The Numbers Did Not MatchMixpanel and Intercom disagreed about Reonomy usage, so I spent a day comparing them and built a manual plan we could trust for now.
  331. Tell Me AnonymouslyBefore Reonomy finalized its company values, I asked the team to say what mattered through an anonymous form or a direct conversation.
  332. Delete My 1:1sReonomy's product and engineering teams had grown, so I replaced a crowded recurring calendar with open office hours and regular goal reviews.
  333. No Email, Lots of BrickA nearly offline weekend in Indiana opened up a doorway and moved my childhood-home rebuild into a much more visible phase.
  334. Mail the Key to MaineMy furnished Portland loft needed a renter, a mailed building key, and a phone-based smart key for the front door.
  335. CTO, Ironman FinisherA short 2015 bio tried to fit startup leadership, Shutterstock's IPO years, Reonomy, and endurance sport into one paragraph.
  336. Run Club Ran LongA 4.54-mile company run down the West Side turned into snacks, drinks, and a much longer evening than planned.
  337. Run Gear Was a Bad CallI rushed into a meeting dressed to run, got called on it, and stopped defending my own standard for punctuality.
  338. Indiana With a HammerAnother trip to my childhood home meant plumbing, carpentry, and the slow move from demolition into rebuilding.
  339. Hold the DirectorI paused an engineering-director search and decided Reonomy needed several team leads first.
  340. Not a Second JobI started sketching a consultancy network that could create a second income stream without becoming another full-time job.
  341. Urgent, MaybeSeveral Reonomy product problems arrived as urgent reports, and the first job was separating a real outage from a narrow bug or known issue.
  342. Peer Pressure WinsA teammate's first Photoshop and Illustrator class showed the kind of self-guided learning culture I wanted at Reonomy.
  343. Party by FiveAn all-day Reonomy hackathon mixed prototypes, Xbox games, drinks, and two ideas that looked worth taking toward production.
  344. Button This UpReonomy's new office needed internet, phones, weekend access, and one final push before the team could work there Monday.
  345. Sweating, Dirty, Burning ThingsAfter Gisi died, my brother and I started clearing and rebuilding the DeMotte house, and I realized how much I had missed physical work.
  346. It Went Out EarlyA feature reached production before it was supposed to, and the repair started with an apology to the teams who depended on the release process.
  347. VP Engineering, Pulling CableI came back from family matters to an office move and an urgent search for somebody who could pull Cat5 cable.
  348. My Mom Died YesterdayGisi died suddenly, so I headed toward Chicago with no arrangements made and a work calendar that had not moved with the rest of my life.
  349. A Pubic Hair AwayWe needed a narrower product, a reliable data API, and mock routes that let the front-end and data teams work in parallel.
  350. Bittersweet DinnerAmanda and I planned a last-minute dinner for a promotion that felt worth celebrating and stressful at the same time.
  351. Pick a WikiReonomy needed one searchable place for its processes, and I did not want the tool choice to become another long project.
  352. Placid Was OutThe back injury made an Ironman at Lake Placid unrealistic, so I asked to transfer the entry and considered going only to cheer.
  353. The Familiar TingleOne bad deadlift repetition turned a familiar warning in my lower back into pain, lost mobility, and an impossible workday.
  354. Dead in the WaterMy phone kept losing data in New York, which meant losing the calendar, Uber, and most of the systems holding the day together.
  355. Stop Everything MondayRecurring outages had become serious enough that I ordered a full work stoppage until two critical blockers were resolved.
  356. Pre-Profit InternetMoving Reonomy into a new office meant finding business-grade internet without spending like a business that had profits.
  357. Brass Tax and ValueA smarter-home side project had code, possible partners, and plenty of ambition, but not yet a reason to form a company.
  358. Wildly UngroomedThe backlogs were a mess, so we put the work on a wall and started building a cadence around it.
  359. So Fucked for PlacidLake Placid was getting close while work, moving, and training were all fighting for the same hours.
  360. I Quit the MoniesThe shortest explanation I had for leaving a public company to join an early-stage startup.
  361. One CalendarMy first full-time week at Reonomy started with one small, excellent change: three calendars had finally become one.
  362. One Last HandoffMy final week at Shutterstock was about transferring every remaining responsibility before starting at Reonomy.
  363. A Hundred Hours InRoughly 100 hours of early Reonomy work were enough to make me want to give the company my full attention.
  364. Training Fell ApartGetting sick, closing on a condo, and interviewing for a new job pushed training out of my schedule.
  365. The Deck Before the JobBefore I joined Reonomy, I made a deck covering cross-functional product teams, engineering leadership, hiring, and onboarding.
  366. The Loft Was MineAn ID, a checkbook, and one final confirmation were all that remained before the purchase at 60 Broadway closed.
  367. 104 PagesTwo bank transfers turned into a 104-page mortgage document package while the purchase at 60 Broadway was still waiting on underwriting.
  368. Christmas Week Security CallDuring a possible Shutterstock account-security incident, I tried to get the technical investigation and customer communication moving at the same time.
  369. Forty-Five DaysThe mortgage deadline arrived during Christmas week, the banker was away, and the 60 Broadway deal could still fall apart.
  370. Qualified. Bad Timing.Nation's Triathlon put me into the national championships. The race landed two weeks after my Ironman.
  371. Coughing After PhillyA bad chest cold took out the last training days. I still ran 1:26, then went looking for pancakes.
  372. In ContractAfter weeks of open houses and paperwork, the loft at 60 Broadway was officially becoming mine.
  373. One Point One Miles UpStorm King was seven and a half miles, one long hill, eighth overall, and exactly the kind of hard race I liked.
  374. Too Many Open HousesThe apartment search moved from one possible DUMBO offer to a Saturday route through several Brooklyn buildings.
  375. Do Not Contact My EmployerGoogle invited me to spend a day interviewing in New York. Shutterstock was not supposed to know.
  376. Buy the Fischer GroupI announced a thirty-six-month acquisition plan with no supporting details and one smiling emoji.
  377. Sea to SeaEight days across the Pyrenees changed what I thought a bike trip and my own legs could handle.
  378. Eva Goes to DCThe race trip had one harder logistics problem than the bike: getting Eva there and home without making Sunday worse.
  379. Two Pilsners. One PR.A North Brooklyn Runners team night produced my fastest 10K in twelve years and a questionable pre-race nutrition theory.
  380. Forgot My ShoesWest Point was a two-minute PR with a better swim, a stiff back, tired legs, and bike shoes left in transition.
  381. Let's Dream a LittleThe next twelve months included faster road races, a long swim, another Ironman, and a bike trip across the Pyrenees.
  382. There's Legs HereA friend had a working prototype for cloud development environments. I wanted to help figure out whether it could become a company.
  383. Storage Was Everybody's ProblemThe storage problem was too important to keep inside one operations circle, so I started identifying product owners and engineers to involve early.
  384. The Very Good News GraphCompleting the private MPLS ring moved data-center traffic behind the firewalls and changed the long-term capital curve.
  385. The Queues Hit ZeroA storage push reached 4.8 gigabits on the trackers, cleared the queues, and gave us room to retire devices more aggressively.
  386. $36 a MonthA first pass at Shutterstock's private-cloud economics put a large virtual machine at $36 per month against $260 in AWS.
  387. West Coast, One PanelA quick West Coast trip for an industry panel became another chance to connect the systems work at Shutterstock with the broader startup network.
  388. Everybody Was Getting DDoSedA roomful of infrastructure leaders confirmed that large denial-of-service attacks had become an industry problem, not a Shutterstock anomaly.
  389. Heartbleed, Then Everything ElseWe patched Shutterstock quickly, rotated security keys, and worked to tell customers what happened without implying a breach we had not found.
  390. London Forgot to Tell UsAn office move in London reached the technology team after planning was already underway, which made a small email into a process correction.
  391. Managers Need Training TooAs the organization added more leaders, a shared management workshop offered a way to build continuity instead of leaving everyone to improvise.
  392. Build the FortressA sustained DDoS attack forced us to abandon the original tunnel design and build private paths into our mitigation provider.
  393. The Empire State Went DarkA Sunday power issue sent us back into the new office to verify network rooms, battery systems, and supplemental cooling.
  394. Break It on PurposeA failed firewall had left the production pair out of sync, so the safer choice was a controlled maintenance window instead of waiting for another failure.
  395. The Pool Part Was NextI completed the six online sections of the PADI Open Water course, with the real pool and open-water work still ahead.
  396. $2 Million Before MidnightThe last day of 2013 ended with major infrastructure orders, spare transceivers, and the practical consequences of a year-end deadline.
  397. $4.6M Became $2.4MA year-end network purchase moved from a $4.6 million list price to $2.4 million after discounts and negotiation.
  398. Move First, Network LaterThe Empire State Building office could open, but bandwidth would arrive in stages and the final design was still months away.
  399. Dinner With the Infrastructure PeopleA post-Thanksgiving invitation from General Catalyst was a reminder that the infrastructure community was becoming part of my work too.
  400. Everyone Ships CodeAt the 2013 OpenStack Summit, I explained how Shutterstock provisioned virtual machines and physical servers through one automated system.
  401. Storage Got FastA sharp improvement in storage latency came from spreading writes across nodes and throttling network traffic in the kernel.
  402. Zero Under-Replicated BlocksFour new Hadoop data nodes pushed an important storage health metric all the way down to zero.
  403. 800,000 a SecondDatadog was interesting, but Shutterstock's monitoring volume meant the useful experiment was smaller and more specific than sending everything offsite.
  404. Two More ThingsA work-from-home Friday still had two storage jobs on the list: enable a read slave and verify the correct load balancer.
  405. Double ItA one-line Friday instruction captures the long, unglamorous work of moving a very large storage system.
  406. Can We Publish This?A request to publish Shutterstock architecture diagrams became a small lesson in supporting engineers who wanted to teach in public.
  407. Same Tools, Different SizeDev, QA, and production did not need identical scale, but they did need the same tools, deployment path, operating system, and testing discipline.
  408. Hack to the FutureOur Shutterstock hackathon project did not win, but the demo landed and the idea was good enough to keep building.
  409. Please Give Us IPv4A late-June ARIN update records the administrative work behind obtaining public internet address space for Shutterstock.
  410. We Needed More HumansA June recruiting email described Shutterstock's WebOps team as it looked for operations engineers for the company's next phase of growth.
  411. Make the Outage PublicA simple public Shutterstock status page pulled product, social, and infrastructure into the same work.
  412. Search Had One GuyA departing specialist created a knowledge gap around Shutterstock's search infrastructure and started a discussion about coverage and hiring.
  413. Thirteen Minutes DownA missing configuration in a new deployment system took a Shutterstock service offline for thirteen minutes.
  414. Ten Minutes. Go.The first opportunity assessments for Shutterstock's technology syndicate were ready for a ten-minute leadership review.
  415. 110 Days to GoA storage rebalance was about ten percent complete after twelve days, with an estimated 110 days still to run.
  416. Who Owns This?A March thread asked whether Shutterstock had formal technical owners and started a written process for defining the role.
  417. All Moved InA four-line email from March 2013 records a fast move into a new place and the end of a longer apartment search.
  418. Offsite: Uptime FirstThe agenda for a March technology leadership offsite started with service uptime, programming languages, syndicates, and more consistent environments.
  419. AWS Was Still ThereAn internal question in February 2013 asked when Shutterstock's development and QA environments would move from AWS back to the office.
  420. Put It on the WallShutterstock restored office monitors showing overall system health, automated tests, and search speed where the teams could see them.
  421. More RAM. Again.A January hardware plan counted the memory modules needed for Shutterstock's search and database servers.
  422. The Circuit Waited for MeA short Monday email asked me to help the Shutterstock team work through a weekend network circuit outage.
  423. Humans Worked. Alert Failed.The Shutterstock mobile site worked when we tested it by hand, but one automated check still failed and needed an owner.
  424. Bacon of the MonthNorm's Christmas present arrived as an all-caps email and a promise of recurring bacon.
  425. Apparently I Wanted EverythingA few weeks after Shutterstock went public, I planned a marathon, two half Ironmans, Leadville, a long swim, and several time goals for 2013.
  426. Jellyfish and a DecadeThe Cozumel swim had current, jellyfish, and plenty of people who did not finish. I stayed calm and completed the goal.
  427. Wear Flexible ClothingAmanda and I hosted Thanksgiving in Williamsburg with a turkey, pumpkin pies, bikes, board games, and optional head-dresses.
  428. Define DevOpsA friend needed a DevOps hire. Before naming anybody, I needed to know what he meant.
  429. Yes, I Would Like to ParticipateSecond in my age group at Westchester came with a slot for Escape from Alcatraz. The answer was immediate.
  430. Book the RoomIronman Cozumel was six weeks away. Amanda and I still needed somewhere to sleep after it.
  431. Provided the Price SticksShutterstock went public. A friend asked if I was a millionaire. My answer was not quite.
  432. Painless. A Little Clumsy.The first run after a hard race did not hurt. That was enough good news to keep the week moving.
  433. Spend $350 to SwimI found a weekend freestyle clinic in New Paltz and invited a friend with a very honest sales pitch.
  434. I AcceptNorth Brooklyn Runners had no dues, a long code of ethics, and coffee after the Williamsburg Bridge run.
  435. Here's the DealioThe Ironman plan was a beach, a Sunday race, a ferry, and the hardest physical thing I had ever tried.
  436. There's a Startup in ThereOptopus was a little piece of software with enough of an idea inside it to justify lunch.
  437. Calling From a Wine CellarA monitoring demo followed me from San Francisco to the mountains to Napa, where the only honest location update was the wine cellar.
  438. One Second Broke EverythingA leap second hit the servers while family was visiting, and the phone would not stop being part of the room.
  439. Broke a PedalSeven miles into a triathlon, the pedal broke. The transitions were bad too. I finished anyway.
  440. Bring Him InA technical recruiting conversation moved from an introduction to a phone call to one short decision.
  441. Joined the GymRetro Fitness followed up about a free day pass. The answer was shorter: I had already joined.
  442. We FiledShutterstock's S-1 became public, and I sent the link to my family with a late Mother's Day call.
  443. Quiet Rack, PleaseThe new office equipment had two requirements: keep it enclosed and do not make the room sound like a data center.
  444. No OutageA week after postponing the work, Shutterstock moved its main databases to Boston without taking the site down.
  445. Still HereThe whole operations team was still provisioning a new data center, so the next database cutover could wait.
  446. Boston Takes the TrafficThe web servers had moved. Next came the part customers could actually hit: production traffic.
  447. I Signed You UpLeadville was high, hard, and apparently something I had decided somebody else should do with me.
  448. Make It FasterA new Akamai product might speed up more than static images. First, it had to work on the real site.
  449. Moderately CrazyShutterstock had grown. The office network had grown with it, just without much of a plan.
  450. Make Local WorkThe infrastructure goal was basic: every developer should have a standard environment that worked on a laptop.
  451. Put Some Weight on ItFour guys, two teams, one spreadsheet, and a lifting bet to keep the 5/3/1 cycle honest.
  452. Someone Should Build ThisA side-project idea started with a simple gap: site-speed tools were expensive, slow, and built for big companies.
  453. Slept on the FloorThe Williamsburg loft had boxes, a real kitchen, a king bed on the way, and one very happy new tenant.
  454. Before Monday Showed UpWe put real load through a new Shutterstock network layout over the weekend and found a bottleneck before Monday traffic arrived.
  455. Tech Happy HourEvery other week, the technical team stopped working long enough to eat and drink together.
  456. Williamsburg, PleaseThe apartment search narrowed to a small loft with high ceilings, big windows, and a January move.
  457. Yep, Sounds GoodA Mudder spot opened, the payment could transfer, and my entire decision took three words.
  458. Best Man, Partly Remote?I asked to work part of my brother's wedding week remotely and take the wedding days off.
  459. One Petabyte. Three Sites.An October announcement draft documented more than one petabyte of Shutterstock storage across three sites.
  460. The Graph DroppedA speed release aimed at distant users landed, and the first measurements moved in the right direction.
  461. Two More CabinetsI asked our provider for one or two short-term data-center cabinets, preferably month to month.
  462. How Long on Diesel?Hurricane Irene produced one blunt question about backup power and time.
  463. Contributors Couldn't UploadAn upload-server issue blocked part of the contributor base while the team restored storage and explored a reroute.
  464. Four Rooms, One HangoutDevelopers and WebOps troubleshot one issue from two Manhattan floors, Denver, and my apartment.
  465. OutstandingMy performance review came back marked outstanding, with a raise behind it.
  466. Get AggressiveI wanted to move the MogileFS conversation from research toward the real Shutterstock and Bigstock libraries.
  467. Three to Six-ThirtyThe site stayed up through an overnight database and search problem whose cause was still unclear.
  468. Typos Were InfrastructureThe DNS migration started with a long inventory of domains, brand variations, and names collected over time.
  469. Four Pieces, One LoftThe Lower East Side apartment needed a couch, a TV stand, and exactly two dressers.
  470. Put a Pool in the RiverA floating, water-filtering public pool in New York sounded just unreasonable enough to back.
  471. Everything Was My JobMy responsibility list kept growing until the breadth of the role became the problem.
  472. Tier I, PleaseThe 2011 email said “Tier1,” but the real idea was to use the facility as a foundation for infrastructure we designed ourselves.
  473. Eight to Ten SecondsThe maintenance plan accepted one small site blip to reduce a much larger power risk.
  474. Data Server IssuesIssues around the data servers had contributed to a recent outage, so I asked for a conversation that day.
  475. Replication LagReplication lag had shown up again, and I wanted systems and development looking at it together.
  476. Recruiters Tried to Hire MeAn outside recruiter rewrote our job post and pitched me the role I was trying to fill.
  477. Kill Spanning TreeThree of us went to the data center to replace the old switches and simplify the network.
  478. Still a Little SpikyA smaller log sample made the error graph easier to read, but the monitoring experiment still needed a second opinion.
  479. The Firewall Didn'tA failover failed, the console path worked, and my laptop was sitting at happy hour.
  480. Fun ShizMogileFS, Xen, deployment graphs, and a weekend in the office sounded like a good time.
  481. By HandAn email with no body, a server-room rack, and a lot of carefully routed white cable.
  482. Call Me When It Goes DownTwo months into Shutterstock, I asked the systems team to call me for every critical alert while I learned the environment.
  483. Seven Months of StartupsIn a fast stretch, I moved from Peek to a hosting company, then joined Shutterstock and kept Ops Dojo going on the side.
  484. One Terabyte, Three CopiesI changed the copy path for more than a terabyte of data to reduce load on the production systems.
  485. I Love BIND FilesI set up PowerDNS with a MySQL backend because database records were easier to automate than hand-edited BIND files.
  486. Four Days BehindI answered a Volkswagen-van naming thread four days late and suggested Axl.
  487. Ops Dojo, DelawareBy the end of October, Ops Dojo was a Delaware S corporation with equal founders and an unsettled software plan.
  488. Goodbye by EmailMy last day at Reality Check passed inside a chaotic weekend, so the proper goodbye came later.
  489. The Withdrawal RequestA death in the family left me behind in two courses, so I asked Baker College to withdraw me from them.
  490. I Officially AcceptedThe second conversation with Shutterstock ended with a Director of Systems Operations job.
  491. Miserable WeekA new Amsterdam data center, school, and a side company all landed in the same seven days.
  492. As If I Didn't Have EnoughThe president of my current company resigned and stayed on the board. My private reaction was immediate and unpolished.
  493. Monk Got a LogoMonk Networks was still a rough business plan, but now it had a very orange face.
  494. One More ShotSeven months after turning down one Shutterstock job, I asked the company to take another look at me.
  495. Outsource the Whole ThingThe early Monk Networks pitch was simple: give a startup an operations department without making it build one.
  496. Done and DoneTwo hours after an advisor asked for a one-page business summary, the first Monk Networks pitch was moving.
  497. Three Weeks, No CardBaker said the school debit card was coming. Classes were getting close, and it still had not arrived.
  498. New BeginningsI asked an old Beatport executive to help build a managed-infrastructure company on the side.
  499. 60K in a FieldTwo nights after watching the Netherlands reach the World Cup final in Amsterdam, I sent one good photo from the trip.
  500. CTO, Written DownReality Check put my CTO responsibilities into a simple roles document, and I immediately used it to help somebody else.
  501. Few Months LateSpring cleaning reached the New York apartment in June, complete with new shelves, a whiteboard wall, and a lot of shoes.
  502. Tunnels Show Up AgainThe old Peek mobile-network integration came back to life after months of routing questions and another round of troubleshooting.
  503. SuzieQ Had EmailA small fashion business needed Google Apps, two working inboxes, and somebody to explain how to get into them.
  504. Can Work Count as Credits?I went back to Baker College and asked whether years as an IT director and CTO could help finish the degree I had left open.
  505. One of You Needs to Take ItI made the same Reality Check offer to two former Beatport teammates and tried to get one to bring the other.
  506. Please Take This JobReality Check needed an infrastructure engineer. I wanted somebody I trusted and was already tired of interviewing.
  507. We Built an Air CompressorAn old family photo showed my brother and me grinning behind industrial machinery in the machine shop where I once lived.
  508. Sick of Gluster ConfigsThe storage proof of concept worked. I wanted four nodes, real performance data, and then a break from staring at it.
  509. Two Days, Cool GraphsReality Check tried two-week sprints, small tasks, daily updates, and a chart that became interesting almost immediately.
  510. Sure, Just Call MeI had left Peek for a new CTO job. The old team still needed help with the network, and I still answered.
  511. Passion Now. Safe Later.Facebook, Shutterstock, and Reality Check offered three different futures. I chose the fifteen-person hosting company.
  512. The Rows Didn't MatchA database import kept producing the wrong row count during a week that also included illness and a London data-center trip.
  513. The Data Center Needed a CarA consulting job in Somerset required a rental car because I could not find a practical transit route from Manhattan.
  514. Holy Shit, FacebookA Facebook recruiter found my profile while I was already holding down multiple startup jobs in New York.
  515. Tmptrash FirstThe GetGlue logs needed to leave the servers without disappearing before I knew the S3 copy was good.
  516. Only Young OnceI had a third job offer, a three-person startup that needed to scale, and a very loose theory about burnout.
  517. References ClearedAdaptiveBlue offered me a consulting systems job, my old Beatport references checked out, and I had no scanner.
  518. Let's Make It HappenThe music-store side project had a team, a rough market, and enough of my schedule cleared to begin after New Year's.
  519. Sorry for the Email LookupCraigslist replies had failed me before, so I found the founder's address and made sure my half-time Linux application reached a person.
  520. How Many Tracks?After Beatport I helped think through storage, catalog size, interfaces, and customers for a new high-quality music store idea.
  521. HollaA Peek SMS gateway test began with one word, then moved through two phone numbers and one less interesting message.
  522. The Marked-Up PlanA clothing-line business plan came home for comments, and I carried the paper copy around until we could go through it together.
  523. Where All Trac Updates GoThe first TechOps list test bounced. Two minutes later, I tried again with a destination for every Peek infrastructure ticket.
  524. Baker What?Finishing my degree came down to an expensive New York classroom or a little-known online college built around six-week terms.
  525. The Rad PillowAfter the U-Haul, the filthy apartment, and a couch that barely fit, one homemade pillow made the place look like ours.
  526. Sent from My PeekA five-word Peek-device email asked whether the previous test had arrived and how work was going.
  527. Add One SpaceAfter leaving Yodle, I kept helping with its Zenoss monitoring and proposed one space to stop a loose process match.
  528. Off EC2 in Twelve MonthsPeek had more than fifty compute nodes in Amazon, and I was already pricing the first half cabinet for our own equipment.
  529. Official. Again.A few weeks after joining Yodle, I gave notice and took the Director of Technical Operations job at Peek.
  530. Almost to IndianaWe were driving our belongings east while Peek was already asking me to price a data center and route traffic back to Amazon.
  531. Nobody Answered at 3 A.M.A Peek email outage lasted four hours because the POP nodes failed overnight and nobody answered the monitoring call.
  532. Permanently, Last WeekI had finally moved to New York, changed my phone number, and still answered the recruiter calling about another infrastructure job.
  533. Last Tickets to DenverThe final Denver flights and a one-way U-Haul turned the New York move into something we could no longer treat as a plan.
  534. Signed. Then Resign.I returned Yodle's signed offer and NDA, then wrote the letter ending three years at Beatport.
  535. The U-Haul Was $1,100Yodle wanted references, which made the job feel real enough to price a moving truck and a trailer for the Jeep.
  536. 1.8 Miles AwayBefore the Yodle interview, I mapped the walk from the East Village apartment to its Flatiron office.
  537. What Kind of Interview?Ten days after applying to Yodle, I got the phone screen and asked exactly what kind of conversation to expect.
  538. Eight Hundred Ninety-Two PercentI applied to Yodle by comparing its rapid growth with the systems I had already scaled at Beatport.
  539. BGP EstablishedA new autonomous-system number, two network providers, and one multihop setting finally brought the session up.
  540. Twenty-Four Months DustyA technical phone screen exposed the difference between doing systems work and reciting it from memory.
  541. The 12:55 A.M. FlightOne overnight flight could get me from Denver to a New Jersey startup interview, if I could find the money and stay awake.
  542. Two Canceled FlightsNew York interviews went well, but two canceled flights kept me there while Denver consulting work waited.
  543. The 1977 CJ5I proposed taking Greyhound to inspect a yellow 1977 Jeep in Grand Junction, and two days later I owned it.
  544. Third Time, Same Unix JobThe Unix administrator job kept appearing on Craigslist, so I sent a third application and explained why I still wanted hands-on work.
  545. Scrub the Network DiagramI offered a security-scrubbed Beatport network diagram as a work sample, but asked before sending it.
  546. Rootkit Checks for EverybodyOne compromised consulting server was taken offline for reprovisioning, and I planned rootkit checks across the remaining systems.
  547. My Third JobBeatport, two consulting jobs, and a phone photo sent with one blunt explanation: I wanted a loft.
  548. Delete the Stale LockA noisy MRTG process looked mysterious until the problem came down to one stale lock file.
  549. One Service at a TimeAn after-hours firewall and Linux Virtual Server rebuild needed a simple plan and very short outages.
  550. Twenty Hours, Still GoingA major Beatport deployment had run for twenty hours, and I was still trying to make the meeting for another side job.
  551. More Than 300 DevicesBeatport's always-on infrastructure had grown beyond 300 devices, with a seven-person systems and network team responsible for it.
  552. February TenthA small Denver studio was approved far enough for a lease, and I accepted a proposed February 10 move-in date.
  553. I Needed a Night ShiftI was Beatport's IT director and applying for night and weekend data-center work because my family needed more money.
  554. The Server Racks WonI studied molecular biology but spent most of my time learning Linux, Unix, storage, and distributed systems on hardware in my basement.
  555. Five VMs. One Desktop.I rebuilt a client's Linux load-balancing setup in virtual machines and tested production-style routing and failover from my desk.
  556. Steve and Barry Needed RAIDTwo client servers with ordinary names needed software RAID, LDAP work, package cleanup, and a lot of careful retracing.
  557. PTR Records. ASAP.A reverse-DNS failure stopped a consulting client's production mail and turned a long domain list into an urgent provider ticket.
  558. Fifteen Hours Every Two WeeksMy first consulting invoice came with a request for more hours and a growing list of firewall, colocation, monitoring, and load-balancing work.
  559. The NDA Was SignedOne month after I started looking for extra Linux work, I signed the paperwork for a real consulting client.
  560. New York, SomehowI was running Beatport's systems in Denver and still tried to turn a New York Unix job into part-time remote work.
  561. A Second Shift From HomeI was Beatport's IT director and answered a Craigslist Linux job with an offer to work remotely at night and on weekends.
  562. The License Did Not HoldA German court restricted Beatport's new European licensing arrangement only weeks after it was announced.
  563. Welcome to PhotobucketA Photobucket welcome email confirmed that I had opened an account, but it did not include a first upload.
  564. One License. Twenty-Seven Countries.Beatport and Buma/Stemra announced a pan-European music license intended to cover the full European Union.
  565. Ski Season in JulyVail Resorts asked about my ski-vacation preferences in the middle of a Denver summer, two months after pitching the new Epic Pass.
  566. Nike+ at the GymA 24 Hour Fitness email passed along a Finish Line offer for the Nike+iPod running kit.
  567. Thirty-Five Dollar FireworksFriends planned a Colorado Rockies game for July 4 with upper-deck seats and the fireworks show included.
  568. Royal Gorge, MaybeA June group email tried to organize a camping and whitewater rafting weekend at Colorado's Royal Gorge.
  569. The Beach at A-BasinMemorial Day plans called for a 12-person tent, soft snow, a grill, beer, and one more day of skiing at Arapahoe Basin.
  570. apt-get WifeA Digg URL ending in APT_GET_WIFE arrived with one sentence and an antivirus footer.
  571. Zero PEAKS PointsMy ski account ended the 2007–08 Colorado season with no reward points and a $579 Epic Pass offer.
  572. Tee Times Went MobileGolfHub's 2008 mobile launch put Colorado tee-time searches in the same inbox as my Linux servers and Beatport work.
  573. Deadmau5 Won Most of ItThe first Beatport Music Awards turned a year of store sales and six weeks of public voting into 19 winners.
  574. Saturday in BoulderA Thursday group email proposed a Saturday night party in Boulder and asked everyone to pass the invitation along.
  575. Open Source EverythingA friend sent a security link with the subject line, Why All security should be open source.
  576. The Signature Was LongerMy Beatport email signature had grown into five products, two phone numbers, a trademark, and almost no actual message.
  577. Nineteen Ways to WinBeatport opened voting for its first Music Awards, using 2007 store sales to build the nominee list across electronic music.
  578. Linux Admin, AgainA recruiter sent a six-month Linux systems contract while I was already leading infrastructure at Beatport.
  579. A Few HoursMy new reseller hosting account took days to appear while I had web-hosting clients waiting for it.
  580. Still No Welcome LetterI ordered a VPS, confirmed it by phone, and then waited for login details that had not arrived.
  581. Only the Front Is WidebodyI tried to trade the RS4 front end off my Audi S4 and get the car back to stock without shipping body panels across the country.
  582. Do I Need to Reformat?A friend's Linux storage question landed in my Gmail chat while I was running infrastructure for Beatport in Denver.
  583. Hiring Outlook: 2008The new year opened with automated IT job alerts while I was already running infrastructure at Beatport.
  584. Welcome to YouTubeA YouTube welcome message asked me to confirm my email before uploading videos or posting comments.
  585. The Phone Bill Kept ComingThe same Beatport wireless bill notice reached my personal Gmail at the end of five straight months.
  586. Spiced Lamb ShankAn accepted ESPN trade kept our badly named fantasy football league moving in November.
  587. The Apartment Called About the DogA Cherry Creek property manager asked me to call immediately about my dog.
  588. Data Center Specialist, AgainThe same recruiter sent the same data center specialist request on two consecutive days.
  589. The Job Alerts Wouldn't DieDice, Monster, and recruiters kept matching an old online resume while I was already running technology at Beatport.
  590. Customer CornerViaWest featured Beatport beside Mozy in its customer newsletter while I managed Beatport's hosted infrastructure there.
  591. Refund NeededI paid for an online NFL channel, found it offline, and asked for my money back.
  592. 7:45 Eastern. 5:45 Denver.An ESPN time-zone setting moved our fantasy football draft and started another round of corrections.
  593. Beatport Added BeatportalBy late August, Beatportal was live with news, reviews, podcasts, events, streams, and community submissions around Beatport's music store.
  594. Extra Work After WorkI introduced myself as Beatport's IT director and asked about additional systems administration work.
  595. Beatport, TwiceA wireless bill notice reached my personal Gmail with the greeting BEATPORT BEATPORT.
  596. The $29,500 AudiI listed a modified black 2001.5 Audi S4 with a manual transmission for $29,500 on Craigslist.
  597. The Resume Kept WorkingRecruiter messages kept finding an online resume after I used Beatport's infrastructure numbers in job applications.
  598. Nine Web ServersA job application listed the web servers, databases, storage, traffic, and uptime I managed at Beatport.
  599. Renewed. Still Not Launched.An automatic domain renewal kept a name registered for another year without proving a project had launched.
  600. The Domain Renewal PileA fifteen-day registrar notice put another group of old domain names back on the decision list.
  601. Playing Catch-upFour Facebook photo-tag notices arrived from an album called Playing Catch-up.
  602. MP3s to My InboxFour Motomail messages tested a simple path for sending MP3 download links through email.
  603. Print Four and FiveA friend sent one instruction before the Nuggets played the Lakers: print tickets four and five.
  604. Recommended Track, Working EmailA test of Beatport's release-recommendation email used placeholder text and a real Strictly Rhythm track.
  605. Two Welcome EmailsTwo 24 Hour Fitness welcome messages marked the start of a new gym membership.
  606. New Title. Same Tests.My Beatport signature now said Director of Information Technology, but I was still sending messages through the system by hand.
  607. The Dog Was StayingAfter weeks of considering a new home for my Weimaraner, I decided to keep working through the difficulty.
  608. The Client Came BackEven after Praxis ended, a former client still needed help finding and preserving old webmail files.
  609. Director at Twenty-TwoMy Beatport title changed from Network Administrator to Director of Information Technology when I was twenty-two.
  610. One Click from LiveA classified post about finding a new home for my young Weimaraner was drafted but still waiting for confirmation.
  611. Praxis Kept GoingPraxis was entering its fifth year of systems and network consulting beside my full-time work.
  612. The Test Wouldn't DieBeatport's mail tests continued into December, alongside lingering consulting work and a company that never really closed.
  613. I Was Literally in the OfficeThe funniest line in a month of mail tests was an out-of-office reply explaining that I was actually sitting at work.
  614. Network AdministratorA Thanksgiving email preserved my first Beatport title and the ordinary mail system surrounding a global store.
  615. I Wasn't Actually AwayAn outside Gmail message triggered a test response from Beatport's vacation responder.
  616. Mail Logs ForeverBeatport's early email setup required a week of tests across queues, lists, outside addresses, and vacation replies.
  617. The Org Chart AttachmentTwo weeks into Beatport, a Visio org chart arrived beside the account and mail-path tests already filling my new inbox.
  618. Beatport OfferA September interview at a small Denver online music store turned into a written systems-administration offer six days later.
  619. Real Estate, Then ServersOne September day mixed an OptiTrex real-estate side project with a request to discuss another systems job.
  620. Linux on His PhoneA friend sent me a link to a Linux port for his Windows Pocket PC phone.
  621. Dogs Allowed or No DealSearching for an August weekend in Estes Park came down to one requirement: the puppy had to be allowed.
  622. New Account. Same Tests.A new work account went through the familiar ritual of sending mail back and forth until both directions worked.
  623. Answer by MondayA Friday company visit turned into a written systems-job offer with a Monday deadline.
  624. Five Hours Was OptimisticI finished the 2006 Leadville Trail Marathon in 5:37:50, 74th out of 238 finishers.
  625. Ride to Work. Run Leadville?I was biking to work, training for a difficult marathon, and considering the Leadville Trail 100 run.
  626. The Resume, TwiceI applied through Dice, then sent the network-administrator resume directly because I did not trust the automated system to deliver it.
  627. I Bought My NameA June 2006 registrar notice confirms that I had registered chrisfischer.info and changed the domain to locked status.
  628. Someone Forgot the DomainA BMX forum disappeared behind an advertising page when its domain expired, then returned after the operator renewed it.
  629. Chicago for a WeddingThe itinerary and my photos line up: I flew from Denver to Chicago for a wedding weekend in May 2006.
  630. Patch It or ElseMy hosting provider planned to upgrade every managed phpBB forum to version 2.0.20 after new security vulnerabilities were found.
  631. Denver Was HiringA Dice employment report arrived while I was applying for network, Linux, Unix, and systems roles around Denver.
  632. Chicago Was on the CalendarI booked a May trip from Denver to Chicago and filed the confirmation with the rest of the travel mail in my new Gmail account.
  633. $8 Million LaterWestar Aerospace acquired SimAuthor for $8 million while I was responsible for its network, systems, security, and in-house data center.
  634. The Data Center Came HomeI rebuilt SimAuthor's network and moved the aviation software company's data center back inside its sixty-person office.
  635. Linux Jobs. All of Them.One Monday produced a pile of resumes for Linux support, network administration, and consulting work.
  636. The Website Wasn't DoneA friend asked me to review a dispute over an unfinished website, a forum, contact forms, a logo, and a missed deadline.
  637. Still Testing EmailRepeated test messages between my personal Gmail and SimAuthor account show a month of checking the mail path in both directions.
  638. The S4 InterrogationBefore buying a used 2001 Audi S4, I sent the owner a detailed list about modifications, maintenance, mileage, and how it had been driven.
  639. Back to CU?While working at SimAuthor, I sent my resume to former CU colleagues and asked them to keep me in mind for administrator roles.
  640. Two Xeons, PleaseA used pair of 3.06 GHz Intel Xeon processors was part of how I kept building and learning on my own hardware.
  641. Free VPN. Merry Christmas.A former CU colleague sent me OpenVPN, security, and network-tool links while I was working across SimAuthor and Praxis.
  642. Italy Blocked EverythingA network in Italy allowed web traffic but blocked the VPN, SSH, remote desktop, and dial-out access I needed for work.
  643. Who Wants a Gmail Invite?Gmail still required invitations, so I used one of mine to bring a friend and Praxis collaborator over.
  644. Test. Test. SimAuthor.A short run of test messages in November 2005 shows me checking delivery between Gmail and SimAuthor accounts.
  645. The Raptors Were DeadTwo Western Digital Raptor drives from an eBay purchase had failed, so I asked the seller to take them back and issue a refund.
  646. Gmail, Denver, DoneA new Gmail account handled a Denver flight, a friend's invitation, and the same mail tests I was still running against SimAuthor.