Skip to content
Signalcrest
Back to feed
lobstersdevtools

Named and Optional Arguments are Awesome

Explains why Rust's named and optional arguments improve API ergonomics.

Steady
Signal score
35
as of 9h ago
Sources
3
agreeing on rust
Trajectory
Cooling
7-day est. ~19

Why this scored 35

every term, weighted
Velocity+0.0 / 40

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+10.5 / 25

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+16.7 / 25

How many independent communities are talking about the same entity

Recency+8.8 / 10

Decays to zero over 14 days

Saturation penalty1.4 / 30

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite34.5

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology

Outlook

low confidence · estimate, not a guarantee

7-day

~19

range 038

14-day

~0

range 023

30-day

~0

range 030

Signal history

7-day window (free)
1995

projected trajectory (estimate, not a guarantee)

Entities

rust
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/lob%3Axlbphk)](https://www.signalcrest.app/topic/lob%3Axlbphk)

Drop this in a README or blog post — it updates automatically as the score moves.