PHP Alive and Kicking Episode 34 — Derick Rethans

PHP Alive and Kicking: Episode 34 — Derick Rethans ![rw-book-cover](https://i.ytimg.com/vi/JXW9Z8uKvQM/maxresdefault.jpg) 🔗 **Source:** [PHP Alive and Kicking: Episode 34 — Derick Rethans](https://www.youtube.com/watch?v=JXW9Z8uKvQM) > [!note]+ Document Notes > tags: [php, php-internals, open-source-maintenance, xdebug, language-governance, developer-community] > author: PHP Architect; guest Derick Rethans > source: PHP Architect YouTube channel > reference: https://www.youtube.com/watch?v=JXW9Z8uKvQM > date created: 2026-08-04 22:20 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: PHP Alive And Kicking: Episode 34 — Derick Rethans >  ## 🧭 Table of Contents - [Summary](#-summary) - [Main Content](#-main-content) - [Notes](#-notes) - [References](#-references-1) - [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) - [Refactor Appendix](#-refactor-appendix--php-alive-and-kicking-episode-34--derick-rethans) ### 🔗 References - [Video on YouTube](https://www.youtube.com/watch?v=JXW9Z8uKvQM) - [PHP project](https://www.php.net/) - [PHP Foundation](https://thephp.foundation/) - [Xdebug](https://xdebug.org/) ## 📝 Summary - **What happened:** PHP Architect hosts Derick Rethans for a wide-ranging conversation about PHP 8.6, Xdebug, deprecations, project infrastructure, documentation, governance, and contributor succession. - **Why it matters:** The episode shows that language stewardship is mostly maintenance work: triage, compatibility analysis, infrastructure renewal, documentation ownership, review, and trust-building. - **Stakeholders:** PHP users, internals contributors, extension authors, framework maintainers, infrastructure operators, educators, employers, and open-source funders. - **Risks and tradeoffs:** The recording is conversational and sometimes speculative. Feature status, vote counts, pricing, and release plans reflect 2026-08-04 and need current primary-source verification. The transcript was recovered locally because no platform captions existed, so names and technical terms may contain recognition errors. - **Bottom line:** Mature open-source systems survive when routine maintenance becomes visible, entry-level contribution remains possible, compatibility claims use ecosystem evidence, and critical access grows through review rather than instant trust. ## 📖 Main Content - Rethans traces his early PHP work through bug reproduction and triage, noting that neglected queues produce large issue and pull-request backlogs. - PHP 8.6 discussion covers a duration value, partial function application, polling and stream APIs, TLS session resumption, and longer-term streams modernization. - The PHP Foundation ambassador effort joins research, speaking, and marketing with planned work on php.net and clearer separation of core versus third-party documentation. - Xdebug work includes native path mapping, compatibility with PHP 8.6, more accurate code coverage, and Xdebug Cloud for remote debugging. - Deprecations should have a clear benefit, assess real ecosystem use, and support future language work; deletion by itself is not maintenance value. - PHP infrastructure is moving from individually maintained servers toward configuration-managed systems, while CDN defaults exposed cache-duration and query-key surprises. - New contributors can begin with report validation and issue triage, then build deeper knowledge and trust through review. ## 🗒️ Notes #### ⏱️ [07:36](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=456) Early contribution and triage - Rethans describes an early PHP patch for detecting Shockwave Flash and years spent reproducing and fixing issue reports. - The conversation treats triage as important, time-consuming maintenance that can be started without deep internals expertise. #### ⏱️ [10:45](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=645) Date and duration semantics - Calendar operations are domain decisions: “add a month” and “go to next month” are not identical. - The duration work is positioned as a smaller API step that supports polling, sleeping, and future time interfaces. #### ⏱️ [14:22](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=862) PHP 8.6 features - Partial function application can make pipe-operator use less closure-heavy. - TLS session resumption can reduce repeated connection setup; streams modernization is broader than one release cycle. #### ⏱️ [19:36](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=1176) Website, documentation, and ambassadors - Old php.net structure complicates change, while the Foundation's research, speaking, and marketing streams aim to explain who uses PHP and why it matters. - The documentation project is clarifying which extensions belong to PHP core and which are maintained elsewhere. #### ⏱️ [27:36](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=1656) Xdebug direction - Native path mapping moves remote/local mappings into Xdebug configuration. - A proposed coverage implementation favors more accurate results at roughly a reported ten-percent extra cost on an already expensive operation. - Path and branch coverage can reveal gaps that line coverage misses, but exhaustive branching can become combinatorial. #### ⏱️ [37:51](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=2271) Deprecation governance - Rethans asks for an impact-to-benefit case before removing old functions or syntax. - Ecosystem scans need transitive dependency awareness, not only direct use in the top repositories. - Voting originally confirmed an emerging consensus; a close vote signals that consensus is weak. #### ⏱️ [47:43](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=2863) Infrastructure and CDN migration - Configuration management reduces the operating-system and ownership drift of individually maintained servers. - New CDN defaults around month-long caching and query-string exclusion required explicit correction and invalidation work. #### ⏱️ [53:35](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=3215) Contributor succession - Marketing and research help show that PHP is active, but contribution paths must make everyday language improvement feel possible. - Triage offers an accessible starting point; security and infrastructure require gradual trust because access cannot be open by default. - The closing bus-factor discussion recognizes that one or two maintainers cannot provide durable coverage. ## 📚 References - [PHP 8.6 release information](https://www.php.net/releases/8.6/en.php) — verify current release state and shipped features. - [PHP RFC index](https://wiki.php.net/rfc) — verify individual proposals, votes, and deprecations. - [PHP Foundation](https://thephp.foundation/) — verify ambassador and funding programs. - [Xdebug documentation](https://xdebug.org/docs/) — verify path mapping, coverage, Cloud, and compatibility details. - [Original episode](https://www.youtube.com/watch?v=JXW9Z8uKvQM) — primary audiovisual source used here. ## 🗣️ Paraphrase 1. Rethans entered PHP through concrete bug work and argues that reproducing and sorting reports remains central to project health. 2. Date and time APIs expose ambiguous human concepts, so new interfaces must encode intent without breaking existing programs. 3. PHP 8.6 contains several focused additions while deeper streams work needs more than one release cycle. 4. Project websites and documentation also age; modernizing them is both technical work and a way to explain PHP's value. 5. Xdebug development balances correctness, speed, compatibility, and the practical realities of remote teams. 6. Deprecations deserve evidence that removal helps the language or unlocks future work and does not impose needless migration costs. 7. Standardized infrastructure improves maintainability, but provider defaults must be tested against release and cache behavior. 8. Contributor succession grows from approachable work, welcoming discussion, bounded permissions, dependable review, and reduced bus factor. ## 📰 Newsletter PHP may be 31 years old, but this episode sounds less like a retirement party and more like a maintainer stand-up with biscuits. Derick Rethans connects PHP 8.6 features, Xdebug accuracy, deprecation discipline, CDN surprises, and contributor onboarding through one theme: mature projects run on patient maintenance. WordPress teams should recognize the landscape—large queues, compatibility promises, old infrastructure, and the need to turn “someone should help” into a reviewed contribution path. [Watch the episode](https://www.youtube.com/watch?v=JXW9Z8uKvQM) and verify release details against the [PHP RFC index](https://wiki.php.net/rfc). ## ✅ Action Items #### DevRel - Publish a PHP 8.6 feature map that marks proposal, accepted, shipped, and independently tested states separately. - Run an office hour on issue reproduction and triage as a first contribution. #### OSPO - Fund maintenance queues, infrastructure succession, and security review as named work rather than invisible overhead. - Define staged access for sensitive systems with mentoring, audit trails, and backup ownership. #### Community - Pair newcomers with maintainers on report validation, minimal reproductions, and documentation fixes. - Track review latency and bus factor without blaming individual maintainers. #### WordPress #### Core - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Core Performance - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Core AI - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Core Program Team - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Mobile - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Playground - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Community - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Training - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Marketing - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Support - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Design - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Documentation - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Photos - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### TV - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Polyglots - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Accessibility - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Meta - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### CLI - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Hosting - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Tide - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Openverse - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Themes - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### Plugins - Apply the episode's maintenance, evidence, onboarding, and succession lessons to this team's contribution workflow; record a small measurable improvement. #### The WPOCC - Support cross-project maintainer apprenticeships, triage stipends, and portable infrastructure runbooks. #### FAIR - Keep governance evidence, dependency impact, and operator responsibilities inspectable before ecosystem-wide compatibility changes. ## 🧪 Hypotheses - A weekly triage rotation reduces the median age of actionable PHP reports without increasing maintainer rework. - Deprecation proposals with transitive ecosystem scans receive fewer late compatibility objections. - Configuration-managed infrastructure reduces recovery time when an original operator leaves. - First contributions framed as report validation produce more returning contributors than code-only starter issues. - Path and branch coverage find defects that line coverage alone misses in high-risk change sets. ## 📊 Methodology - Sample PHP issue and pull-request queues before and after a documented triage rotation; measure age, duplicate rate, reproduction quality, and review time. - For proposed deprecations, scan direct and transitive dependencies across a reproducible package corpus and publish false-negative limits. - Exercise CDN behavior with exact expected-state tests for cache duration, query keys, invalidation, pre-release pages, and geographic nodes. - Compare line-only and path/branch coverage on the same seeded defects; record runtime and detection rate. - Survey contributors at first contact and 90 days later to compare onboarding paths and retention. ## ❓ Questions - Which PHP 8.6 features were accepted and shipped after this recording? - What minimum evidence should every deprecation RFC include about ecosystem use? - How can security and infrastructure teams add apprentices without exposing sensitive systems prematurely? - Which php.net and documentation tasks offer the best newcomer path? - What bus-factor target is realistic for each critical PHP service? ## 🔮 Future Research - Audit feature claims against the final PHP 8.6 release and RFC vote records. - Map maintainer concentration across PHP core, documentation, infrastructure, Xdebug, and security response. - Study whether ambassador programs change contributor conversion, not only public awareness. - Test cache and release workflows under CDN failure and stale-edge conditions. - Compare contributor onboarding across PHP, WordPress, Python, and other mature language communities. ## 💡 Implications - **Practice:** Treat triage, review, documentation, and operations as first-class engineering output. - **Policy:** Require impact evidence and migration plans for removals that affect a large dependency graph. - **Security:** Use staged trust, least privilege, review, and backup operators for sensitive systems. - **Education:** Teach report validation and reproduction before assuming contributors must write language internals. - **Funding:** Pay for maintenance, succession, and infrastructure work whose value appears mainly when it prevents failure. ## 🧠 Learning Styles Assessment - **Reading level estimate:** Flesch-Kincaid Grade 10–12 by structural estimate; an exact score is inappropriate because the source is an automatically transcribed conversation. #### 👀 Visual learners - Present: the video may contain speaker and screen visuals, but this text pass did not audit every frame. Improve with a release-feature map and infrastructure diagram. #### 🔊 Aural learners - Present: the original hour-long conversation is the source. Improve with chapter markers and a five-minute audio recap. #### 🗣️ Verbal learners - Present: examples, analogies, humor, and repeated restatement. Improve with a glossary correcting transcript recognition of PHP terms. #### 🧩 Kinesthetic learners - Present: practical ideas about triage, coverage, and infrastructure. Improve with a report-reproduction lab and cache test fixture. #### 🧠 Logical learners - Present: tradeoff reasoning about compatibility, correctness, consensus, and cost. Improve with decision tables and benchmark results. #### 🧑‍🤝‍🧑 Social learners - Present: multi-host discussion and community examples. Improve with facilitated RFC and triage exercises. #### 🧘‍♀️ Solitary learners - Present: timestamped transcript supports self-paced review. Improve with reflection prompts and a self-check quiz. #### 🌿 Naturalistic learners - Present: not applicable to the main subject. Improve by adding compute, infrastructure lifecycle, and energy considerations to operational choices. ## 📊 Accessibility Assessment #### Screen reader semantics - The recovered Reader version uses headings, paragraphs, and timestamp links. Verify player labels and heading order against WCAG 1.3.1 and 2.4.6. #### Keyboard navigation - The YouTube player was not audited. Test keyboard operation, focus visibility, and bypass behavior under WCAG 2.1.1, 2.4.1, and 2.4.7. #### Contrast and readability - Visual contrast was not audited. Test player controls, captions, and linked text under WCAG 1.4.3 and 1.4.11. #### Text resizing and reflow - Reader text should reflow, but the source page was not tested at 200% zoom or 320 CSS pixels. Apply WCAG 1.4.4 and 1.4.10. #### Media and captions - YouTube and vidIQ supplied no captions. A local transcript was recovered, but automatic recognition needs human correction. This is a major gap under WCAG 1.2.2 and related media criteria. #### Forms and interactions - Comments and player controls were not audited. Test labels, status messages, and target sizes under WCAG 3.3.x, 4.1.2, 4.1.3, and 2.5.8. #### Standards reference - This is a content assessment, not a WCAG 2.2 AA conformance audit. ## 🌍 DEIB Assessment #### Cultural breadth - The hosts and guest draw mainly on UK, Dutch, and PHP-internals experience; wider geographic contributor constraints are not explored. #### Inclusive language - The tone is informal and generally welcoming, though dense insider terminology can exclude newcomers. #### Neurodiversity support - Humor and tangents make the conversation personable but harder to scan. Chapters, corrected captions, and concise recaps would help. #### Representation - The episode centers established maintainers and does not include newer contributors describing their own barriers. #### Psychological safety - The speakers normalize mistakes and reviewed contributions, though joking labels such as “stupid idea” can discourage people when removed from the friendly context. ## ✅ Logical Validity #### Strong reasoning - Rethans uses concrete maintenance mechanisms: neglected triage creates backlogs, diverse infrastructure creates ownership risk, and hidden CDN defaults create stale release behavior. - The deprecation argument distinguishes removal cost from future-language benefit and asks for usage evidence. - The onboarding argument correctly separates low-risk report validation from sensitive infrastructure and security access. #### Fallacies - **Hasty generalization:** individual experiences with users, queues, and infrastructure sometimes stand in for broad ecosystem behavior. Fix with queue data, surveys, and published incident evidence. - **Appeal to anecdote:** Xdebug performance and onboarding recommendations rely largely on practitioner experience. Fix with repeatable benchmarks and retention studies. - **False precision risk:** reported percentages, vote counts, prices, and versions can be misread as current facts. Fix by dating each claim and linking primary records. #### Tone of voice - Collegial, humorous, technically candid, and maintenance-oriented, with frequent tangents typical of a live podcast. ## 🛡️ DARVO Analysis - Not applicable to this source. The speakers discuss technical disagreements and project constraints without denying reported harm, attacking complainants, or reversing victim and offender roles. ## 🎯 Conclusion - PHP's continued health depends as much on triage, evidence, infrastructure, documentation, review, and succession as on new syntax. - Next: verify final PHP 8.6 state, correct the automatic transcript, identify one approachable triage task, and document one critical service's backup owner. ## 🔄 Refactor Appendix — PHP Alive And Kicking: Episode 34 — Derick Rethans ### 📚 Literature Atoms (H3) ### [H1] Open-source health depends on sustained triage, not only feature development. > [!quote] ID:rw_01kz7vdprw21x94xkxx5hh4yx9 > there was over 900 issues, **Context & use**: - Timestamp: [09:37](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=577) - Why: Open-source health depends on sustained triage, not only feature development. **Tags**: #xref **Highlight**: [view highlight](https://read.readwise.io/read/01kz7vdprw21x94xkxx5hh4yx9)  ### [H2] Backward-compatibility decisions need ecosystem evidence and a stated benefit. > [!quote] ID:rw_01kz7vdnpgc3xcgkvkfcd7571t > I think you need to have a very good reason for removing something. **Context & use**: - Timestamp: [46:12](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=2772) - Why: Backward-compatibility decisions need ecosystem evidence and a stated benefit. **Tags**: #xref **Highlight**: [view highlight](https://read.readwise.io/read/01kz7vdnpgc3xcgkvkfcd7571t)  ### [H3] Correct diagnostic output can justify measured performance cost. > [!quote] ID:rw_01kz7vdwysgqh085yq8fb7bd19 > I prefer correct output over quick output. **Context & use**: - Timestamp: [30:10](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=1810) - Why: Correct diagnostic output can justify measured performance cost. **Tags**: #xref **Highlight**: [view highlight](https://read.readwise.io/read/01kz7vdwysgqh085yq8fb7bd19)  ### [H4] Infrastructure modernization must surface hidden defaults such as cache keys and expiry. > [!quote] ID:rw_01kz7vdzzs1x4hatr2yjy2b7c1 > ancestral-based infrastructure repository to maintain all these services. **Context & use**: - Timestamp: [48:46](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=2926) - Why: Infrastructure modernization must surface hidden defaults such as cache keys and expiry. **Tags**: #xref **Highlight**: [view highlight](https://read.readwise.io/read/01kz7vdzzs1x4hatr2yjy2b7c1)  ### [H5] Contributor growth starts with accessible work and expands trust through review. > [!quote] ID:rw_01kz7vdtsxbt2f9fr150jcsrm7 > you don't need to know the internals so deep for that **Context & use**: - Timestamp: [61:43](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=3703) - Why: Contributor growth starts with accessible work and expands trust through review. **Tags**: #xref **Highlight**: [view highlight](https://read.readwise.io/read/01kz7vdtsxbt2f9fr150jcsrm7)  ### 🧠 Permanent Candidates (H4) #### [P1] Maintenance queues reveal project capacity **Claim:** A growing issue queue is operational evidence that a project lacks enough sustained triage capacity. **Evidence pointer:** [[#H1]] **Scope & conditions:** Holds when the queue is categorized by actionability and age; breaks when counts include closed, duplicated, or intentionally deferred work. **Links:** - [[Open-source maintenance]] — because extends invisible work into measurable project health. - [[WordPress contribution queues]] — because applies-in Core, documentation, and plugin review work. - [[Feature velocity]] — because contrasts new delivery with maintenance capacity.  #### [P2] Removal requires a positive compatibility case **Claim:** A deprecation deserves adoption evidence and a concrete future benefit before it transfers cost to users. **Evidence pointer:** [[#H2]] **Scope & conditions:** Applies to mature ecosystems with long compatibility promises; exceptions may exist for urgent security or correctness hazards. **Links:** - [[Backward compatibility]] — because extends evidence-based migration policy. - [[PHP RFC governance]] — because applies-in language voting and proposal review. - [[Dependency impact analysis]] — because evidence-for measuring transitive use.  ### ✏️ Fleeting Queue - [F1] Compare PHP and WordPress approaches to triage, consensus, and deprecation evidence — https://www.youtube.com/watch?v=JXW9Z8uKvQM #fleeting #inbox - [F2] Correct Xdebug and PHP names in the local Whisper transcript before quoting publicly — https://www.youtube.com/watch?v=JXW9Z8uKvQM #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Verify the episode's PHP 8.6 claims against final RFC and release records #things - [ ] Identify one reproducible PHP issue that can be triaged without sensitive access #things  📄 **Full text:** [[Full Document Contents/Articles/PHP Alive and Kicking Episode 34 — Derick Rethans.md|PHP Alive and Kicking: Episode 34 — Derick Rethans by PHP Architect; guest Derick Rethans]] ## Highlights - [[09:37]](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=577) getting back on top of the backlogs that last time I looked, there was over 900 issues, ([View Highlight](https://read.readwise.io/read/01kz7vdprw21x94xkxx5hh4yx9)) - Note: Open-source health depends on sustained triage, not only feature development. - Tags: php, open-source-maintenance, atom/literature/h1 - [[30:10]](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=1810) I will regard this because I prefer correct output over quick output. Yeah, and I suppose it depends ([View Highlight](https://read.readwise.io/read/01kz7vdwysgqh085yq8fb7bd19)) - Note: Correct diagnostic output can justify measured performance cost. - Tags: atom/literature/h3, open-source-maintenance, php - [[46:12]](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=2772) I don't like that. I think you need to have a very good reason for removing something. ([View Highlight](https://read.readwise.io/read/01kz7vdnpgc3xcgkvkfcd7571t)) - Note: Backward-compatibility decisions need ecosystem evidence and a stated benefit. - Tags: atom/literature/h2, open-source-maintenance, php - [[48:46]](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=2926) ancestral-based infrastructure repository to maintain all these services. So everything is now ([View Highlight](https://read.readwise.io/read/01kz7vdzzs1x4hatr2yjy2b7c1)) - Note: Infrastructure modernization must surface hidden defaults such as cache keys and expiry. - Tags: atom/literature/h3, open-source-maintenance, php - [[62:02]](https://www.youtube.com/watch?v=JXW9Z8uKvQM&t=3722) you don't need to know the internals so deep for that. But as I said, with this help sometimes. ([View Highlight](https://read.readwise.io/read/01kz7vdtsxbt2f9fr150jcsrm7)) - Note: Contributor growth starts with accessible work and expands trust through review. - Tags: atom/literature/h3, open-source-maintenance, php