More ideas to convey "ideal" posts

[EdmundsEcho]

Rough draft (early morning stream of thought inspired by the twitter post and early examples)...

• Error design by the reqwest team
• Error design by the axom team
• Error design by fill-in the blank of a more traditional "lib" (i.e., does not require a runtime; nor is a bin)

In this case: the topic overlap is by design while the approaches unique; each are effective at solving the problem.

Process for nominating similar "sources" of "how to use Rust": the successful nomination then serves as fodder for writing the post as envisioned (i.e., avoid hinging on required participation from original contributors).

Sources of coherence between otherwise wide range of posts:

• how it reduces cognitive load for the end user; whilst encouraging/represents "best use of rust"

• manages complexity, vs reduces boilerplate, vs both

• isolates/focuses user to critical decisions that remain: i.e., scope of the remaining bounds of the abstraction

• use of the type system, conventions and the borrow-checker to solve a problem (likely by simplifying design process for end user)

• type reuse (e.g., axum); minimize need to learn "yet another abstraction" or "limited incremental abstractions" to an important and useful "essence" of the task

All in all, some sort of framework that gets us to concrete topics such as working with the borrow-checker, proactive consideration of lifetimes, code-reuse in a strongly typed system (the duality of what that means; net solution that introduces new tensions that require a new mix of design proficiencies); best use of rust ~ aligns with core rust principals.