Rust RFCs propose features as if they already existed. Alice Ryhl, Rust for Android at Google & Tokio maintainer, on answering every question before it gets asked: “You write this doc and it has a template, and I think it's actually a pretty good template. The first section is summary, but the first important one is motivation, to explain why this feature. And then I think they have two really interesting sections: the guide level explanation and the reference level explanation. In the guide level explanation, you explain your feature as if you were writing a guide, as if the feature already existed. And in the reference level explanation, you explain your feature again as if it already existed, but as if it would be in the language reference instead of a tutorial. [Gergely: This is really interesting. Amazon does - just related to this - when they ask people to build a feature, they have a press release, like imagine if you announced this. I just love how both this and what you're saying forces you to think from a very different perspective, from how people will use this feature. And then other sections, you mentioned rationale and alternatives, prior art, future possibilities…] Yeah, so you get to explain. Rationale and alternatives, I think, is a pretty important section, because you get to answer all of the questions before they get asked. You get to explain: why did you pick this design and not some other design and I think that's usually a pretty big part of an RFC. And then of course it's good to look at what did C do, and what can we do in the future as well.”

On the contrary I think it's great that community grows and new contributors can create RFCs of such a high quality. The more important work for the core team with ai. And it takes patience to push such dramatic shifts forward.

Maybe now you'll close that arc in the next (and as you promised, last) RFCS this year

BGP never fails to ammuse me 😭😭🔥 Highly complicated and over engineered protocol 😬 ippatikiii RFCs raastuune unnaru kadara baabu 🙏🙏

Under the hood: OAuth 2.1 with mandatory PKCE, straight from the RFCs. Tokens are short-lived and audience-bound. A token minted for one server is useless anywhere else.

Also, no. RFCs are suggestions, as they are not finalized. Standards are standards. They're how protocols are defined. Yes, many places violate standards. It's up to the individual to decide if continuing to interact with whoever or whatever it is that's violating said standards is worth the risk, effort, and headache. I'm here to tell you that in 99.9% of the cases, they aren't.

Top 10 resources to learn communication for developers (practical, not fluffy): 1. The Manager’s Path (Fournier) — clear 1:1s, feedback, expectations, career ladders. 2. Crucial Conversations — how to talk when stakes are high (incidents, perf issues, deadlines). 3. Writing for Software Developers (Piotr Wozniak) — specs, emails, design docs, status updates that don’t ramble. 4. Staff Engineer (Larson) — influencing without authority, aligning teams, handling ambiguity. 5. Google Engineering Practices docs — code review wording, readability, small CLs, concrete examples. 6. GitLab Handbook (communication sections) — async habits: agendas, notes, decisions, DRIs. 7. Stripe’s writing culture (memos, RFCs, docs) — good templates and the level of detail that works. 8. Resilient Management (Lara Hogan) — hard feedback, coaching, and team communication under stress. 9. Toastmasters (or any weekly speaking group) — reps for concise updates and clear storytelling. 10. Practice project: write 3 docs per feature (RFC, runbook, postmortem) — reviewers catch vagueness fast

Just to be clear on this. IMO, a fork is not the ideal solution, it would fragment the community even more. But I do think that how some things are handled should be revisited. And I'm not saying this because of the generics RFC. Other RFCs, and even other actions and decisions, have shown the community sometimes is not on board with how things are done. If we want to make PHP more popular, and used more, we need to revisit some things.

Typst 0.15.0 (298 on HN) ships experimental HTML export — the same source file now compiles to PDF *and* semantic HTML. The interesting target isn't blogs. It's the long tail of LaTeX docs that get manually re-authored as web versions: papers, RFCs, books, internal reports. Two toolchains collapse into one. Also quietly important: content-driven `pagebreak(to:)`, PDF/A-3b archival output, and mandatory manifest fields on the package registry — the governance move you make when you're planning for 10x the packages. #typst #latex

Yeah, I don't think a fork would be good, TBH. There are valid points for sure about this generics implementation, and I'm not saying this only about this specific RFC. But there were many other RFCs that showed the PHP community gets really split in different groups.

It's no secret that the PHP RFC process itself is a problem for the language's evolution. I think everyone is aware of that. But as far as I can tell, nobody is really in a position to change it. The issue is not that RFCs are of poor quality. Rather, the RFC process itself pushes proposals to be less refined than they could otherwise be. The most appropriate solution would be a reform of the RFC process itself.

💻 Hiring: Senior Software Engineer, Wallets - Stellar 📍 San Francisco (Remote) | 💼 Full-time | 🧑‍💻 Blockchain/Wallets | 💰 $185k–$275k | 🕐 20 hours ago The Stellar Development Foundation (SDF) is hiring a Senior Software Engineer for their Wallets team. The engineer will work on products powering applications connecting end-users to the Stellar network, including Freighter and open-source libraries/services at the intersection of scale and usability. 📋 Responsibilities include: - Work on cutting-edge blockchain & finance technology. - Drive development for wallet projects from vision to implementation. - Design new functionality and developer-facing APIs. - Build/maintain scalable web services. - Identify needs and design protocols to boost developer velocity. - Engage with open-source community. - Code reviews, design discussions, performance optimization. - Author technical specifications (RFCs). 🔑 Requirements: - 5 years software development experience in collaborative teams. - Strong CS fundamentals (data structures, algorithms, distributed systems). - Proficiency in server-side languages (Go, Python, Rust, etc.). - Experience with production web services at scale. - Excellent communication and product mindset. 🛠 Nice-to-have: - Blockchain experience. - Data pipelines, open-source contributions. - Go and NodeJS. 💡 Perks & Benefits: - Top-tier health coverage, flexible PTO, parental leave, 401K match, gym reimbursement, L&D budget, retreats & more. 📩 To apply: Visit jobs.ashbyhq.com/stellar/1d2… 🔗 Original post: blockchainjobsboard.com/job/… ⚠️ DYOR! I don’t verify every job. If someone asks to run files or payment 🚩 likely a scam. ❗️ I'm not hiring myself! I just sharing fresh web3/crypto/blockchain roles DAILY for all levels! 💡 For Interns & juniors → t.me/crypto_vazima_english 💼 Mid/senior jobs → t.me/web3_jobs_crypto_vazima #Web3 #Blockchain #Hiring #CryptoJobs #Stellar #SoftwareEngineer #Wallets #Remote #Engineering #Developer

“Thank you, truly.” Words like these remind us why rural financial counselling matters and why we show up for our communities across western Victoria. #RFCS #CommunitySupport

“Thank you, truly.” Words like these remind us why rural financial counselling matters and why we show up for our communities across western Victoria. #RFCS #CommunitySupport 🫂

I totally agree, the real skill is knowing when a microservice isn’t the answer. I’ve seen great coders flounder without that cost‑aware mindset. Writing clear RFCs and mentoring without ego is what turns a coder into a leader.

found skill to review specifications, protocols, proposals, adrs, rfcs - "structural-transformation-review"

What most Backend developers miss when trying to become senior: ⇥ Knowing when NOT to use microservices ⇥ Trade-off analysis (the real senior skill) ⇥ Cost-aware architecture ⇥ Incident response & postmortems ⇥ Building tools that multiply team output ⇥ Writing clear RFCs and architecture docs ⇥ Mentoring without ego Technical skills get you to senior. These get you respected as senior. 🔖Bookmark this one.