kennethreitz-org-ywzt9y.txt (18810B)
1 [1] View on GitHub ☀️ 🌙 [3]Home [4]Archive [5]Search 2 Themes 3 [svg][6]The Algorithm Eats 4 [svg][7]Artificial Intelligence 5 [svg][8]Consciousness & AI 6 [svg][9]Evolution of Ideas 7 [svg][10]The "For Humans" Philosophy 8 [svg][11]Mental Health 9 [svg][12]Open Source & Community 10 [svg][13]Pattern Recognition & Manipulation 11 [svg][14]Psychology & Consciousness 12 [svg][15]Spiritual Practice & Technology 13 [16]All Themes → 14 etc. 15 [svg][17]artificial-intelligence 16 [svg][18]essays 17 [svg][19]music 18 [svg][20]photography 19 [svg][21]poetry 20 [svg][22]software 21 [svg][23]talks 22 [svg][24]themes 23 [svg][25]colophon 24 [svg][26]contact 25 [svg][27]family 26 [svg][28]great-books 27 [svg][29]great-music 28 [svg][30]mental-health 29 [svg][31]plurality 30 [svg][32]timeline 31 [svg][33]values 32 [svg][34]worldview 33 [svg][35]yoga-meditation 34 [36]~ / [37]Essays 35 Icon for Open Source Gave Me Everything Until I Had Nothing Left to Give 36 37 Open Source Gave Me Everything Until I Had Nothing Left to Give 38 39 March 2026 11 min read 40 4 themes 41 [39]Lived Experience [40]For Humans [41]Open Source [42]Burnout 42 [43]PDF [44]Markdown 43 44 I thought I was having a spiritual awakening. I was having a psychiatric 45 emergency. 46 47 I was at a tech conference in Sweden when it started. I hadn't slept in days. I 48 was one of the most prolific open source developers in the Python ecosystem, 49 maintaining the most downloaded HTTP library on Earth, keynoting conferences 50 across the world, and I was losing my mind in a hotel room six thousand miles 51 from home. 52 53 Nobody around me knew. The mania looked like productivity. It always does. 54 55 This is the story I've been avoiding writing for a decade. Not the origin story 56 of [45]Requests, the library I built that changed my life. I've told that one 57 plenty of times. This is the story of what it cost. 58 59 What Open Source Gave 60 61 Open source didn't just give me a career. It gave me an identity when I had 62 none. 63 64 I was a college dropout who had been [46]working the front line at McDonald's 65 the year before. The education system had written me off. My GPA was 1.14. The 66 standard paths to professional legitimacy were closed, and I had no plan for 67 opening new ones. I was bidding on freelance jobs for pocket change and hoping 68 something would happen. 69 70 Open source was the thing that happened. 71 72 When Requests took off, it wasn't just a popular library. It was proof that I 73 existed, that I was capable, that the thing I could do had value in the world. 74 The download counts were a scoreboard, and I was winning at the only game that 75 had ever let me play. Every star on GitHub was a person saying: you matter, 76 what you built matters, we see you. 77 78 For a kid who had never been seen by any system that was supposed to see him, 79 that was everything. I don't use the word lightly. It was everything.[47][ ] 80 Identity formation through open source contribution is more common than people 81 realize. For those of us who didn't fit the credentialed paths, community 82 recognition became the primary mirror in which we learned to see ourselves as 83 capable. This is a gift. It becomes a trap only when the mirror is the only one 84 you have. 85 86 Open source gave me Heroku. Heroku gave me a salary, health insurance, 87 colleagues who took me seriously, and a front-row seat to the infrastructure of 88 the internet. It gave me a platform to advocate for the [48]"for humans" 89 philosophy that I still believe is one of the most important ideas in software 90 design. 91 92 It gave me a life. A real one, built from nothing, through craft and generosity 93 and a community that rewarded good work regardless of where you went to school. 94 95 What follows is not ingratitude. It's accounting. 96 97 The Escalation 98 99 Here's how it worked, practically. You build something good. People use it. 100 People depend on it. People file issues, request features, report bugs. The 101 community grows. The responsibility grows. The expectations grow. And because 102 the thing that gave you your identity is the thing people are depending on, you 103 can't separate "maintaining the project" from "maintaining yourself." 104 105 I didn't have boundaries around this because I didn't know I needed them. The 106 kid who had been invisible was now visible, and visibility felt like oxygen. 107 More users meant more validation. More conferences meant more proof that I 108 mattered. More projects meant more surface area for the world to see me. I said 109 yes to everything because saying no felt like closing the door that had saved 110 my life. 111 112 from dataclasses import dataclass 113 114 115 @dataclass 116 class MaintainerLoop: 117 """The cycle that builds careers and breaks people.""" 118 119 identity: str 120 project_success: float = 0.0 121 community_expectations: float = 0.0 122 self_worth: float = 0.0 123 124 def cycle(self): 125 # Success raises expectations. 126 self.community_expectations = self.project_success * 1.5 127 128 # Self-worth tracks community response. 129 self.self_worth = self.project_success 130 131 # When identity IS the project, 132 # every expectation becomes personal. 133 # Every criticism lands on the self, 134 # not just the code. 135 136 # There's no circuit breaker here. 137 # That's the design flaw. 138 pass 139 140 Copy 141 142 The pressure was largely self-directed. I want to be honest about that. Nobody 143 at Heroku was cracking a whip over my open source work. The community wasn't 144 threatening me. The pressure came from the fact that I had welded my sense of 145 self to the project's success, and anything that threatened the project 146 threatened me. A rude issue comment wasn't just feedback about code. It was 147 someone questioning whether I deserved to exist in the space I'd carved out. 148 149 And underneath all of this, undiagnosed, was bipolar disorder. 150 151 The Crises 152 153 I need to talk about this directly, because the connection between open source 154 and my mental health crises is the thing I've been avoiding writing about for a 155 decade. 156 157 I've [50]written about the clinical details elsewhere. What I haven't written 158 about is the fuel. The manic episodes didn't come from nowhere. They came from 159 a young person with an undiagnosed mood disorder who was running at maximum 160 intensity, sleeping four hours a night, crossing time zones every other week, 161 saying yes to every opportunity, and performing the role of "prolific open 162 source developer" at a pace that would have been unsustainable for anyone and 163 was genuinely dangerous for someone with my brain chemistry.[51][ ]The 164 relationship between external stressors and manic episodes is well-documented 165 in bipolar disorder research. Stress doesn't cause bipolar disorder, but it can 166 trigger episodes in people who have it. Sleep disruption is particularly 167 dangerous, and the open source maintainer lifestyle (conferences across time 168 zones, late-night coding sessions, the always-on expectation of community 169 engagement) is essentially a sleep disruption machine. 170 171 I wasn't suicidal. But manic episodes are dangerous in ways people don't talk 172 about enough. You don't sleep for days. Your judgment dissolves. You make 173 decisions that a stable mind would never make. You burn relationships, burn 174 money, burn credibility. You believe things about yourself and the world that 175 aren't true, and you act on those beliefs with absolute conviction. And each 176 episode was worse than the last, escalating in lockstep with the pressure I was 177 putting on myself. 178 179 I had my first serious manic break at that conference in Sweden. I stayed awake 180 for a week. I thought I was enlightened. I was psychotic. 181 182 The second one put me in a hospital for twelve days. I believed I was God. Then 183 Lucifer. Then Jesus. Then a transterrestrial being from the star system Sirius. 184 The psychosis was total. When I came back to reality, I didn't recognize myself 185 or the wreckage around me. 186 187 The same intensity that produced Requests produced the conditions for the worst 188 experiences of my life. The engine was the same. It just had two outputs: 189 beautiful software and shattered minds. Nobody in the open source community 190 talks about this because the survivors go quiet and the ones who don't survive 191 aren't around to write essays. 192 193 I am tired of the silence around this. Open source culture celebrates 194 intensity. It celebrates the all-night hack session, the prolific contributor, 195 the person who maintains fifty projects and keynotes ten conferences a year. 196 What it doesn't celebrate, what it actively looks away from, is what that 197 intensity does to people who are wired differently. And a lot of us are wired 198 differently. That's why we're here in the first place. 199 200 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 201 202 The Cost 203 204 I sold my twenties to a corporation. Heroku was a good employer, and I'm 205 grateful for the years I spent there. But the honest truth is that I was there 206 because of open source, maintained open source while I was there, and the two 207 became so entangled that I couldn't tell where the job ended and the volunteer 208 work began. My most productive years as a human being, the years when I had the 209 most energy and the fewest obligations, were spent in service of a project 210 ecosystem that I maintained for free and a company that benefited from my 211 maintaining it for free. That's not a complaint. It's a description of a deal I 212 made without fully understanding the terms. 213 214 I traveled too much. Conference culture in the 2010s was relentless, and I was 215 in the thick of it. I keynoted, I spoke, I attended, I networked. I saw the 216 inside of more hotel rooms and airport lounges than I can count. At the time it 217 felt like success. In retrospect it was a young person with a mood disorder and 218 no boundaries being fed a steady diet of stimulation and validation that made 219 his condition worse. Every timezone change was a sleep disruption. Every 220 conference was a performance. Every after-party was an opportunity to not rest. 221 222 I gave too much of myself away. Not just code. Myself. My time, my energy, my 223 emotional bandwidth, my identity. I made myself a public resource and then was 224 surprised when the public felt entitled to my resources. This is the deal that 225 open source offers, and it's not a bad deal for everyone, but it was a bad deal 226 for me specifically, given my specific mental health profile and my specific 227 tendency to derive self-worth from external validation. 228 229 I almost lost my mind. Literally. Multiple times. And the culture I was 230 embedded in rewarded the exact behaviors that made the losing more likely. The 231 hypomanic productivity wasn't a warning sign to anyone around me. It was a 232 feature. "Kenneth ships so much code." Yeah. There's a reason for that, and 233 it's not discipline. 234 235 The part that's hardest to write: I don't know who I would have been without 236 open source. That cuts both ways. I might have been nobody. I might have been 237 happier. I might have found my way to a stable career through some other door 238 that didn't require me to make my inner life a public performance. There's no 239 control group for a life. You just live the one you get and try to learn from 240 it. 241 242 What I'd Do Differently 243 244 I would have kept my identity separate from my projects. Requests is a library. 245 I am a person. The conflation of the two was the root cause of most of the 246 damage. When the project is you, every issue is personal, every critique is 247 existential, and every success is addictive in exactly the wrong way. I'd build 248 the thing, release the thing, and then go home and be a person who also built a 249 thing. Not a person who IS the thing. 250 251 I wish I'd had the diagnosis earlier. Not because diagnosis is a magic wand 252 that heals things. It's just information, information I didn't have until there 253 was a crash. But knowing the shape of the thing you're dealing with changes how 254 you move through the world, and I was moving through the world blind. 255 256 I would have said no more. To conferences, to new projects, to the steady 257 expansion of my surface area in the community. Not because those things were 258 bad, but because each yes was another commitment that increased the pressure on 259 a system that was already under more load than it could handle. 260 261 I would not have tied my financial security to the goodwill of a community. 262 That's a fragile foundation for a life, especially when you have a condition 263 that can erode goodwill quickly during an episode. 264 265 These aren't recriminations. They're engineering notes from a post-mortem, 266 written a decade after the incident. 267 268 If You're a Maintainer and You're Wired Like Me 269 270 I want to say something directly to the person reading this who recognizes 271 themselves in it. 272 273 If you're maintaining open source projects and you notice that your 274 productivity comes in surges, that you don't sleep much during the good 275 periods, that your best work happens in states that feel elevated and electric, 276 please pay attention to that. It might just be flow. It might be something 277 else. I didn't know the difference, and by the time I learned, the crash had 278 already happened. 279 280 The things that make you a great open source contributor (hyperfocus, 281 intensity, pattern recognition, the ability to hold entire systems in your 282 head) overlap significantly with the things that make certain psychiatric 283 conditions both more likely and harder to detect. The community will celebrate 284 your output without ever asking what it costs you to produce it. That's not 285 malice. It's just a system that optimizes for code, not for the person writing 286 it. 287 288 Separate your identity from your projects. Find people who see you when you're 289 not shipping. Get a doctor who understands that "I've been incredibly 290 productive lately" is sometimes a symptom, not a success story. Build a life 291 that doesn't depend on the community's approval to feel real. 292 293 I wish someone had told me this when I was twenty-three and staying up for 294 three days straight because the code was flowing so beautifully. The code was 295 beautiful. I was in trouble. 296 297 Where It Lands 298 299 Time heals things. That's a cliche because it's true. 300 301 All things in tech are seasonal. The fame I experienced in 2013 is a different 302 climate than the quiet I experience in 2026. Both are weather. Neither is 303 permanent. The mistake I made was treating the fame season as though it defined 304 the entire climate of my life, and then being unprepared when the season 305 changed. 306 307 I wrote earlier about [52]the values I outgrew and the ones that stayed. That 308 essay is the companion piece to this one. That essay is about where I've 309 landed. This one is about what the landing cost. 310 311 Tech became craft instead of lifestyle. I still write code. I still think about 312 the [53]recursive loop between code and consciousness. I still believe that 313 programmers have a responsibility to think about what kind of minds they're 314 shaping when they ship software. But the center of gravity moved. The code 315 serves the life now, not the other way around. 316 317 I have a son. I have a wife who [54]sees things before I do. I have a faith 318 practice that grounds me in something that doesn't depend on download counts or 319 community approval. I have a diagnosis and a treatment plan and enough 320 self-knowledge to recognize when the engine is running too hot. 321 322 I don't know if I'd do it again. That's the truest thing I can say. The kid in 323 the coworking space didn't have better options, and the path that opened was 324 extraordinary. But knowing what it cost, the mental health crises, the 325 community fracture, the years sold to intensity, the identity built on 326 something that could be taken away by one person's blog post. I don't know. I 327 genuinely don't know. 328 329 What I know is that it happened. It gave me everything and it almost broke me 330 and now it's a part of my history instead of the center of my present. I'm 331 grateful for what it gave. I'm honest about what it took. And I'm done 332 performing either gratitude or grievance about it. 333 334 The house I live in matters more than the code I ship. That's not something I 335 would have written ten years ago. It's the truest thing I can write now. 336 337 © 2026 Kenneth Reitz. [55]Made with love. 338 339 340 References: 341 342 [1] https://github.com/kennethreitz/kennethreitz.org/blob/main/data/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give.md 343 [3] https://kennethreitz.org/ 344 [4] https://kennethreitz.org/archive 345 [5] https://kennethreitz.org/search 346 [6] https://kennethreitz.org/themes/algorithmic-critique 347 [7] https://kennethreitz.org/themes/artificial-intelligence 348 [8] https://kennethreitz.org/themes/consciousness-and-ai 349 [9] https://kennethreitz.org/themes/evolution-of-ideas 350 [10] https://kennethreitz.org/themes/for-humans-philosophy 351 [11] https://kennethreitz.org/themes/mental-health 352 [12] https://kennethreitz.org/themes/open-source-and-community 353 [13] https://kennethreitz.org/themes/pattern-recognition-and-manipulation 354 [14] https://kennethreitz.org/themes/psychology-and-consciousness 355 [15] https://kennethreitz.org/themes/spiritual-practice-and-technology 356 [16] https://kennethreitz.org/themes 357 [17] https://kennethreitz.org/artificial-intelligence 358 [18] https://kennethreitz.org/essays 359 [19] https://kennethreitz.org/music 360 [20] https://kennethreitz.org/photography 361 [21] https://kennethreitz.org/poetry 362 [22] https://kennethreitz.org/software 363 [23] https://kennethreitz.org/talks 364 [24] https://kennethreitz.org/themes 365 [25] https://kennethreitz.org/colophon 366 [26] https://kennethreitz.org/contact 367 [27] https://kennethreitz.org/family 368 [28] https://kennethreitz.org/great-books 369 [29] https://kennethreitz.org/great-music 370 [30] https://kennethreitz.org/mental-health 371 [31] https://kennethreitz.org/plurality 372 [32] https://kennethreitz.org/timeline 373 [33] https://kennethreitz.org/values 374 [34] https://kennethreitz.org/worldview 375 [35] https://kennethreitz.org/yoga-meditation 376 [36] https://kennethreitz.org/ 377 [37] https://kennethreitz.org/essays 378 [39] https://kennethreitz.org/archive/themes#Lived-Experience 379 [40] https://kennethreitz.org/archive/themes#For-Humans 380 [41] https://kennethreitz.org/archive/themes#Open-Source 381 [42] https://kennethreitz.org/archive/themes#Burnout 382 [43] https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give.pdf 383 [44] https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give.md 384 [45] https://kennethreitz.org/software/requests 385 [46] https://kennethreitz.org/essays/2026-03-06-the_coworking_space_saved_my_life 386 [48] https://kennethreitz.org/essays/2025-08-27-from_http_to_consciousness 387 [50] https://kennethreitz.org/essays/2016-01-mentalhealtherror_an_exception_occurred 388 [52] https://kennethreitz.org/essays/2026-03-18-values_i_outgrew_and_the_ones_that_stayed 389 [53] https://kennethreitz.org/essays/2025-09-05-the_recursive_loop_how_code_shapes_minds 390 [54] https://kennethreitz.org/essays/2026-03-06-sarah_knows_first 391 [55] https://kjvstudy.org/topics/Love