Growth, Hackathons, and Gratitude Lessons from an Eventful 2025 🔗 **Source:** [Growth, Hackathons, and Gratitude Lessons from an Eventful 2025](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/) > [!note]+ Document Notes > tags: [WordPress, AI, career-growth] > author: [openchannels.fm] > source: [openchannels.fm] > reference: [https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/] > date created: > > # 🏷️ Title: Growth, Hackathons, and Gratitude Lessons from an Eventful 2025 > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - Zach and Carl recap a packed 2025: CloudFest hackathons, new partnerships, rapid AI/LLM changes, and personal health journeys. - It shows how fast the WordPress/open web ecosystem is evolving across business, tooling, and AI. - Stakeholders: WordPress hosts, developers, community organizers, and indie product folks. - Risks: burnout, FOMO around AI, health issues, and economic pressure on independents. - Bottom line: sustainable growth means pairing experimentation (AI, hackathons, partnerships) with boundaries, health, and gratitude. ## 📖 Main Content - The episode opens with both hosts reflecting on a “big” 2025, including CloudFest USA and (for Carl) WordCamp Canada and CloudFest Europe. - Zach shares his move into a partnerships role at BigScoots, highlighting how events help him “get to know other people who are my peers in the other companies in our space” and understand the hosting ecosystem better. - They compare CloudFest hackathons in Miami (one day, one project) versus Germany (three days, multiple teams plus WordPress Day plus the main conference), noting how intense and rewarding the longer format is and how much “WordPress intelligence” ends up in one room. - Carl announces an exclusive partnership between his company and BuiltFast (founded by former A2 Hosting leaders) and describes the emotional and cognitive load of self‑funded business negotiations and legal work, even when all parties are “very human” and values‑aligned. - They zoom out to WordPress itself: WordPress 6.9, a return to three major releases a year, and the Core AI team’s work integrating MCP-style AI connections into WordPress core much faster than expected, giving the platform “a leg up on the competition.” - Zach and Carl discuss “AI” as a marketing term versus precise language, likening it to “serverless has servers,” and emphasize that naming sticks even when it’s technically wrong. - Carl recounts being “pretty ahead of the curve” using Claude for code in early 2025, then seeing AI coding (and later Claude Code) rapidly normalize across hackathons and projects. They frame current LLM churn like the JavaScript ecosystem: high “creative destruction,” tools changing every few months, and the need to “find a place you’re comfortable and camp there for a while.” - They touch on evolving dev stacks (Next.js, Livewire, Alpine.js, Laravel Tall stack, Filament, Shadcn UI) as examples of constant change that both increases capability and complexity. - The conversation pivots to health: Zach shares a major decision to reverse COVID‑era weight gain and manage serious back issues, losing ~50 pounds in four months under a very aggressive protein target (280g/day) and working with a nutritionist. Carl responds with his 20‑year lifting journey, car‑accident‑related back problems, and how Stuart McGill’s book “Back Mechanic” plus exercises like “nerve flossing” and the “McGill Big Three” helped him rehab. - They stress that for back pain, “it’s much more about endurance than it is about strength,” and that excess weight and imbalanced ab‑only training can worsen problems. - Zach recounts a frightening car accident triggered by bronchitis and a coughing fit which aggravated his existing back injury, underscoring how fragile health can feel and why he’s grateful to be regaining mobility. - In the last segment they shift to gratitude and boundaries: being “very grateful” for progress in health, the ability to “choose what level of toxicity you want to allow in your life,” and learning to say no and set hard boundaries—especially as highly empathetic “empath” personalities. - Carl talks about emotional overload, hurting for other people, supporting community members like Tessa, and how protecting himself has been hard but necessary. - He expresses deep gratitude for still being self‑employed ~15 years in, for clients who stuck around despite economic strain, and for the BuiltFast partnership, which likely spared him from needing a job search—framed as the “Two Towers” middle book of an ongoing trilogy about committing to the open web. - They outline ambitions to broaden podcast guests beyond WordPress (e.g., Carl’s friend’s mom, former CIO of Canada), capture older tech histories, and acknowledge that they’re becoming the “old guard” of tech as mentors retire and new voices like Christian Taylor and Mark Zymanski arrive. - Both close with what they’re looking forward to: Carl hopes he can still be independent “next December”; Zach aims to grow in 2026—deepening partnership skills, creative expression (concert photography, writing), and, humorously, being “half the man” he is physically by the next year‑in‑review—while thanking listeners and inviting feedback, guest ideas, and complaints via the running joke hashtag “bugbob.” ### 🗒️ Notes #### ⏱️ [00:02:00](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/?t=120) CloudFest, hackathons, and partnership work - Zach and Carl recap CloudFest USA, WordCamp Canada, and CloudFest Europe; Zach uses Miami to meet hosting peers and strengthen BigScoots partnerships. - Carl explains how European CloudFest hackathons span three days with multiple teams and flow into WordPress Day and the main conference, calling a full week of hackathon+conference “massively draining” but “so good.” #### ⏱️ [00:10:00](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/?t=600) BuiltFast partnership and WordPress AI shift - Carl reveals an exclusive partnership between his product (Lemire/Vector) and BuiltFast, founded by ex‑A2 Hosting leaders, and describes the steep learning curve around negotiations and legal documents that are “there in case something happens.” - They connect this to wider WordPress shifts: 6.9, returning to three releases per year, and the WordPress AI team shipping MCP‑style LLM integration into core far faster than expected, giving WordPress “a leg up on the competition.” #### ⏱️ [00:18:00](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/?t=1080) AI as JavaScript‑like churn - Zach critiques “AI” as a marketing term, comparing it to “serverless has servers,” while Carl notes we’re stuck with catchy names once they take off. - Carl recounts being often the only one using Claude for code at events in early 2025; by Miami, everyone uses AI tools, but he’s still ahead in workflow sophistication—though many tools (e.g., Claude Code) didn’t even exist 12 months prior. - They equate AI’s rapid evolution with JavaScript’s: stacks move from jQuery to React to Next.js, while they personally favor Livewire, Alpine, Laravel Tall stack, and Filament as ways to manage complexity. #### ⏱️ [00:28:00](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/?t=1680) Health, back mechanics, and rehab - Zach shares a decisive pivot in his health: significant COVID‑era weight gain, persistent back issues, and mobility problems push him to change; he’s lost ~50 lbs in four months under a very high daily protein target. - Carl describes his own back issues after a car accident and moving snow, endorses Stuart McGill’s “Back Mechanic” as an “absolute gem” that explains biomechanics clearly, provides self‑assessments, and introduces exercises like “nerve flossing” and the “McGill Big Three” (curl‑up, side plank, bird dog). - They highlight that back recovery is about endurance and balanced core stability more than brute strength, and that weight loss materially helps by reducing overall load. #### ⏱️ [00:36:00](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/?t=2160) Gratitude, boundaries, and emotional load - Zach expresses gratitude for his improving health and mobility and emphasizes the life skill of “choosing what level of toxicity you want to allow in your life” and learning to say no, especially for empaths who default to making others feel better “sometimes to our detriment.” - Carl shares how hard it’s been to protect himself emotionally amid “so much signal coming your way,” feeling others’ pain (including community members like Tessa) and struggling not to internalize blame. #### ⏱️ [00:43:00](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/?t=2580) Indie survival, open web trilogy, and aging in tech - Carl is “immensely grateful” to have survived another year self‑employed, retaining clients where possible and gaining the BuiltFast partnership; he frames his multi‑year journey into the open web (including re‑focusing this podcast) as a Lord of the Rings‑style trilogy, with 2025 as “The Two Towers.” - They talk about broadening guests to include long‑time tech leaders (e.g., Carl’s friend’s mom, former CIO of Canada) to capture diverse histories, acknowledging they’re becoming “the boomers of tech” as mentors retire and newer folks like Christian Taylor and Mark Zymanski enter. #### ⏱️ [00:50:00](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/?t=3000) Looking forward to 2026 and closing - Asked what he’s most looking forward to, Carl says he hopes he can still say “I’m doing my stuff” next December rather than “I work for X now,” recognizing both luck and hard work in his independence. - Zach wants to “learn in 2026,” deepening partnership skills, advancing in concert photography and creative expression, and (physically) being “half the man I am today” by their next year‑in‑review. - They thank listeners, invite topic and guest suggestions, and revive the in‑joke hashtag “bugbob” for complaints, emphasizing their gratitude for having a community that makes the show possible. ## 📚 References - CloudFest: https://www.cloudfest.com/ - WordPress 6.9 release info: https://wordpress.org/news/ - WordPress Core AI / MCP discussions (example hub): https://make.wordpress.org/core/tag/ai/ - Claude & Claude Code (Anthropic): https://www.anthropic.com - Laravel: https://laravel.com - Livewire: https://livewire.laravel.com - Alpine.js: https://alpinejs.dev - Filament (Laravel admin): https://filamentphp.com - Shadcn UI: https://ui.shadcn.com - “Back Mechanic” by Stuart McGill: https://www.backfitpro.com/back-mechanic/ - Open Web / OpenChannels.fm podcast: https://openchannels.fm/ ## 🗣️ Paraphrase - The hosts look back on a demanding but rewarding 2025: intense event travel, new business partnerships, AI upheaval in WordPress, personal health challenges, and the emotional realities of being empathetic leaders in a stressed ecosystem. They connect technical shifts (AI, dev stacks) with human themes of burnout, boundaries, and gratitude. - Looking ahead, they hope for continued independence, deeper learning, better health, and a broader, more diverse set of voices on the show, while explicitly thanking listeners and inviting them into the conversation. ## 📰 Newsletter In this year‑in‑review episode of OpenChannels.fm, Zach Stepek and Carl Alexander unpack a wildly eventful 2025 across WordPress, the broader open web, and their own lives. From CloudFest hackathons in Miami and Germany to a new BuiltFast partnership around Lemire/Vector, they show how fast the ecosystem is shifting—especially with WordPress 6.9 and core AI integrations giving the project a serious “leg up on the competition.” They also touch on dev‑stack evolution (Next.js, Laravel Tall stack, Livewire, Alpine, Filament, Shadcn UI) and what it feels like to be early adopters of Claude‑powered coding as tools like Claude Code appear seemingly overnight. The real heart of the episode, though, is human: Zach’s 50‑pound weight‑loss and back‑rehab journey, Carl’s 20‑year lifting story and love of biomechanics (with a strong recommendation for Stuart McGill’s “Back Mechanic”), and an honest discussion about setting boundaries, managing empathy, and staying indie in a tough year for freelancers and product founders. If you’re in the WordPress or open web space—and especially if you juggle DevRel, indie product work, or community roles—this one’s worth a listen. You’ll come away with ideas for using AI without drowning in FOMO, practical back‑care resources, and a reminder that gratitude and good boundaries are as strategic as any new plugin. Recommended follow‑ups: - Explore WordPress core AI initiatives: https://make.wordpress.org/core/tag/ai/ - Check out Laravel + Livewire + Filament if you’re building internal tools or SaaS backends: https://laravel.com • https://livewire.laravel.com • https://filamentphp.com - For back pain and desk‑bound devs, consider McGill’s “Back Mechanic”: https://www.backfitpro.com/back-mechanic/ ## ✅ Action Items #### DevRel - Map CloudFest and WordCamp‑style hackathons into a yearly DevRel calendar, with clear goals (SDK feedback, partner integrations, case studies). - Produce AI‑assisted coding demos using Claude/Claude Code and WordPress core AI APIs; publish step‑by‑step examples and sample repos. - Create “WordPress + modern PHP stacks” tutorials (Tall stack + Filament admin) that show migration paths from older jQuery‑style sites. - Run office hours or workshops on “using AI safely in your development workflow” aimed at easing FOMO and focusing on durable practices. #### OSPO - Define guidance on AI‑generated code contributions (license compatibility, provenance, review requirements) for WordPress‑adjacent projects. - Establish or update contribution policies for AI tooling in core and plugins, including security review and prompt‑injection threat models. - Track SBOM coverage for WordPress plugins/themes, especially those bundling AI SDKs or remote services. - Integrate AI‑related security considerations (model API keys, data exfiltration) into standard OSPO training. #### Community - Use hackathons as on‑ramp experiences: design “first issue” AI + WordPress tasks with strong mentorship. - Facilitate mental‑health‑aware spaces: talks or panels on boundaries, burnout, and empathic leadership in open source communities. - Highlight stories like Carl’s indie journey and Zach’s health journey to normalize non‑linear careers and vulnerability. - Build cross‑project incident playbooks for AI‑related outages or abuses (e.g., plugin misusing LLM APIs). #### WordPress - Core: Document and evangelize the AI/MCP features in core: APIs, extension points, and security considerations. - Core Performance: Benchmark AI‑powered features’ impact on page performance and admin UX; set budgets where appropriate. - Core AI: Define responsible AI guardrails (data handling, consent, model selection, evaluation sets for prompts and responses). - Core Program Team: Align release cadence (3x per year) with AI and UX roadmap; schedule community testing windows. - Playground: Provide LLM‑ready sandboxes with sample plugins showing safe AI integrations. - Community: Encourage meetups/WordCamps to run “build with AI and WordPress” labs with clear best practices. - Training: Create learning paths on “Modern WordPress Dev + AI” with code examples and short videos. - Marketing: Tell stories of real AI + WooCommerce use cases, tempering hype with clear limits and responsibilities. - Accessibility: Audit AI‑generated content patterns for headings, alt text, and ARIA misuse. - Documentation: Maintain living docs on AI integrations, updated as tools churn (like JavaScript ecosystems). - Hosting: Publish shared checklists for hosts providing AI‑enhanced WordPress offerings (quota, rate‑limits, privacy). - Plugins/Themes: Encourage reviewers to look at AI features (data collection, model endpoints) during security checks. #### The WPOCC - Support fellowships and micro‑grants for maintainers exploring AI responsibly in WordPress (docs, governance, security). - Fund documentation and educational sprints explaining new core AI capabilities in plain language. - Pilot matched grants for cross‑CMS/open web AI tooling that remains interoperable and standards‑friendly. ### FAIR - Encourage local evaluation of AI models/tools where possible; document provenance, signing, and lifecycle commitments for AI dependencies. - Promote transparent funding and governance around AI features, with published charters and sunset clauses for experiments. - Turn governance artifacts (AI risk scorecards, data‑handling policies) into reusable templates projects can adopt. ## 🧪 Hypotheses - H1: Participating in multi‑day, focused hackathons meaningfully increases cross‑company collaboration and long‑term partnership opportunities in the WordPress ecosystem. - H2: Developers who adopt AI coding tools early (e.g., Claude/Claude Code) gain productivity initially, but perceived advantage erodes within a year as tools commoditize. - H3: Structured back‑rehab programs like those in “Back Mechanic” significantly reduce pain and improve function for knowledge workers with chronic back issues. - H4: Indie developers with strong community presence (podcasts, events, blogs) have higher resilience to economic downturns due to diversified opportunity streams. - H5: Explicit training on boundaries and emotional load improves retention and wellbeing for highly empathetic community leaders. ### 📊 Methodology - For H1: Survey and interview hackathon participants before and 6–12 months after events; measure joint projects, partnerships, and commits across org boundaries. - For H2: Longitudinal study of dev teams adopting AI tools; track velocity, defect rates, and subjective stress; compare early vs late adopters. - For H3: Randomized controlled trial comparing McGill‑style protocols vs usual care in remote workers; use validated pain/function scales over 6–12 months. - For H4: Correlational study of indie devs’ income stability vs community engagement metrics (talks, podcasts, OSS contributions) across 2023–2026. - For H5: Pilot boundary/mental‑health workshops for community organizers; pre/post metrics on burnout, turnover, and conflict incidents. ### ❓ Questions - How can WordPress core and hosting companies channel AI hype into sustainable, maintainable features rather than one‑off experiments? - What’s the right balance between in‑person hackathons and asynchronous collaboration in a post‑COVID world? - How can we better support self‑employed maintainers who are “a dying breed” without forcing them into traditional employment? - Which AI coding patterns today are likely to remain stable over 3–5 years (vs. the framework‑of‑the‑month churn seen in JavaScript)? - How do we teach boundaries and emotional self‑protection as first‑class leadership skills in open source? ### 🔮 Future Research - Long‑term impact of AI integration into CMS cores (WordPress, Drupal, etc.) on plugin/theme ecosystems and host offerings. - Comparative studies of dev‑stack longevity (e.g., Tall stack vs. full SPA frameworks) for agency/indie workloads. - Best‑practice handbooks for back health and ergonomics tailored to remote devs and open‑source contributors. - Governance models that let indie founders form partnerships without surrendering control or burning out. - Story‑collecting projects capturing “old guard” tech leaders’ experiences to inform new generations. ### 💡 Implications - Practice: Teams should treat AI like evolving JavaScript frameworks—pick a stack, document it, and revisit periodically instead of chasing every new tool. - Policy: Projects need clear rules for AI‑assisted contributions (licensing, attribution, security) to avoid downstream legal and security risks. - Security: AI integrations add new attack surfaces; hosts and plugin authors must consider prompt‑injection, data exposure, and rate limiting. - Education: Training for devs now must cover AI literacy, ergonomics, and mental health/boundaries alongside code. - Funding: Community organizations and hosts may need to underwrite key indie maintainers and governance work to keep the open web healthy. ### 🧠 Learning Styles Assessment - Reading level estimate: Around Grade 9–10 on Flesch‑Kincaid; conversational but with some technical jargon (WordPress, AI, dev‑stack terms). #### 👀 Visual learners - Present: Mental images via stories (roller coasters at Europa Park, hackathon rooms, gym work), but few concrete visuals. - Improve: Add architecture diagrams for WordPress AI flows, stack diagrams (Tall stack), and simple posture/nerve‑flossing illustrations with captions. #### 🔊 Aural learners - Present: Entire piece is an audio podcast with natural back‑and‑forth conversation. - Improve: Provide a short 3–5 minute audio “TL;DR” at the start and isolated clips for segments on AI, health, and gratitude. #### 🗣️ Verbal learners - Present: Rich analogies (AI vs JavaScript churn, LOTR trilogy), definitions in context, narrative explanations. - Improve: Include a small glossary (MCP, Tall stack, nerve flossing) and explicit compare/contrast callouts for AI tools and stacks. #### 🧩 Kinesthetic learners - Present: Descriptions of exercises (McGill Big Three, nerve flossing), hackathon participation, and personal experiments. - Improve: Offer step‑by‑step hackathon prep checklists, back‑care routines for devs, and small “try this AI coding workflow” experiments. #### 🧠 Logical learners - Present: Causal reasoning about tech evolution, AI tool adoption, and health; timelines of career and tool changes. - Improve: Add simple tables comparing stacks, timelines of AI features landing in core, and pros/cons matrices for hackathon formats. #### 🧑‍🤝‍🧑 Social learners - Present: Strong emphasis on community, events, collaborations, and empathy; podcast format fosters social context. - Improve: Provide discussion prompts for meetups, guided reflection questions for mastermind groups, and Q&A office hours. #### 🧘‍♀️ Solitary learners - Present: Zach’s and Carl’s introspective health and career reflections can prompt personal journaling. - Improve: Add explicit reflection prompts (e.g., “What boundaries do you need next year?”) and self‑check quizzes on AI comfort level. #### 🌿 Naturalistic learners - Present: Limited, mostly analogies (e.g., Black Forest, seasons/weather). - Improve: Tie open web and AI infrastructure to energy use, hardware lifecycles, and sustainable hosting; use ecosystem metaphors for communities. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Article transcript can be structured with headings and speaker labels. - Improve: Ensure headings are properly nested; identify speakers with semantic markup; add language attributes and descriptive alt text if images exist. #### Keyboard navigation - Present: Likely acceptable with basic web defaults. - Improve: Ensure the podcast page has clear focus states, skip‑links, and no focus traps in players or embedded widgets. #### Contrast and readability - Present: Depends on openchannels.fm theme; transcript text likely meets basic contrast. - Improve: Verify 4.5:1 contrast, generous line‑height, and avoid long unbroken paragraphs. #### Text resizing and reflow - Present: Site likely responsive. - Improve: Test at 200% zoom, ensure player controls reflow cleanly, and honor prefers‑reduced‑motion. #### Media and captions - Present: Full transcript is available, which is excellent. - Improve: Add downloadable transcript, clear captions/subtitles for the audio player, and optional audio descriptions for any non‑spoken content. #### Forms and interactions - Present: Basic forms (contact, subscription) likely have labels. - Improve: Use inline validation, accessible error messages, and adequate target sizes on mobile controls. #### Standards reference - Map any issues to WCAG 2.2 AA criteria (e.g., 1.4.x for contrast, 2.1.x for keyboard, 1.2.x for captions, 1.4.10 for reflow). ### 🌍 DEIB Assessment #### Cultural breadth - Present: North American/European tech conference and hosting culture; some geographic variety (Canada, Germany, Miami). - Improve: Include more global examples and guests from underrepresented regions and economies. #### Inclusive language - Present: Generally gender‑neutral and respectful; some technical jargon. - Improve: Offer plain‑language summaries around dense technical or fitness terms; avoid insider WordPress/event shorthand where possible. #### Neurodiversity support - Present: Structured conversational format with recurring themes; explicit notes on being autistic about language. - Improve: Provide clear section headings in show notes, icon+text labels for segments, and predictable release formats. #### Representation - Present: Two male hosts; mentions of women leaders (e.g., ex‑CIO of Canada, Tessa) but they’re not on‑mic here. - Improve: Bring those guests on more often, highlight diverse career paths, and choose imagery that reflects varied identities. #### Psychological safety - Present: Hosts model vulnerability around health, fear, and financial uncertainty; emphasize boundaries and empathy. - Improve: Publish community guidelines for listener interactions and clarify support/escalation paths for harassment around events. ### ✅ Logical Validity #### Strong reasoning - Inductive: Comparing AI to JavaScript framework churn is a strong analogy; both show frequent tool replacement and “creative destruction,” supporting advice to pick a stable stack for a while. - Causal: Linking weight loss and back endurance to reduced pain is consistent with biomechanics literature and McGill’s work, strengthening the recommendation to focus on endurance, not just strength. #### Fallacies - Mild survivorship bias: Carl’s successful indie path over ~15 years could be read as evidence that similar choices will work for others; addressing structural factors and luck (which he does mention) mitigates this. - Potential hasty generalization: Observations from a few events (CloudFest, Miami) might not represent all devs’ AI adoption; could be framed more explicitly as “in these circles.” #### Tone of voice - Tone is conversational, candid, and supportive. Example: gratitude and empathy segments where they admit struggles and express thanks for ongoing independence and community support, while joking lightly (“we’re kind of boomers of tech,” “bugbob”). ### 🛡️ DARVO Analysis - Deny: No evident denial or minimization of harm; they acknowledge difficulties (health, finances, burnout) directly. - Attack: No attacks on critics or accusers; when referencing technical failures (e.g., State of the Word livestream), they explicitly avoid blame and empathize with the events team. - Reverse victim/offender: None; they don’t recast themselves as victims to avoid accountability. Instead, they own their luck and privilege in still being independent, and they focus on gratitude rather than grievance. ## 🎯 Conclusion Zach and Carl’s 2025 recap weaves together three threads: rapid change in WordPress and AI, the grind and hope of indie/self‑employed careers, and deeply personal health and emotional journeys. Their message for 2026 is to keep experimenting—with AI tools, partnerships, and creative work—while fiercely guarding health, boundaries, and gratitude. For listeners, practical next steps are to choose a sane AI/dev stack, invest in body and back health, and intentionally shape communities that are both technically ambitious and emotionally sustainable. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] 5–10-word present-tense claim > [!quote] [Growth, Hackathons, and Gratitude Lessons from an Eventful 2025](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/) by [[openchannels.fm]] via [[openchannels.fm]]. Published 2025-12-09. > “It’s been a year. It’s definitely been a year.” Two lines: context and use. Cite data if relevant. [view highlight](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [Growth, Hackathons, and Gratitude Lessons from an Eventful 2025](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/) > “Losing weight’s gonna help it. Losing weight’s gonna help a lot.” Two lines: context and use. [view highlight](https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] AI adoption mirrors JavaScript framework churn - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[AI-Tooling]] [[JavaScript-Ecosystem]] #### [Z2] Back endurance improves chronic back pain - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Back-Health]] [[Knowledge-Worker-Ergonomics]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Design a “WordPress + AI without FOMO” workshop—https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/ #fleeting #inbox - [F2] Summarize McGill’s “Back Mechanic” for devs—https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/ #fleeting #inbox - [F3] Draft a blog on boundaries for empathetic community leaders—https://openchannels.fm/growth-hackathons-and-gratitude-lessons-from-an-eventful-2025/ #fleeting #inbox --- <!-- deep-read:sections end -->