Skip to content
Signalcrest
Back to feed
lobstersdevtools

Sloc Cloc and Code - Did I just get Buster Scrugged?

Go tooling highlights SLOC/Cloc metrics, revealing code-size effects on performance.

Steady
Signal score
29
as of 1d ago
Sources
2
agreeing on go
Trajectory
Too early
needs a few more snapshots

Why this scored 29

every term, weighted
Velocity+0.0 / 40

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

Acceleration+7.4 / 25

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

Cross-source spread+12.5 / 25

How many independent communities are talking about the same entity

Recency+9.5 / 10

Decays to zero over 14 days

Saturation penalty0.3 / 30

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

Composite29.1

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

Signal history

7-day window (free)
2764

Entities

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

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