SShortSingh.
Back to feed

Why the Metric You Track at Work May Not Reflect the Value You Create

0
·23 views

A North Star Metric is defined as a single number representing value actually delivered, yet most people default to tracking activity-based numbers that are easier to count and rise more reliably. Using job searching as an illustration, the article contrasts shallow metrics like applications sent or hours spent with more meaningful ones like interviews earned from roles a candidate would genuinely accept. Each step away from raw activity and toward outcomes better captures whether real progress is being made, but outcome metrics can stay flat for weeks even during periods of hard work. The same pattern applies in professional settings, where tickets closed or commits pushed say nothing about whether anything meaningfully improved for users. The piece also warns that any single metric can be gamed unintentionally, making a counterbalancing guardrail metric necessary to keep the primary measure honest.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Claude Fable 5.2 Tops Dual-Arm Robotics Benchmark Without Task-Specific Training

Anthropic's general-purpose model Claude Fable 5.2 reportedly scored a 64.9% average success rate on the RoboDojo dual-arm manipulation benchmark, up from 27.6% for its predecessor and ahead of Opus 5.5 and GPT-6 Astra. Rather than relying on a dedicated robot policy, the model plans actions directly from camera input, reasoning about the scene and adjusting when grips slip or objects shift. Official real-robot demonstrations reportedly included solving a Rubik's cube, unscrewing a bottle cap, and drawing with a pen, none of which the model was specifically trained on. The company also says the model handled hardware design tasks, producing PCB layouts, enclosure models and firmware for three working devices. The benchmark is simulated, and the model depends on clear visual input and existing robot controllers for low-level motor control.

0
ProgrammingDEV Community ·

Connector Engineering Ch.05 Explores Waterproofing Design for Interface Seals

This chapter from the STATERA Library's Connector Engineering series examines how interface seals keep water, dust, and contaminants out of connectors at the boundary where housings meet. It explains that effective sealing relies on controlled, continuous compression of an elastomeric gasket rather than on rubber alone, since both insufficient and excessive compression cause problems. The text covers how seal cross-section, elastomer choice such as silicone, EPDM, or fluoroelastomers, and hardness affect performance under environmental and mechanical conditions. It also stresses that housing geometry, mold quality, and tolerance stack-up must be designed together with the seal to maintain adequate pressure across the full range of manufacturing variation.

0
ProgrammingDEV Community ·

IP Code Explained: Dust and Water Ratings for Connector Environmental Protection

The IP Code, defined by IEC 60529, classifies enclosure protection against hazardous parts, solid objects, and water ingress, offering engineers a shared vocabulary for connector specification. Its two numerals rate solid-particle and water protection separately, so they must be assessed independently rather than merged into one durability score. The first digit covers access restriction and dust exclusion, with IP5X permitting limited non-interfering dust and IP6X requiring a dust-tight design. The second digit addresses water exposure, ranging from dripping and spraying to jets, temporary immersion, and continuous immersion. The article notes that ratings such as IP67 and IP68 carry specific test conditions, so engineers should verify declared depth, duration, and configuration rather than relying on the marking alone.

0
ProgrammingDEV Community ·

D-Bus Policy Governs Messages, Not the Authorization Logic Behind Them

D-Bus is widely used for local service communication on desktops and increasingly in embedded and administrative systems. Its bus daemon policy decides which messages are delivered, but it cannot judge whether a receiving method performs a safe operation. The article argues that a narrow policy still depends on the service exposing a narrow API, and that applications must enforce their own authorization after receiving a message. It recommends inventorying exported interfaces, separating system and session bus trust domains, and treating policy files as reviewable configuration. The author also notes that signals can leak sensitive data, so services should limit what they emit.