commit 20f997d5a693cc1dbbd30337c57f1796982f8d0e parent 0df34caafcfb06c241a69fedccbaf4b4b510a1e6 Author: David Eisinger <[email protected]> Date: Mon, 11 May 2026 00:40:43 -0400 Post progress Diffstat:
20 files changed, 1623 insertions(+), 36 deletions(-)
diff --git a/content/journal/dispatch-39-may-2026/55247387333_60bbe1a7d4_o.jpg.enc b/content/journal/dispatch-39-may-2026/55247387333_60bbe1a7d4_o.jpg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_0185.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_0185.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_0196.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_0196.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_0252.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_0252.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_0261.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_0261.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_0271.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_0271.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_4118.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_4118.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_4132.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_4132.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/IMG_4482.jpeg.enc b/content/journal/dispatch-39-may-2026/IMG_4482.jpeg.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/deck1.png.enc b/content/journal/dispatch-39-may-2026/deck1.png.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/deck2.png.enc b/content/journal/dispatch-39-may-2026/deck2.png.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/dmp_screenshot.png.enc b/content/journal/dispatch-39-may-2026/dmp_screenshot.png.enc Binary files differ. diff --git a/content/journal/dispatch-39-may-2026/index.md b/content/journal/dispatch-39-may-2026/index.md @@ -1,54 +1,151 @@ --- -title: "Dispatch 39 May 2026" -date: 2026-05-10T13:37:01-04:00 +title: "Dispatch #39 (May 2026)" +date: 2026-05-12T01:32:16-04:00 draft: false tags: - dispatch +references: +- title: "Print-in-place - Beginners guide" + url: https://www.thingiverse.com/blog?p=print-in-place-beginners-guide + date: 2026-05-12T04:46:31Z + file: www-thingiverse-com-v7ip1b.txt +- title: "3D Print Your Way Out of Chaos With Gridfinity Modular Storage Systems: All You Need to Know | All3DP" + url: https://all3dp.com/2/gridfinity-simply-explained/ + date: 2026-04-08T05:22:41Z + file: all3dp-com-1skmik.txt +- title: "Optimism is not a personality flaw" + url: https://www.joanwestenberg.com/optimism-is-not-a-personality-flaw/ + date: 2026-05-12T05:27:58Z + file: www-joanwestenberg-com-w65sdh.txt +- title: "Manton Reece - Optimism by default" + url: https://www.manton.org/2026/04/12/optimism-by-default.html + date: 2026-05-12T05:26:33Z + file: www-manton-org-etlydh.txt +- title: "Vibe coding and agentic engineering are getting closer than I’d like" + url: https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/#atom-everything + date: 2026-05-12T05:26:37Z + file: simonwillison-net-0ovi9d.txt +- title: "Open Source Gave Me Everything Until I Had Nothing Left to Give - Kenneth Reitz" + url: https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give + date: 2026-05-12T05:26:42Z + file: kennethreitz-org-ywzt9y.txt +- title: "Favourites of March 2026 | Brain Baking" + url: https://brainbaking.com/post/2026/05/april-2026/ + date: 2026-05-12T05:28:40Z + file: brainbaking-com-vh1pf8.txt --- -- Gridfinity -- Lake -- Tar Heel 10 Miller - - [certificate][1] - - [result][2] -- Car charger / Charging station -- Gitea -- Savannah Bananas -- Joel -- Claire hospitalization -- Asheville - - TTT - - DMP - - Music performance - - Kids + mom + dad - -[1]: /journal/dispatch-39-may-2026/2026_10_miler_certificate.pdf -[2]: /journal/dispatch-39-may-2026/2026_10_miler_result.png +Man, what a month. Rich with the stuff of life. THICK. High highs (Nev's first ballet recital, an incredible trip to Asheville), low lows (the death of our next door neighbor Joel, a major health scare -- don't worry, everyone's alright). Impossible to capture the feeling of it as I sit here, and frankly it feels silly to document all the dumb stuff I get into alongside the heavy shit, but I'm committed to this project. Let's go. <!--more--> +We headed down to Lake Norman for Easter weekend. Good to get some time with our little nephew Sully, who's just a few months younger than Nico. I ran the Tar Heel 10 Miler ([result][1], [certificate][2]), which went okay. Happy enough with my overall time at sub-9 minutes/mile, but I thought I might do a little better until I hit the final climb. + +{{<dither IMG_4118.jpeg "782x600">}}Smiles and life jackets on the lake.{{</dither>}} +{{<dither IMG_4132.jpeg "782x600">}}A gleeful first mate on the water.{{</dither>}} + +{{<dither IMG_0185.jpeg "782x600">}}Cheering from the cheap seats.{{</dither>}} +{{<dither IMG_4482.jpeg "782x600">}}A mid-race high-five on Franklin Street.{{</dither>}} + +Between the race and an ill-fated outing to see the [Savannah Bananas][3], we spent a good bit of time in Chapel Hill, where Claire went to school. Neat for her to be able to show the kids around. I sort of take for granted that we live where I went to college (though the main campus is rather separate and not somewhere we ever go). + +[1]: /journal/dispatch-39-may-2026/2026_10_miler_result.png +[2]: /journal/dispatch-39-may-2026/2026_10_miler_certificate.pdf +[3]: https://thesavannahbananas.com/ + +### Asheville + +At the end of the month, we headed to Asheville for our company's annual gathering, which was awesome. We took over [The Restoration][4] hotel right in the heart of the city. I did a live performance of my song [Asperitas][5], which was well-received and something I've never done before. And we unveiled the project we built as part of the [hackathon in February][6], which went over so well it gets its own section below. + +[4]: https://therestorationhotel.com/asheville-nc-restoration-hotel/ +[5]: /music/#asperitas +[6]: /journal/dispatch-37-march-2026/#pointless-palooza + +After the rest of the company departed, my parents (bless them) brought the kids out, and we got to take them around the city for a few days. Highlights included the [Asheville Museum of Science][7], [WNC Nature Center][8], and [Highland Brewing][9]. + +[7]: https://ashevillescience.org/ +[8]: https://wildwnc.org/ +[9]: https://highlandbrewing.com/ + +{{<dither IMG_0261.jpeg "782x600">}}Story time on the couch.{{</dither>}} +{{<dither IMG_0271.jpeg "782x600">}}Riding high in downtown Asheville.{{</dither>}} + +### Mystery Project + +Right, so in February, I pitched this concept of a 3D-printed name tag tied to a digital product that would encourage people to connect in real life. I worked with a team to build a prototype, but the mechanics still needed fleshing out and the name tag/keychain thing needed refinement. In the subsequent months, my coworker [Steven][10] continued iterating on the keychain, eventually getting to a slick design featuring a [print-in-place][11] hinge and embedded magnets. + +[10]: https://www.viget.com/about/team/shascher +[11]: https://www.thingiverse.com/blog?p=print-in-place-beginners-guide + +About a week before the event, I decided to get serious about the digital updates. I worked with Codex to overhaul the character/inventory system, replacing the AI-generated avatars with a character builder based on the [LPC Spritesheet Character Generator][12] so that people could equip the items they picked up and have that reflected on their avatar. And I added the concept of "item tags," standalone [AprilTags][13] that I 3D printed that could then be associated with items. + +[12]: https://github.com/liberatedpixelcup/Universal-LPC-Spritesheet-Character-Generator +[13]: https://docs.wpilib.org/en/stable/docs/software/vision-processing/apriltag/apriltag-intro.html + +{{<dither 55247387333_60bbe1a7d4_o.jpg "782x600">}}A phone running a pixel-art social game sits beside an orange conference lanyard and badge.{{</dither>}} +{{<dither dmp_screenshot.png "782x600">}}A cigar-smoking pixel-art captain with ski goggles, a glowing blue saber, and a cat sidekick.{{</dither>}} + +The game was a big hit. The keychains were distributed in everyone's welcome bags along with a little explainer card. People were already playing when we got to Asheville (which was a relief as we'd never done a full end-to-end test). We created new items throughout the event (Daft Punk Helmet, Grogu, etc.), associated them with the item tags, and had a lot of fun hiding them at the different event locations. Major props to Claire for running with that side of things. + +I don't know if we'll revisit this concept or if it'll be a one-time thing. I definitely need to write a comprehensive post about it. Look for that next month. + +### Gridfinity + +Still having a blast with the 3D printer. My latest obsession is the [Gridfinity][14] organization system, printing little bins for all of our stuff. + +{{<dither IMG_0196.jpeg "782x600">}}Gridfinity desk organizer.{{</dither>}} +{{<dither IMG_0252.jpeg "782x600">}}Gridfinity/GOEWS entryway organizer.{{</dither>}} + +If you're into this sort of thing, check out this [desktop organizer set][15] and this [wall system][16] you can connect to a Gridfinity base with [this adapter][17] (and a ton of little magnets). + +[14]: https://all3dp.com/2/gridfinity-simply-explained/ +[15]: https://makerworld.com/en/collections/16269937-hexed-desktop-series +[16]: https://www.printables.com/model/1090032-goews-greatly-over-engineered-wall-system +[17]: https://makerworld.com/en/models/831320-gridfinity-goews-tile-stand + +### Deck Project + +Finally, we're in the early stages of replacing our rotted-out deck with a screened-in porch. We met with an architect who showed us some sketches: + +{{<dither deck2.png "782x600">}}Architectural rendering of a screened-in second-story deck addition.{{</dither>}} +{{<dither deck1.png "782x600">}}Architectural sketch of a screened porch and elevated deck addition.{{</dither>}} + +Exciting stuff! This month's looking busy, but I'm feeling relatively unencumbered with all of those obligations out of the way. Looking forward to getting back into music and kicking off the summer with a trip to the lake for Memorial Day and the [Running of the Bulls][18] 8K in downtown Durham. + ### This Month -* Adventure: -* Project: -* Skill: +* Adventure: Lake for Memorial Day; [Running of the Bulls][18] +* Project: make some new music +* Skill: I've been having a lot of fun finger drumming on my sampler while ChatGPT does my job for me -- might try to incorporate that into the new piece + +[18]: https://bullcityrunning.com/our-races/running-of-the-bulls-8k/ ### Reading & Listening -* Fiction: [_Every Tool's a Hammer_][3], Adam Savage -* Non-fiction: [_Operation Bounce House_][4], Matt Dinniman -* Music: [_Title_][5], Author +* Fiction: [_Every Tool's a Hammer_][19], Adam Savage +* Non-fiction: [_Operation Bounce House_][20], Matt Dinniman +* Music: [_Ecology Division_][21], Bastard Jazz Compilations -[3]: https://www.simonandschuster.net/books/Every-Tools-a-Hammer/Adam-Savage/9781982113483 -[4]: https://www.penguinrandomhouse.com/books/772005/operation-bounce-house-by-matt-dinniman/ -[5]: https://www.turntablelab.com/ +[19]: https://www.simonandschuster.net/books/Every-Tools-a-Hammer/Adam-Savage/9781982113483 +[20]: https://www.penguinrandomhouse.com/books/772005/operation-bounce-house-by-matt-dinniman/ +[21]: https://bastardjazzcompilations.bandcamp.com/album/ecology-division ### Links -* [Title][6] -* [Title][7] -* [Title][8] +* [Optimism is not a personality flaw][22] ([via][23]) + + > Whoever can list the most reasons something won't work gets treated as the smartest person in the room. If you say "I think this could go well," you get ~the look. That slight tilt of the head. Optimism is treated like a belief in astrology. Pessimism reads as intelligence now. Optimism reads as naivety. This has gotten so baked into educated Western culture that most people don't notice they're doing it. But it's toxic, all the same. + +* [Vibe coding and agentic engineering are getting closer than I’d like][24] + + > There are a whole bunch of reasons I’m not scared that my career as a software engineer is over now that computers can write their own code, partly because these things are amplifiers of existing experience. If you know what you’re doing, you can run so much faster with them. + +* [Open Source Gave Me Everything Until I Had Nothing Left to Give - Kenneth Reitz][25] ([via][26]) + + > I wish someone had told me this when I was twenty-three and staying up for three days straight because the code was flowing so beautifully. The code was beautiful. I was in trouble. -[6]: https://example.com/ -[7]: https://example.com/ -[8]: https://example.com/ +[22]: https://www.joanwestenberg.com/optimism-is-not-a-personality-flaw/ +[23]: https://www.manton.org/2026/04/12/optimism-by-default.html +[24]: https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/#atom-everything +[25]: https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give +[26]: https://brainbaking.com/post/2026/05/april-2026/ diff --git a/static/archive/brainbaking-com-vh1pf8.txt b/static/archive/brainbaking-com-vh1pf8.txt @@ -0,0 +1,203 @@ +[1]skip to main content +[2] [logo] + + • [3] Archives + • [4] Works + • [5] About + • [6] More... + +Favourites of March 2026 + +3 May 2026 + +It’s May! What happened? This weekend was unusually hot! What happened? +Everyone knows but no-one admits or cares… Anyway, welcome to another month of +2026. I like May. It’s got a lot of national holidays. It signals the start of +lots of great local food: strawberries in abundance, a strong asparagus month +that you should enjoy while it lasts as in June the season is usually over, and +we already ate some fresh French artichokes. It’s getting warmer but not as +scorching as some of the coming months (although given the start of this month, +that remains to be seen). But most of all: the end of May usually indicates the +beginning of the exam period, which for me as an examiner instead of student is +always interesting. Let’s light a candle and pray for not too many LLM-only +submissions. + +Previous month: [7]March 2026. + +Games I’ve played + +A miracle happened: I made some time to get back into gaming—and writing about +games. + + • I finally got to the Kirby spin-offs on the Game Boy: [8]Kirby’s Pinball + Land, [9]Kirby’s Block Ball, and [10]Kirby’s Star Stacker. They’re all + really good! + • But then [11]Robert and a GOG discount pushed me to finally try out [12]The + Drifter. What a thrill. I loved every minute of it. If you like gritty + pixelated adventure games, you can’t miss this. + • After being turned off by the bad technical performance of [13]Ruffy and + the Riverside on the Nintendo Switch, I switched gears to other games. I + picked it up and finished it. It’s an OK N64-inspired collect-a-thon that + should be enjoyed on PC instead. + +In May, we’re finally digging into UFO 50, in chronological order. If we play +one a week we might finish in May 2027… So far, the first entry already is a +home run. + +Selected (blog) posts + + • Speaking of Robert, his [14]/concerts slash page is very cool: it contains + scans of all concert tickets he ever went to. + • Kenneth Reitz tells us to [15]separate our identity from our work/projects, + otherwise bad things happen (via [16]Roy Tang). + • Stefano Marinelli explains [17]why he loves FreeBSD. The Power To Serve + conveys such as strong message, its almost convincing me to jump ship! + Until I read about [18]the laptop gap. This year huh. + • Zakhary Kaplan [19]stole the GBC logo from a ROM and made a cool web logo + from it. + • Cal Newport’s [20]In Defense of Thinking hits yet another nail on the head. + • Forrest’s essay [21]On Pulling The Master Sword links Link’s (ha!) N64 + behaviour to our capitalistic world. It’s a very long essay but well worth + your time if you can stomach a game rant, some swearing, and philosophical + questions about life and society. + • Drakenvlieg manages to pull more [22]students into literature using + journaling (in Dutch). + • Juhis shares his [23]favourite two-player board games. Hive (pocket) is on + the list! + • Chris Smith [24]rates the movies he watched. I’m always interested in the + rating systems other people employ when they do something like this. + • I liked blinry’s [25]Do It Yourself soft drinks experiment. Translucent + coke looks weird! + • Night’s Ham Stock examines [26]the ending story of SKALD the video game I + [27]played in 2024. It was great but I couldn’t make sense of the ending. + Now I still can’t… + • Kain Klarden’s [28]Gex Trilogy review saved me from throwing money at + Limited Run Games. Again. + • [29]It Fits On A Floppy is a strong manifesto for small software that more + developers should read and take heart. + • Eli (Oatmeal) re-iterates something very important: “choose to truly care + about something.” But then he goes much further. I need to re-read this a + couple of times and let it sink in. + • It was also Eli who pointed out the existence of [30]picoSYNTH. + • Richard Moss, the author known for [31]The Secret History of Mac Gaming, is + writing [32]a book on Age of Empires! + • Ruben Schade’s enthusiasm for [33]the Commodore 64 knows no boundaries. The + newly released C64 Ultimate looks very enticing, but where to put all these + things? + • Amelia’s little blog website/host [34]got hammered by AI bots. It’s yet + another infuriating story but the visualisation part is very cool. + +Other random links + + • There’s an interesting upcoming documentary [35]on Clojure the programming + language that might be worth checking out. + • [36]https://www.codingfont.com/ is a cool way to help pick a monospaced + editing font. I’m using JetBrains Mono for now. + • Did you know Windows was released for the Game Boy: + +[37][yt-ad1zZR6] + + • I didn’t know [38]palm rejection was a thing on Linux/KDE. + • The [39]Underkeep Steam demo looks very promising; something to keep close + tabs on! + • I don’t know what this is, but [40]Listography looks like a lot of fun. I + happen to like lists so I should be liking this. + • Isowulf is a very cool [41]isometric perspective Wolfenstein 3D mod. + • You can build retro games using WebAssembly with [42]https://wasm4.org/ + • I love the [43]GoodEnough guestbook that even used to print the drawn + images on thermal paper! + • Thomas Lehmann, the designer of one of my favourite card games ever Race + for the Galaxy, took the deck building genre for another spin. The result + is [44]Dark Pact. Needless to say, it’s on my list. + +[45]metapost + +You Might Also Like... + + • [46]Favourites of March 2026 01 Apr 2026 + • [47]Favourites of February 2026 04 Mar 2026 + • [48]Favourites of January 2026 04 Feb 2026 + • [49]Favourites of December (And a Short 2025 Recap) 10 Jan 2026 + • [50]Favourites of November 2025 03 Dec 2025 + +Bio and Support + +[avatar2024] + +I'm [51]Wouter Groeneveld, a Brain Baker, and I love the smell of freshly baked +thoughts (and bread) in the morning. I sometimes convince others to bake their +brain (and bread) too. + +If you found this article amusing and/or helpful, you can support me via [52] +PayPal or [53]Ko-Fi. I also like to hear your feedback via [54]Mastodon or +email. Thanks! + +JavaScript is disabled. I use it to obfuscate my e-mail, keeping spambots at +bay. +Reach me using: [firstname] at [this domain]. + +↑ [55]Top | [56]Archives | [57]RSS Feed | [58]© CC BY 4.0 License. [59] +[brainbakin] + + +References: + +[1] https://brainbaking.com/post/2026/05/april-2026/#top +[2] https://brainbaking.com/ +[3] https://brainbaking.com/archives/ +[4] https://brainbaking.com/works/ +[5] https://brainbaking.com/about +[6] https://brainbaking.com/more +[7] https://brainbaking.com/post/2026/04/march-2026/ +[8] https://jefklakscodex.com/games/gameboy/kirbys-pinball-land/ +[9] https://jefklakscodex.com/games/gameboy/kirbys-block-ball/ +[10] https://jefklakscodex.com/games/gameboy/kirbys-star-stacker/ +[11] https://www.schafe-sind-bessere-rasenmaeher.de/ +[12] https://jefklakscodex.com/games/pc/the-drifter/ +[13] https://jefklakscodex.com/games/switch/ruffy-and-the-riverside/ +[14] https://schafe-sind-bessere-rasenmaeher.de/concerts/ +[15] https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give +[16] https://roytang.net/ +[17] https://it-notes.dragas.net/2026/03/16/why-i-love-freebsd/ +[18] https://freebsdfoundation.org/blog/freebsd-closes-the-laptop-gap-year-one-project-update/ +[19] https://zakhary.dev/blog/gbc-web-button +[20] https://calnewport.com/in-defense-of-thinking-2/ +[21] https://oncomputer.games/2026/04/27/pulling-the-master-sword/ +[22] https://drakenvlieg.nl/2025/05/24/het-reading-journal/ +[23] https://notes.hamatti.org/gaming/board-games/my-favourite-2-player-games +[24] https://chameth.com/films/ +[25] https://blinry.org/diy-soft-drinks/ +[26] https://nighthams.wordpress.com/2024/09/03/examining-the-story-of-skald-against-the-black-priory-warning-heavy-spoilers/ +[27] https://jefklakscodex.com/games/pc/skald-against-the-black-priory/ +[28] https://klardendum.com/review/o-tempora-gex-trilogy/ +[29] https://fitsonafloppy.com/ +[30] https://johanpeitz.itch.io/picosynth +[31] https://secrethistoryofmacgaming.com/ +[32] https://bossfightbooks.com/products/age-of-empires-by-richard-moss +[33] https://www.rubenerd.au/commodore-releases-the-64c-ultimate/ +[34] https://vulpinecitrus.info/blog/one-in-every-2000-ipv4-visualizing-ddos-ai-web-scrapers/ +[35] https://www.youtube.com/watch?v=JJEyffSdBsk +[36] https://www.codingfont.com/ +[37] https://www.youtube.com/watch?v=ad1zZR6xhZw +[38] https://community.frame.work/t/palm-rejection/40069/24?page=2 +[39] https://store.steampowered.com/app/2411200/Underkeep/ +[40] https://listography.com/static/books/start.html +[41] https://www.youtube.com/watch?v=rqExkeUeiLU +[42] https://wasm4.org/ +[43] https://guestbook.goodenough.us/ +[44] https://boardgamegeek.com/boardgame/448445/dark-pact +[45] https://brainbaking.com/tags/metapost +[46] https://brainbaking.com/post/2026/04/march-2026/ +[47] https://brainbaking.com/post/2026/03/february-2026/ +[48] https://brainbaking.com/post/2026/02/january-2026/ +[49] https://brainbaking.com/post/2026/01/december-2025-and-a-recap/ +[50] https://brainbaking.com/post/2025/12/november-2025/ +[51] https://brainbaking.com/about +[52] https://www.paypal.com/donate/?hosted_button_id=R2WTKY7G9V2KQ +[53] https://ko-fi.com/woutergroeneveld +[54] https://dosgame.club/@jefklak +[55] https://brainbaking.com/post/2026/05/april-2026/#top +[56] https://brainbaking.com/archives +[57] https://brainbaking.com/index.xml +[58] https://brainbaking.com/copyright-and-tracking-policy +[59] https://brainbaking.com/links diff --git a/static/archive/kennethreitz-org-ywzt9y.txt b/static/archive/kennethreitz-org-ywzt9y.txt @@ -0,0 +1,391 @@ +[1] View on GitHub ☀️ 🌙 [3]Home [4]Archive [5]Search +Themes +[svg][6]The Algorithm Eats +[svg][7]Artificial Intelligence +[svg][8]Consciousness & AI +[svg][9]Evolution of Ideas +[svg][10]The "For Humans" Philosophy +[svg][11]Mental Health +[svg][12]Open Source & Community +[svg][13]Pattern Recognition & Manipulation +[svg][14]Psychology & Consciousness +[svg][15]Spiritual Practice & Technology +[16]All Themes → +etc. +[svg][17]artificial-intelligence +[svg][18]essays +[svg][19]music +[svg][20]photography +[svg][21]poetry +[svg][22]software +[svg][23]talks +[svg][24]themes +[svg][25]colophon +[svg][26]contact +[svg][27]family +[svg][28]great-books +[svg][29]great-music +[svg][30]mental-health +[svg][31]plurality +[svg][32]timeline +[svg][33]values +[svg][34]worldview +[svg][35]yoga-meditation +[36]~ / [37]Essays +Icon for Open Source Gave Me Everything Until I Had Nothing Left to Give + +Open Source Gave Me Everything Until I Had Nothing Left to Give + +March 2026 11 min read +4 themes +[39]Lived Experience [40]For Humans [41]Open Source [42]Burnout +[43]PDF [44]Markdown + +I thought I was having a spiritual awakening. I was having a psychiatric +emergency. + +I was at a tech conference in Sweden when it started. I hadn't slept in days. I +was one of the most prolific open source developers in the Python ecosystem, +maintaining the most downloaded HTTP library on Earth, keynoting conferences +across the world, and I was losing my mind in a hotel room six thousand miles +from home. + +Nobody around me knew. The mania looked like productivity. It always does. + +This is the story I've been avoiding writing for a decade. Not the origin story +of [45]Requests, the library I built that changed my life. I've told that one +plenty of times. This is the story of what it cost. + +What Open Source Gave + +Open source didn't just give me a career. It gave me an identity when I had +none. + +I was a college dropout who had been [46]working the front line at McDonald's +the year before. The education system had written me off. My GPA was 1.14. The +standard paths to professional legitimacy were closed, and I had no plan for +opening new ones. I was bidding on freelance jobs for pocket change and hoping +something would happen. + +Open source was the thing that happened. + +When Requests took off, it wasn't just a popular library. It was proof that I +existed, that I was capable, that the thing I could do had value in the world. +The download counts were a scoreboard, and I was winning at the only game that +had ever let me play. Every star on GitHub was a person saying: you matter, +what you built matters, we see you. + +For a kid who had never been seen by any system that was supposed to see him, +that was everything. I don't use the word lightly. It was everything.[47][ ] +Identity formation through open source contribution is more common than people +realize. For those of us who didn't fit the credentialed paths, community +recognition became the primary mirror in which we learned to see ourselves as +capable. This is a gift. It becomes a trap only when the mirror is the only one +you have. + +Open source gave me Heroku. Heroku gave me a salary, health insurance, +colleagues who took me seriously, and a front-row seat to the infrastructure of +the internet. It gave me a platform to advocate for the [48]"for humans" +philosophy that I still believe is one of the most important ideas in software +design. + +It gave me a life. A real one, built from nothing, through craft and generosity +and a community that rewarded good work regardless of where you went to school. + +What follows is not ingratitude. It's accounting. + +The Escalation + +Here's how it worked, practically. You build something good. People use it. +People depend on it. People file issues, request features, report bugs. The +community grows. The responsibility grows. The expectations grow. And because +the thing that gave you your identity is the thing people are depending on, you +can't separate "maintaining the project" from "maintaining yourself." + +I didn't have boundaries around this because I didn't know I needed them. The +kid who had been invisible was now visible, and visibility felt like oxygen. +More users meant more validation. More conferences meant more proof that I +mattered. More projects meant more surface area for the world to see me. I said +yes to everything because saying no felt like closing the door that had saved +my life. + +from dataclasses import dataclass + + +@dataclass +class MaintainerLoop: + """The cycle that builds careers and breaks people.""" + + identity: str + project_success: float = 0.0 + community_expectations: float = 0.0 + self_worth: float = 0.0 + + def cycle(self): + # Success raises expectations. + self.community_expectations = self.project_success * 1.5 + + # Self-worth tracks community response. + self.self_worth = self.project_success + + # When identity IS the project, + # every expectation becomes personal. + # Every criticism lands on the self, + # not just the code. + + # There's no circuit breaker here. + # That's the design flaw. + pass + +Copy + +The pressure was largely self-directed. I want to be honest about that. Nobody +at Heroku was cracking a whip over my open source work. The community wasn't +threatening me. The pressure came from the fact that I had welded my sense of +self to the project's success, and anything that threatened the project +threatened me. A rude issue comment wasn't just feedback about code. It was +someone questioning whether I deserved to exist in the space I'd carved out. + +And underneath all of this, undiagnosed, was bipolar disorder. + +The Crises + +I need to talk about this directly, because the connection between open source +and my mental health crises is the thing I've been avoiding writing about for a +decade. + +I've [50]written about the clinical details elsewhere. What I haven't written +about is the fuel. The manic episodes didn't come from nowhere. They came from +a young person with an undiagnosed mood disorder who was running at maximum +intensity, sleeping four hours a night, crossing time zones every other week, +saying yes to every opportunity, and performing the role of "prolific open +source developer" at a pace that would have been unsustainable for anyone and +was genuinely dangerous for someone with my brain chemistry.[51][ ]The +relationship between external stressors and manic episodes is well-documented +in bipolar disorder research. Stress doesn't cause bipolar disorder, but it can +trigger episodes in people who have it. Sleep disruption is particularly +dangerous, and the open source maintainer lifestyle (conferences across time +zones, late-night coding sessions, the always-on expectation of community +engagement) is essentially a sleep disruption machine. + +I wasn't suicidal. But manic episodes are dangerous in ways people don't talk +about enough. You don't sleep for days. Your judgment dissolves. You make +decisions that a stable mind would never make. You burn relationships, burn +money, burn credibility. You believe things about yourself and the world that +aren't true, and you act on those beliefs with absolute conviction. And each +episode was worse than the last, escalating in lockstep with the pressure I was +putting on myself. + +I had my first serious manic break at that conference in Sweden. I stayed awake +for a week. I thought I was enlightened. I was psychotic. + +The second one put me in a hospital for twelve days. I believed I was God. Then +Lucifer. Then Jesus. Then a transterrestrial being from the star system Sirius. +The psychosis was total. When I came back to reality, I didn't recognize myself +or the wreckage around me. + +The same intensity that produced Requests produced the conditions for the worst +experiences of my life. The engine was the same. It just had two outputs: +beautiful software and shattered minds. Nobody in the open source community +talks about this because the survivors go quiet and the ones who don't survive +aren't around to write essays. + +I am tired of the silence around this. Open source culture celebrates +intensity. It celebrates the all-night hack session, the prolific contributor, +the person who maintains fifty projects and keynotes ten conferences a year. +What it doesn't celebrate, what it actively looks away from, is what that +intensity does to people who are wired differently. And a lot of us are wired +differently. That's why we're here in the first place. + +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ + +The Cost + +I sold my twenties to a corporation. Heroku was a good employer, and I'm +grateful for the years I spent there. But the honest truth is that I was there +because of open source, maintained open source while I was there, and the two +became so entangled that I couldn't tell where the job ended and the volunteer +work began. My most productive years as a human being, the years when I had the +most energy and the fewest obligations, were spent in service of a project +ecosystem that I maintained for free and a company that benefited from my +maintaining it for free. That's not a complaint. It's a description of a deal I +made without fully understanding the terms. + +I traveled too much. Conference culture in the 2010s was relentless, and I was +in the thick of it. I keynoted, I spoke, I attended, I networked. I saw the +inside of more hotel rooms and airport lounges than I can count. At the time it +felt like success. In retrospect it was a young person with a mood disorder and +no boundaries being fed a steady diet of stimulation and validation that made +his condition worse. Every timezone change was a sleep disruption. Every +conference was a performance. Every after-party was an opportunity to not rest. + +I gave too much of myself away. Not just code. Myself. My time, my energy, my +emotional bandwidth, my identity. I made myself a public resource and then was +surprised when the public felt entitled to my resources. This is the deal that +open source offers, and it's not a bad deal for everyone, but it was a bad deal +for me specifically, given my specific mental health profile and my specific +tendency to derive self-worth from external validation. + +I almost lost my mind. Literally. Multiple times. And the culture I was +embedded in rewarded the exact behaviors that made the losing more likely. The +hypomanic productivity wasn't a warning sign to anyone around me. It was a +feature. "Kenneth ships so much code." Yeah. There's a reason for that, and +it's not discipline. + +The part that's hardest to write: I don't know who I would have been without +open source. That cuts both ways. I might have been nobody. I might have been +happier. I might have found my way to a stable career through some other door +that didn't require me to make my inner life a public performance. There's no +control group for a life. You just live the one you get and try to learn from +it. + +What I'd Do Differently + +I would have kept my identity separate from my projects. Requests is a library. +I am a person. The conflation of the two was the root cause of most of the +damage. When the project is you, every issue is personal, every critique is +existential, and every success is addictive in exactly the wrong way. I'd build +the thing, release the thing, and then go home and be a person who also built a +thing. Not a person who IS the thing. + +I wish I'd had the diagnosis earlier. Not because diagnosis is a magic wand +that heals things. It's just information, information I didn't have until there +was a crash. But knowing the shape of the thing you're dealing with changes how +you move through the world, and I was moving through the world blind. + +I would have said no more. To conferences, to new projects, to the steady +expansion of my surface area in the community. Not because those things were +bad, but because each yes was another commitment that increased the pressure on +a system that was already under more load than it could handle. + +I would not have tied my financial security to the goodwill of a community. +That's a fragile foundation for a life, especially when you have a condition +that can erode goodwill quickly during an episode. + +These aren't recriminations. They're engineering notes from a post-mortem, +written a decade after the incident. + +If You're a Maintainer and You're Wired Like Me + +I want to say something directly to the person reading this who recognizes +themselves in it. + +If you're maintaining open source projects and you notice that your +productivity comes in surges, that you don't sleep much during the good +periods, that your best work happens in states that feel elevated and electric, +please pay attention to that. It might just be flow. It might be something +else. I didn't know the difference, and by the time I learned, the crash had +already happened. + +The things that make you a great open source contributor (hyperfocus, +intensity, pattern recognition, the ability to hold entire systems in your +head) overlap significantly with the things that make certain psychiatric +conditions both more likely and harder to detect. The community will celebrate +your output without ever asking what it costs you to produce it. That's not +malice. It's just a system that optimizes for code, not for the person writing +it. + +Separate your identity from your projects. Find people who see you when you're +not shipping. Get a doctor who understands that "I've been incredibly +productive lately" is sometimes a symptom, not a success story. Build a life +that doesn't depend on the community's approval to feel real. + +I wish someone had told me this when I was twenty-three and staying up for +three days straight because the code was flowing so beautifully. The code was +beautiful. I was in trouble. + +Where It Lands + +Time heals things. That's a cliche because it's true. + +All things in tech are seasonal. The fame I experienced in 2013 is a different +climate than the quiet I experience in 2026. Both are weather. Neither is +permanent. The mistake I made was treating the fame season as though it defined +the entire climate of my life, and then being unprepared when the season +changed. + +I wrote earlier about [52]the values I outgrew and the ones that stayed. That +essay is the companion piece to this one. That essay is about where I've +landed. This one is about what the landing cost. + +Tech became craft instead of lifestyle. I still write code. I still think about +the [53]recursive loop between code and consciousness. I still believe that +programmers have a responsibility to think about what kind of minds they're +shaping when they ship software. But the center of gravity moved. The code +serves the life now, not the other way around. + +I have a son. I have a wife who [54]sees things before I do. I have a faith +practice that grounds me in something that doesn't depend on download counts or +community approval. I have a diagnosis and a treatment plan and enough +self-knowledge to recognize when the engine is running too hot. + +I don't know if I'd do it again. That's the truest thing I can say. The kid in +the coworking space didn't have better options, and the path that opened was +extraordinary. But knowing what it cost, the mental health crises, the +community fracture, the years sold to intensity, the identity built on +something that could be taken away by one person's blog post. I don't know. I +genuinely don't know. + +What I know is that it happened. It gave me everything and it almost broke me +and now it's a part of my history instead of the center of my present. I'm +grateful for what it gave. I'm honest about what it took. And I'm done +performing either gratitude or grievance about it. + +The house I live in matters more than the code I ship. That's not something I +would have written ten years ago. It's the truest thing I can write now. + +© 2026 Kenneth Reitz. [55]Made with love. + + +References: + +[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 +[3] https://kennethreitz.org/ +[4] https://kennethreitz.org/archive +[5] https://kennethreitz.org/search +[6] https://kennethreitz.org/themes/algorithmic-critique +[7] https://kennethreitz.org/themes/artificial-intelligence +[8] https://kennethreitz.org/themes/consciousness-and-ai +[9] https://kennethreitz.org/themes/evolution-of-ideas +[10] https://kennethreitz.org/themes/for-humans-philosophy +[11] https://kennethreitz.org/themes/mental-health +[12] https://kennethreitz.org/themes/open-source-and-community +[13] https://kennethreitz.org/themes/pattern-recognition-and-manipulation +[14] https://kennethreitz.org/themes/psychology-and-consciousness +[15] https://kennethreitz.org/themes/spiritual-practice-and-technology +[16] https://kennethreitz.org/themes +[17] https://kennethreitz.org/artificial-intelligence +[18] https://kennethreitz.org/essays +[19] https://kennethreitz.org/music +[20] https://kennethreitz.org/photography +[21] https://kennethreitz.org/poetry +[22] https://kennethreitz.org/software +[23] https://kennethreitz.org/talks +[24] https://kennethreitz.org/themes +[25] https://kennethreitz.org/colophon +[26] https://kennethreitz.org/contact +[27] https://kennethreitz.org/family +[28] https://kennethreitz.org/great-books +[29] https://kennethreitz.org/great-music +[30] https://kennethreitz.org/mental-health +[31] https://kennethreitz.org/plurality +[32] https://kennethreitz.org/timeline +[33] https://kennethreitz.org/values +[34] https://kennethreitz.org/worldview +[35] https://kennethreitz.org/yoga-meditation +[36] https://kennethreitz.org/ +[37] https://kennethreitz.org/essays +[39] https://kennethreitz.org/archive/themes#Lived-Experience +[40] https://kennethreitz.org/archive/themes#For-Humans +[41] https://kennethreitz.org/archive/themes#Open-Source +[42] https://kennethreitz.org/archive/themes#Burnout +[43] https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give.pdf +[44] https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give.md +[45] https://kennethreitz.org/software/requests +[46] https://kennethreitz.org/essays/2026-03-06-the_coworking_space_saved_my_life +[48] https://kennethreitz.org/essays/2025-08-27-from_http_to_consciousness +[50] https://kennethreitz.org/essays/2016-01-mentalhealtherror_an_exception_occurred +[52] https://kennethreitz.org/essays/2026-03-18-values_i_outgrew_and_the_ones_that_stayed +[53] https://kennethreitz.org/essays/2025-09-05-the_recursive_loop_how_code_shapes_minds +[54] https://kennethreitz.org/essays/2026-03-06-sarah_knows_first +[55] https://kjvstudy.org/topics/Love diff --git a/static/archive/simonwillison-net-0ovi9d.txt b/static/archive/simonwillison-net-0ovi9d.txt @@ -0,0 +1,295 @@ +[1]Simon Willison’s Weblog + +[2]Subscribe +Sponsored by: [3]WorkOS — Make your app Enterprise Ready with SSO, SCIM, RBAC, +and more. + +Vibe coding and agentic engineering are getting closer than I’d like + +6th May 2026 + +I recently talked with Joseph Ruscio about AI coding tools for Heavybit’s High +Leverage podcast: [4]Ep. #9, The AI Coding Paradigm Shift with Simon Willison. +Here are some of my highlights, including my disturbing realization that vibe +coding and agentic engineering have started to converge in my own work. + +One thing I really enjoy about podcasts is that they sometimes push me to think +out loud in a way that exposes an idea I’ve not previously been able to put +into words. + +Vibe coding and agentic engineering are starting to overlap [5]# + +A few weeks after vibe coding was first coined I published [6]Not all +AI-assisted programming is vibe coding (but vibe coding rocks), where I firmly +staked out my belief that “vibe coding” is a very different beast from +responsible use of AI to write code, which I’ve since started to call [7] +agentic engineering. + +When Joseph brought up the distinction between the two I had a sudden +realization that they’re not nearly as distinct for me as they used to be: + + Weirdly though, those things have started to blur for me already, which is + quite upsetting. + + I thought we had a very clear delineation where vibe coding is the thing + where you’re not looking at the code at all. You might not even know how to + program. You might be a non-programmer who asks for a thing, and gets a + thing, and if the thing works, then great! And if it doesn’t, you tell it + that it doesn’t work and cross your fingers. + + But at no point are you really caring about the code quality or any of + those additional constraints. And my take on vibe coding was that it’s + fantastic, provided you understand when it can be used and when it can’t. + + A personal tool for you, where if there’s a bug it hurts only you, go + ahead! + + If you’re building software for other people, vibe coding is grossly + irresponsible because it’s other people’s information. Other people get + hurt by your stupid bugs. You need to have a higher level than that. + + This contrasts with agentic engineering where you are a professional + software engineer. You understand security and maintainability and + operations and performance and so forth. You’re using these tools to the + highest of your own ability. I’m finding the scope of challenges I can take + on has gone up by a significant amount because I’ve got the support of + these tools. + + But I’m still leaning on my 25 years of experience as a software engineer. + + The goal is to build high quality production systems: if you’re building + lower quality stuff faster, I think that’s bad. I want to build higher + quality stuff faster. I want everything I’m building to be better in every + way than it was before. + + The problem is that as the coding agents get more reliable, I’m not + reviewing every line of code that they write anymore, even for my + production level stuff. + + I know full well that if you ask Claude Code to build a JSON API endpoint + that runs a SQL query and outputs the results as JSON, it’s just going to + do it right. It’s not going to mess that up. You have it add automated + tests, you have it add documentation, you know it’s going to be good. + + But I’m not reviewing that code. And now I’ve got that feeling of guilt: if + I haven’t reviewed the code, is it really responsible for me to use this in + production? + + The thing that really helps me is thinking back to when I’ve worked at + larger organizations where I’ve been an engineering manager. Other teams + are building software that my team depends on. + + If another team hands over something and says, “hey, this is the image + resize service, here’s how to use it to resize your images”... I’m not + going to go and read every line of code that they wrote. + + I’m going to look at their documentation and I’m going to use it to resize + some images. And then I’m going to start shipping my own features. And if I + start running into problems where the image resizer thing appears to have + bugs or the performance isn’t good, that’s when I might dig into their Git + repositories and see what’s going on. But for the most part I treat that as + a semi-black box that I don’t look at until I need to. + + I’m starting to treat the agents in the same way. And it still feels + uncomfortable, because human beings are accountable for what they do. A + team can build a reputation. I can say “I trust that team over there. They + built good software in the past. They’re not going to build something + rubbish because that affects their professional reputations.” + + Claude Code does not have a professional reputation! It can’t take + accountability for what it’s done. But it’s been proving itself anyway—time + and time again it’s churning out straightforward things and doing them + right in the style that I like. + +There’s an element of [8]the normalization of deviance here—every time a model +turns out to have written the right code without me monitoring it closely +there’s a risk that I’ll trust it at the wrong moment in the future and get +burned. + +The new challenge of evaluating software [9]# + + It used to be if you found a GitHub repository with a hundred commits and a + good readme and automated tests and stuff, you could be pretty sure that + the person writing that had put a lot of care and attention into that + project. + + And now I can knock out a git repository with a hundred commits and a + beautiful readme and comprehensive tests of every line of code in half an + hour! It looks identical to those projects that have had a great deal of + care and attention. Maybe it is as good as them. I don’t know. I can’t tell + from looking at it. Even for my own projects, I can’t tell. + + So I realized what I value more than the quality of the tests and + documentation is that I want somebody to have used the thing. If you’ve got + a vibe coded thing which you have used every day for the past two weeks, + that’s much more valuable to me than something that you’ve just spat out + and hardly even exercised. + +The bottlenecks have shifted [10]# + + If you can go from producing 200 lines of code a day to 2,000 lines of code + a day, what else breaks? The entire software development lifecycle was, it + turns out, designed around the idea that it takes a day to produce a few + hundred lines of code. And now it doesn’t. + + It’s not just the downstream stuff, it’s the upstream stuff as well. I saw + [11]a great talk by Jenny Wen, who’s the design leader at Anthropic, where + she said we have all of these design processes that are based around the + idea that you need to get the design right—because if you hand it off to + the engineers and they spend three months building the wrong thing, that’s + catastrophic. + + There’s this whole very extensive design process that you put in place + because that design results in expensive work. But if it doesn’t take three + months to build, maybe the design process can be a whole lot riskier + because cost, if you get something wrong, has been reduced so much. + +Why I’m still not afraid for my career [12]# + + When I look at my conversations with the agents, it’s very clear to me that + this is moon language for the vast majority of human beings. + + There are a whole bunch of reasons I’m not scared that my career as a + software engineer is over now that computers can write their own code, + partly because these things are amplifiers of existing experience. If you + know what you’re doing, you can run so much faster with them. [...] + + I’m constantly reminded as I work with these tools how hard the thing that + we do is. Producing software is a ferociously difficult thing to do. And + you could give me all of the AI tools in the world and what we’re trying to + achieve here is still really difficult. [...] + + Matthew Yglesias, who’s a political commentator, yesterday [13]tweeted, + “Five months in, I think I’ve decided that I don’t want to vibecode — I + want professionally managed software companies to use AI coding assistance + to make more/better/cheaper software products that they sell to me for + money.” And that feels about right to me. I can plumb my house if I watch + enough YouTube videos on plumbing. I would rather hire a plumber. + +On the threat to SaaS providers of companies rolling their own solutions +instead: + + I just realized it’s the thing I said earlier about how I only want to use + your side project if you’ve used it for a few weeks. The enterprise version + of that is I don’t want a CRM unless at least two other giant enterprises + have successfully used that CRM for six months. [...] You want solutions + that are proven to work before you take a risk on them. + +Posted [14]6th May 2026 at 2:24 pm · Follow me on [15]Mastodon, [16]Bluesky, +[17]Twitter or [18]subscribe to my newsletter + +More recent articles + + • [19]Notes on the xAI/Anthropic data center deal - 7th May 2026 + • [20]Live blog: Code w/ Claude 2026 - 6th May 2026 + +This is Vibe coding and agentic engineering are getting closer than I’d like by +Simon Willison, posted on [21]6th May 2026. + +[22] ai 2016 [23] generative-ai 1785 [24] llms 1751 [25] podcast-appearances 39 +[26] vibe-coding 90 [27] coding-agents 201 [28] agentic-engineering 50 + +Next: [29]Live blog: Code w/ Claude 2026 + +Previous: [30]LLM 0.32a0 is a major backwards-compatible refactor + +Monthly briefing + +Sponsor me for $10/month and get a curated email digest of the month's most +important LLM developments. + +Pay me to send you less! + +[31] Sponsor & subscribe + + • [32]Disclosures + • [33]Colophon + • © + • [34]2002 + • [35]2003 + • [36]2004 + • [37]2005 + • [38]2006 + • [39]2007 + • [40]2008 + • [41]2009 + • [42]2010 + • [43]2011 + • [44]2012 + • [45]2013 + • [46]2014 + • [47]2015 + • [48]2016 + • [49]2017 + • [50]2018 + • [51]2019 + • [52]2020 + • [53]2021 + • [54]2022 + • [55]2023 + • [56]2024 + • [57]2025 + • [58]2026 + • + + +References: + +[1] https://simonwillison.net/ +[2] https://simonwillison.net/about/#subscribe +[3] https://fandf.co/4daZLgh +[4] https://www.heavybit.com/library/podcasts/high-leverage/ep-9-the-ai-coding-paradigm-shift-with-simon-willison +[5] https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/#vibe-coding-and-agentic-engineering-are-starting-to-overlap +[6] https://simonwillison.net/2025/Mar/19/vibe-coding/ +[7] https://simonwillison.net/guides/agentic-engineering-patterns/what-is-agentic-engineering/ +[8] https://simonwillison.net/2025/Dec/10/normalization-of-deviance/ +[9] https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/#the-new-challenge-of-evaluating-software +[10] https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/#the-bottlenecks-have-shifted +[11] https://simonwillison.net/2026/Jan/24/dont-trust-the-process/ +[12] https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/#why-i-m-still-not-afraid-for-my-career +[13] https://twitter.com/mattyglesias/status/2049105745132585161 +[14] https://simonwillison.net/2026/May/6/ +[15] https://fedi.simonwillison.net/@simon +[16] https://bsky.app/profile/simonwillison.net +[17] https://twitter.com/simonw +[18] https://simonwillison.net/about/#subscribe +[19] https://simonwillison.net/2026/May/7/xai-anthropic/ +[20] https://simonwillison.net/2026/May/6/code-w-claude-2026/ +[21] https://simonwillison.net/2026/May/6/ +[22] https://simonwillison.net/tags/ai/ +[23] https://simonwillison.net/tags/generative-ai/ +[24] https://simonwillison.net/tags/llms/ +[25] https://simonwillison.net/tags/podcast-appearances/ +[26] https://simonwillison.net/tags/vibe-coding/ +[27] https://simonwillison.net/tags/coding-agents/ +[28] https://simonwillison.net/tags/agentic-engineering/ +[29] https://simonwillison.net/2026/May/6/code-w-claude-2026/ +[30] https://simonwillison.net/2026/Apr/29/llm/ +[31] https://github.com/sponsors/simonw/ +[32] https://simonwillison.net/about/#disclosures +[33] https://simonwillison.net/about/#about-site +[34] https://simonwillison.net/2002/ +[35] https://simonwillison.net/2003/ +[36] https://simonwillison.net/2004/ +[37] https://simonwillison.net/2005/ +[38] https://simonwillison.net/2006/ +[39] https://simonwillison.net/2007/ +[40] https://simonwillison.net/2008/ +[41] https://simonwillison.net/2009/ +[42] https://simonwillison.net/2010/ +[43] https://simonwillison.net/2011/ +[44] https://simonwillison.net/2012/ +[45] https://simonwillison.net/2013/ +[46] https://simonwillison.net/2014/ +[47] https://simonwillison.net/2015/ +[48] https://simonwillison.net/2016/ +[49] https://simonwillison.net/2017/ +[50] https://simonwillison.net/2018/ +[51] https://simonwillison.net/2019/ +[52] https://simonwillison.net/2020/ +[53] https://simonwillison.net/2021/ +[54] https://simonwillison.net/2022/ +[55] https://simonwillison.net/2023/ +[56] https://simonwillison.net/2024/ +[57] https://simonwillison.net/2025/ +[58] https://simonwillison.net/2026/ diff --git a/static/archive/www-joanwestenberg-com-w65sdh.txt b/static/archive/www-joanwestenberg-com-w65sdh.txt @@ -0,0 +1,286 @@ +[1] >Westenberg. [MENU] [3] 1. About [4] 2. Self [5] 3. RSS [6] 4. Tools [7] 5. +YouTube [8] 6. Forum | [9] / Search | [10] → Sign in [11] + Subscribe +STATUS // operational +Westenberg. | v1.0 | 2026 +2026-04-12 // 6 min read + +Optimism is not a personality flaw + +AUTHOR // [12]JA Westenberg ACCESS // true +Optimism is not a personality flaw Photo by [13]Cherry Laithang / [14]Unsplash + +On October 4, 1957, the Soviet Union launched Sputnik - and the United States +lost its collective mind. Newspapers ran headlines about Soviet nuclear weapons +raining from orbit, and schools held duck-and-cover drills. Eisenhower's +approval rating cratered and the smartest people in Washington agreed that +America had fallen behind, for good, the free world was in terminal decline, +and their enemies were about to launch space-faring Nukes. + +Then, eleven years and 8 months later, Neil Armstrong stepped onto the moon. +One small step, etc. + +Folks in 1957 had at least some reason to be afraid, and the fear was grounded +in something real: you could measure the gap in rocket technology down to the +pound of thrust. But the people who responded to that fear by building things +(the Apollo program, the engineers who decided the problem was solvable) landed +on the moon. The people who responded by predicting doom were forgotten before +the decade was out. + +I can't think of a better summary of the argument I'm trying to make here... + +In the last 15 years, a specific kind of intellectual posture has taken hold +everywhere. I've started calling it "competitive pessimism" - which might not +be perfect, but it's the best I've got. + +Whoever can list the most reasons something won't work gets treated as the +smartest person in the room. If you say "I think this could go well," you get +~the look. That slight tilt of the head. Optimism is treated like a belief in +astrology. + +Pessimism reads as intelligence now. + +Optimism reads as naivety. + +This has gotten so baked into educated Western culture that most people don't +notice they're doing it. But it's toxic, all the same. + +Where this came from + +The instinct has some logic to it, I'll be fair about that. + +The 21st century opened with the dot-com crash, which wiped $5 trillion off the +NASDAQ between March 2000 and October 2002. Then September 11th, and the +Afghanistan War, and then the Iraq War. Then the 2008 financial crisis, which +destroyed 8.7 million American jobs in eighteen months. Then Obama! And then +Trump. Then a pandemic that killed over a million people in the US alone. +Climate reports from the IPCC kept landing, each one worse. If you paid +attention to any of this, bracing for impact started to look like base common +sense. + +The internet of course poured a gasoline on all of it. In 2012, Jonah Berger +and Katherine Milkman at Wharton went through about seven thousand New York +Times articles and tracked which ones readers actually emailed to their +friends. The anxious // angry pieces won. The hopeful writing just sort +of...sat there. The platforms didn't need an academic paper to work this out. +Doom = clicks. Doom = ad revenue. Doom got you a booking on Joe Rogan. +Pessimists built media empires, and optimists built water treatment plants in +sub-Saharan Africa and nobody wrote a magazine cover about them. + +Pessimism is useful and I won't be glib about that. You want a pessimist +reviewing the specs on the I-35W bridge before it goes up. You want a pessimist +reading your bloodwork. Risk assessment is a discipline that saves lives every +single day. What happened over the last two decades is that risk assessment +slid from being a discipline into being a disposition; worry stopped being +something you ~did and became something you ~were. + +And that's where the trouble started. + +What the doomers predicted + +In 1894, the Times of London published a calculation: at current rates of +growth, the city's streets would be buried under nine feet of horse manure by +the 1940s. The math was technically on the money: fifty thousand horses working +in London at the time, each producing 15 to 35 pounds of dung per day, with a +population growing...the arithmetic pointed one way. + +What nobody at the Times knew was that Karl Benz, tinkering in a shop in +Mannheim, had already patented a gasoline-powered vehicle eight years earlier. +The car scaled up, the manure problem disappeared and a completely different +set of problems showed up in its place. + +Thomas Malthus did the same thing a century earlier, in his 1798 Essay on the +Principle of Population. Population grows geometrically, food arithmetically, +and therefore - famine is mathematically inevitable. He published this at the +start of the Agricultural Revolution. Paul Ehrlich doubled down in 1968: "The +battle to feed all of humanity is over," he wrote on page one of The Population +Bomb, "In the 1970s hundreds of millions of people will starve to death." + +Well, food production tripled instead. + +Peak oil in 2005, same story; the doomsday logic was always internally +consistent. The world just did not cooperate. + +I know I'm cherry-picking here. Listing reversals is easy. Plenty of problems +didn't get fixed. Plenty of hopeful people were dead wrong. But the doomers +were also wrong, and the doomers didn't build anything while they were busy +~being wrong. + +The optimists who failed at least generated attempts. + +This is the asymmetry I keep snagging on. + +Why it feels smart to be grim + +In 1984, a psychologist at Berkeley named Philip Tetlock started cornering +experts at conferences and asking them to make specific, testable predictions. + + • Would the Soviet Union collapse within five years? + • Would inflation top 6%? + +He accumulated tens of thousands of these forecasts from 284 political +scientists, economists, and government advisors, and after twenty years he +scored them all against reality. Most of the experts performed about as well as +"dart-throwing chimpanzees" -- Tetlock's line, not mine. The very worst +forecasters were the folks with One Grand Theory™️ who bent all incoming data +to fit it. + +Nobody puts the careful, uncertain forecasters on television. + +"I see arguments on both sides and I'm not confident" doesn't fill a segment. + +This is an ongoing complaint of mine. + +And then there's the reputation factor. If you predict a catastrophe and you're +wrong, nobody circles back to check - and your wrong call just dissolves. If +you predict things will work out and they don't, that shit follows you around +forever. The lopsidedness of the payoff alone is enough to push smart, careful +people toward the darkest possible forecast even when the evidence is genuinely +mixed. + +Being wrong about doom costs you nothing. + +Being wrong about hope costs you your career. + +Hope as a decision + +Cornel West split optimism and hope into two separate things... + + • Optimism is a spectator sport, in his framing. You watch the data and + decide whether the trend lines look good. + • Hope is a commitment to act as though improvement is possible, because + without that commitment you guarantee it isn't. Nobody serious is claiming + things will get better on their own. In fact, things can only get better if + enough people act as though they might. + +Every hospital that got built started with someone saying "we can treat those +people." Every civil rights movement and every vaccine that reduced suffering +began with someone who looked at a bad situation and decided to treat it as a +problem to solve, and a problem that ~could be solved. + +"What about the problems that didn't get solved? What about the optimists who +were wrong?" + +Well, what about them? + +The optimists who were wrong still attempted something. + +The pessimists who were right attempted nothing. + +And the world runs on attempts, not on accurate // profound predictions of +failure. + +The permanent bracing costs + +At the University of Pennsylvania, Martin Seligman spent decades studying what +he called "learned helplessness." He found that people who explain bad events +as permanent and personal, baked into the fabric of reality, are more likely to +become depressed and less likely to keep trying. I should know. That about +accurately describes my emotional state for most of my 20's. + +The cultural pessimism that passes for intelligence has the same structure - if +your default explanation for every problem is "systems are broken and people +are selfish, so nothing will ever be different," you've adopted a worldview +that is indistinguishable from despair, and you might call it realism but it +produces the same behavior as hopelessness. + +When pessimism becomes the default in public conversation, it starts building +the world it claims to be describing. People who believe nothing can be +different don't vote, don't volunteer, don't start companies, don't run for +office, don't build the thing that might have mattered. + +Pessimism at scale is a self-fulfilling prophecy. + +Rebecca Solnit put it well in Hope in the Dark: "Hope is not a lottery ticket +you can sit on the sofa and clutch, feeling lucky. It is something you do." + +The stubborn, irrational case + +In 1903, Simon Newcomb - a professor of mathematics at Johns Hopkins and +probably the most credentialed scientist in the country - wrote a widely-read +essay arguing that powered heavier-than-air flight was a practical +impossibility. And on December 17 of that same year, Wilbur and Orville Wright +flew four times at Kitty Hawk. The longest flight lasted 59 seconds and covered +852 feet. Newcomb never revised his position. + +Pessimism is more accurate in the short term - almost always, I'll give it +that. Things do go wrong in roughly the ways people predict they will. But +optimism is more productive over decades. Optimism is the thing that generates +attempts, and without attempts nothing changes. + +Blind cheerfulness ignores evidence, crashes planes, builds the Humane AI Pin +and bankrupts companies. Nobody wants that. But the choice to look at bad data +and act anyway, because sitting still is the one move that guarantees the bad +outcome, is a noble one. + +The most dangerous idea I keep running into is that there is nothing to be +done. It's the one idea that, if enough people hold it, comes true - and I +refuse to treat that as a serious intellectual position. I refuse to let Quiet +Quitting become the dominant intellectual model of our age. + +I would rather be wrong about what we're capable of than right about why we +shouldn't bother trying... + +$ whois studio-self + +Westenberg is designed, built and funded by Studio Self. + +We make tech legible. + +[15]Work with us. +$ cat ./comments +$ cat ./subscribe.md + +Get updates + +Field Notes on Now. + +[16][ ] SUBSCRIBE_ +[18]About/// [19]Self/// [20]RSS/// [21]Tools/// [22]YouTube/// [23]Forum/// +[24]About/// [25]Self/// [26]RSS/// [27]Tools/// [28]YouTube/// [29]Forum/// +[30]About/// [31]Self/// [32]RSS/// [33]Tools/// [34]YouTube/// [35]Forum/// +[36]About/// [37]Self/// [38]RSS/// [39]Tools/// [40]YouTube/// [41]Forum/// +© 2026 Westenberg. [42]Sign up +Westenberg is designed, built, and backed by [43]Studio Self + +References: + +[1] https://www.joanwestenberg.com/ +[3] https://www.joanwestenberg.com/about/ +[4] https://www.thisisstudioself.com/ +[5] https://www.joanwestenberg.com/rss/ +[6] https://studioself.gumroad.com/ +[7] https://www.youtube.com/@jawestenberg +[8] https://westenberg.discourse.group/ +[9] https://www.joanwestenberg.com/optimism-is-not-a-personality-flaw/# +[10] https://www.joanwestenberg.com/signin/ +[11] https://www.joanwestenberg.com/signup/ +[12] https://www.joanwestenberg.com/author/jawestenberg/ +[13] https://unsplash.com/@laicho?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit +[14] https://unsplash.com/?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit +[15] https://thisisstudioself.com/ +[18] https://www.joanwestenberg.com/about/ +[19] https://www.thisisstudioself.com/ +[20] https://www.joanwestenberg.com/rss/ +[21] https://studioself.gumroad.com/ +[22] https://www.youtube.com/@jawestenberg +[23] https://westenberg.discourse.group/ +[24] https://www.joanwestenberg.com/about/ +[25] https://www.thisisstudioself.com/ +[26] https://www.joanwestenberg.com/rss/ +[27] https://studioself.gumroad.com/ +[28] https://www.youtube.com/@jawestenberg +[29] https://westenberg.discourse.group/ +[30] https://www.joanwestenberg.com/about/ +[31] https://www.thisisstudioself.com/ +[32] https://www.joanwestenberg.com/rss/ +[33] https://studioself.gumroad.com/ +[34] https://www.youtube.com/@jawestenberg +[35] https://westenberg.discourse.group/ +[36] https://www.joanwestenberg.com/about/ +[37] https://www.thisisstudioself.com/ +[38] https://www.joanwestenberg.com/rss/ +[39] https://studioself.gumroad.com/ +[40] https://www.youtube.com/@jawestenberg +[41] https://westenberg.discourse.group/ +[42] https://www.joanwestenberg.com/optimism-is-not-a-personality-flaw/#/portal/ +[43] https://thisisstudioself.com/ diff --git a/static/archive/www-manton-org-etlydh.txt b/static/archive/www-manton-org-etlydh.txt @@ -0,0 +1,80 @@ +● [1]Manton Reece +[2]About [3]Photos [4]Videos [5]Archive [6]30 days [7]90 parks [8]Reading [9] +Search [10]Also on Micro.blog + +Optimism by default + +[11]Apr 12, 2026 + +[12]This new essay by JA Westenberg about pessimism comes at just about the +perfect time, relating to many things in the current tech world: + + Whoever can list the most reasons something won’t work gets treated as the + smartest person in the room. If you say “I think this could go well,” you + get ~the look. That slight tilt of the head. Optimism is treated like a + belief in astrology. + +And: + + When pessimism becomes the default in public conversation, it starts + building the world it claims to be describing. People who believe nothing + can be different don’t vote, don’t volunteer, don’t start companies, don’t + run for office, don’t build the thing that might have mattered. + +I always want to be the naive optimist who believes in people and believes in +ambitious new projects that probably won’t work. Everything good I’ve done is a +result of that. + +[13]Also on Bluesky +● Matt Anderson + +I appreciate how well the quote and your post put words to this concept! +Totally agree! + +[14]2026-04-12 08:39 + +Sign in with [15]Micro.blog, [16]Mastodon, or [17]Bluesky to reply: + +[ ] +[ ] +[ ] +[ ] + +[22][Post] + +[23] [3] +[24] Manton Reece [25]@manton + + • [26]RSS + • [27]JSON Feed + • [28]Surprise me! + • [29]Tweets + +×←→ + +References: + +[1] https://www.manton.org/ +[2] https://www.manton.org/about/ +[3] https://www.manton.org/photos/ +[4] https://www.manton.org/videos/ +[5] https://www.manton.org/archive/ +[6] https://www.manton.org/30-days/ +[7] https://www.manton.org/90-parks/ +[8] https://www.manton.org/reading/ +[9] https://www.manton.org/search/ +[10] https://micro.blog/manton +[11] https://www.manton.org/2026/04/12/optimism-by-default.html +[12] https://www.joanwestenberg.com/optimism-is-not-a-personality-flaw/ +[13] at://did:plc:pko7wbcggok753hnvndxh3ni/app.bsky.feed.post/3mjcekyspzw2z +[14] https://micro.blog/mathyousee/88102104 +[15] https://micro.blog/account/comments/88099573/mb?url=https://www.manton.org/2026/04/12/optimism-by-default.html +[16] https://micro.blog/account/comments/88099573/mastodon?url=https://www.manton.org/2026/04/12/optimism-by-default.html +[17] https://micro.blog/account/comments/88099573/bluesky?url=https://www.manton.org/2026/04/12/optimism-by-default.html +[23] https://www.manton.org/ +[24] https://www.manton.org/ +[25] https://micro.blog/manton +[26] https://www.manton.org/feed.xml +[27] https://www.manton.org/feed.json +[28] https://www.manton.org/surprise-me/ +[29] https://www.manton.org/tweets/ diff --git a/static/archive/www-thingiverse-com-v7ip1b.txt b/static/archive/www-thingiverse-com-v7ip1b.txt @@ -0,0 +1,235 @@ +[1] +[3] +Challenges +Explore, enter and win with your own designs +[4] +Forum +Learn, discuss and share with other makers +[5] +Events +Browse or suggest open-source hardware and 3D printing events +[7]All Categories[8]3D Printing[9]Art[10]Fashion[11]Gadgets[12]Hobby[13] +Household[14]Learning[15]Models[16]Tools[17]Toys & Games[18]Other +[20][ ] +Log In +Join the Community +Small thing previews +2M+ Things across categories +Small creator previews +70k+ Creators +[22]Sign up to Thingiverse! +Already have an account?[23]Log in + +Print-in-place - Beginners guide + +Print-in-place - Beginners guide + +Alexandru Pascovici [24]Alexandru Pascovici [25]Guides +August 6th, 2025 4 minute read + +Did you see a fun articulated dragon on YouTube or at a craft fair that you +want to print? Or maybe a model with complex-looking hinges? How about a +brain-teasing puzzle with lots of moving parts? All of these can be printed and +assembled using glue or fasteners. But they can also be printed already +assembled with no extra work required! These are called print-in-place models, +and this article explains exactly what they are and how you can print them! + +What is a print-in-place model? + +Simply put, any 3D printable design that has moving or interlocking parts that +are built as one continuous print job falls under the print-in-place umbrella. + +More precisely, in a print-in-place model, the moving or interlocking parts are +designed with precise clearances that allow them to be printed as a single +assembly without needing any post-printing assembly. + +These parts are typically suspended within or connected to the main body of the +model in such a way that they remain stationary during printing, either +directly attached to the build plate or supported by small breakaway bridges, +joints, or supports. + +Once the print is complete, a simple flex or twist is often enough to free the +moving parts, allowing hinges, sliders, gears or articulated segments to move +freely without any additional post-processing. + +The main advantage of these kinds of models is that they save time, removing +the hassle of screws, snap-fits, glue, or various other post-processing “fiddly +bits” that can be especially frustrating for a beginner maker. + +How do I find print-in-place designs? + +Ok, cool, by now you’re sold on the idea of print-in-place designs, but you +don’t know what exactly to print, so here’s where we come in, if you don’t mind +a suggestion or two. + +For everyday utility, we recommend trying out these Things (we even printed +some of these ourselves since they were so useful). + +[phone-stand-thing] + +[26]Phone/Tablet Stand - Flat fold - Print in place! +By: [27]jonnig + +[large-display-printinplace-kaleidocycle] + +[28]Print-in-Place Kaleidocycle +By: [29]ecoiras + +[fidget-cube-thing][30]Print In Place Ultimate Fidget Cube +By: [31]mygadgetlife + +[nozzle-box-thing] + +[32] Print in Place Nozzle Box +By: [33]John_Wet + + +If none of these strike your fancy, try searching “print-in-place” on +Thingiverse to find a plethora of Things to choose from. + +How do I print a print-in-place model?? + +Argh! You’ve tried printing a design, and it simply didn’t come out as +advertised! Joints can’t be moved, bearings don’t rotate, hinges break rather +than bend, and so on… + +To be fair, a lot of the print-in-place designs are difficult to print by +nature, especially on older printers, because of their tight tolerances. Any +overextrusion or dimensional inaccuracies will cause sections within the Thing +to fuse and compromise its functionality. + +In order to ensure you have the best possible chances, we recommend the +following steps: + + 1. Calibrate your printer! If your printer doesn’t have an autocalibration + feature, Matt the Printing Nerd has a [34]great guide on how to calibrate + your printer, but if you want to go more in-depth, you can also check out + Ellis’ [35]Print Tuning Guide. + + 2. Check the Thing details tab; many makers provide specific instructions and + parameters that you should use for your print. These will probably be + tailored to the specific model you're trying to print and might give you + just the help you need! + + 3. Ensure first-layer adhesion. Especially for longer prints, keep an eye out + while the first 1-2 layers extrude. Layer shifts will ruin print-in-place + prints. If your prints have a tendency to unstick themselves from the build + plate, a good old-fashioned glue stick might just do the trick + + 4. Slow down! If all else fails, slowing your print speeds way down should + result in a more dimensionally accurate and functional print. + +This might sound weird, but if you’re having issues and you already followed +all of the above steps, there’s one more bonus technique you can try: scale up +the design. + +Increasing the model size means that the tolerances between the moving parts +become less of an issue (clearance grows with scale). While this isn’t exactly +a fix, but more of a workaround, it should help, so why not give it a shot? + +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ + +That’s pretty much it. If you successfully printed a print-in-place Thing, +don’t forget to share it by uploading an image of it on the Thing’s page! And +if you want more 3D printing tips and tricks from us, [36]sign up for our +newsletter! + +[37] [38] [39] [40] + +[41]« Back to Blog + +Related Articles + +Low-poly models - Beginners guide + +[42] Low-poly models - Beginners guide + +6 minute read + +July 3rd, 2025 + +HueForge - Beginners guide + +[43] HueForge - Beginners guide + +5 minute read + +September 16th, 2025 + +Articulated prints - Beginners guide + +[44] Articulated prints - Beginners guide + +6 minute read + +October 9th, 2025 + +[45]About us[46]SoulCrafted[47]FAQ[48]Blog +[49]Cura[50]For Developers +[51][52][53][54][55] + +Subscribe for news, community spotlights, and more! + +[56][ ] +Subscribe +[58]Advertise with Us +Cookies[60]Legal[61]Privacy Policy[62]Changelog +iiq_pixel +iiq_pixel + +References: + +[1] https://www.thingiverse.com/ +[3] https://www.thingiverse.com/challenges +[4] https://forum.thingiverse.com/ +[5] https://labs.thingiverse.com/events +[7] https://www.thingiverse.com/search? +[8] https://www.thingiverse.com/search?category_id=73 +[9] https://www.thingiverse.com/search?category_id=63 +[10] https://www.thingiverse.com/search?category_id=64 +[11] https://www.thingiverse.com/search?category_id=65 +[12] https://www.thingiverse.com/search?category_id=66 +[13] https://www.thingiverse.com/search?category_id=67 +[14] https://www.thingiverse.com/search?category_id=69 +[15] https://www.thingiverse.com/search?category_id=70 +[16] https://www.thingiverse.com/search?category_id=71 +[17] https://www.thingiverse.com/search?category_id=72 +[18] https://www.thingiverse.com/search?category_id=0 +[22] https://www.thingiverse.com/register +[23] https://www.thingiverse.com/login?redirect=https%3A%2F%2Fwww.thingiverse.com%2Fblog%3Fp%3Dprint-in-place-beginners-guide +[24] https://www.thingiverse.com/blog?a=alexandru-pascovici +[25] https://www.thingiverse.com/blog?c=guides +[26] https://www.thingiverse.com/thing:3146835 +[27] https://www.thingiverse.com/jonnig/designs +[28] https://www.thingiverse.com/thing:4761150 +[29] https://www.thingiverse.com/ecoiras/designs +[30] https://www.thingiverse.com/thing:6894971 +[31] https://www.thingiverse.com/mygadgetlife/designs +[32] https://www.thingiverse.com/thing:4716051 +[33] https://www.thingiverse.com/john_wet/designs +[34] https://www.youtube.com/watch?v=ikvOHPZL6Cc +[35] https://ellis3dp.com/Print-Tuning-Guide/ +[36] https://www.thingiverse.com/ne +[37] https://facebook.com/sharer/sharer.php?u=https%3A%2F%2Fshare.dropinblog.com%2Fs%2Foaxvwz +[38] https://x.com/intent/post/?text=Print-in-place+-+Beginners+guide%0A&url=https%3A%2F%2Fshare.dropinblog.com%2Fs%2Foaxvwz +[39] https://wa.me/?text=Print-in-place+-+Beginners+guide%0Ahttps%3A%2F%2Fshare.dropinblog.com%2Fs%2Foaxvwz +[40] mailto:?subject=Print-in-place%20-%20Beginners%20guide&body=%0A%0APrint-in-place%20-%20Beginners%20guide%0Ahttps%3A%2F%2Fshare.dropinblog.com%2Fs%2Foaxvwz +[41] https://www.thingiverse.com/blog +[42] https://www.thingiverse.com/blog?p=getting-started-with-low-poly-models-a-beginners-printing-guide +[43] https://www.thingiverse.com/blog?p=hueforge-beginners-guide +[44] https://www.thingiverse.com/blog?p=articulated-prints-beginners-guide +[45] https://www.thingiverse.com/about +[46] https://www.soulcrafted.it/ +[47] https://www.thingiverse.com/support +[48] https://www.thingiverse.com/blog +[49] https://www.thingiverse.com/software/ultimaker-cura +[50] https://www.thingiverse.com/developers +[51] https://www.instagram.com/thingiverse +[52] https://www.tiktok.com/@thingiversewastaken +[53] https://www.youtube.com/@thingiversewastaken +[54] https://x.com/thingiverse +[55] https://www.facebook.com/Thingiverse +[58] https://www.thingiverse.com/about/advertising +[60] https://www.thingiverse.com/legal +[61] https://www.thingiverse.com/legal/privacy +[62] https://www.thingiverse.com/changelog diff --git a/themes/v2/layouts/music/list.html b/themes/v2/layouts/music/list.html @@ -10,7 +10,7 @@ {{ $page := . }} {{ range sort (.Resources.Match "*.mp3") "Title" "desc" }} - <div class="music-track"> + <div id="{{ substr .Title 0 -4|urlize }}" class="music-track"> <audio controls src="{{ .RelPermalink }}"></audio> <div>
