SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Quote Comparisons Need an Equivalence Policy Beyond Normalization

0
·7 views

The article argues that sorting supplier offers by price is straightforward, but establishing what each price actually covers requires a clear policy. Different units, specifications, delivery terms, or validity periods can make offers look comparable when they are not. The author distinguishes normalization, which standardizes data for easier comparison, from equivalence, which judges whether an offer meets the approved need. A fictional mounting-kit example illustrates how a lower headline price can still be ineligible when components or delivery conditions are unclear. The piece recommends recording required attributes, permitted transformations, and review conditions, along with versioned policies and frozen comparison snapshots.

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 ·

AI Reshapes Job Titles and Work Methods, Shifting Value Toward Engineering Judgment

An opinion piece argues that artificial intelligence is changing both job titles and the way work gets done across industries. It contends that AI tools are now widely accessible, so the key differentiator is how users apply them, including their methodology and ability to steer the tools toward useful results. In software development, the author says writing code is becoming a cheap, routine step, with value moving toward engineers who understand the broader discipline and can guide AI toward real-world solutions. The piece notes that AI also creates new roles, citing examples such as prompt engineering, RAG engineering, agentic AI engineering, Chief AI Officer, and AI business translator. It concludes that people who resist adaptation risk falling behind, and that thoughtful, moderate adoption of AI can strengthen skills and professional capabilities.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why coding agents turn CRLF files into whole-file diffs, and what Codex 0.162 changed

Coding agents that rewrite a Windows file with LF line endings can make git report every line as changed, even when only one word was edited. This happens because git stores the committed CRLF bytes, and the rewrite adds an invisible difference to each line. Developers have reported the problem with Claude Code, and Codex CLI's 0.162.0 release now preserves existing CRLF endings in its patch updates. The article includes a reproducible git demo showing that one changed word produces three deletions and three insertions. It explains how core.autocrlf and text attributes in .gitattributes decide where conversion occurs, and why files already committed with CRLF can escape normalization.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

GraphGuard Uses a Graph Database to Link Security Alerts Into Attack Stories

Security teams often face alert fatigue because tools display each alert as an isolated record that hides its connections to other events. The author argues that security data is naturally a graph, so the context needed to spot attacks lies in relationships between users, devices, IP addresses, and incidents. GraphGuard uses FalkorDB, a graph-native database, as the backbone for an AI investigation agent that traverses these connections quickly. The system stores investigations and evidence as persistent nodes, allowing the agent to recall past cases across sessions. The model is built from eight node types and ten relationship types, seeded with three realistic attack scenarios.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Remote-support session logs must leave the appliance to survive a rebuild, experts say

Remote-support sessions are recorded mainly to document changes made during maintenance, but appliance-local logs sit on an encrypted partition and are not centralised unless forwarding is configured. CISA advises forwarding appliance syslog and session events to a SIEM immediately, along with web application firewall, reverse proxy and perimeter firewall logs covering the exposure window. The article stresses that usable records must leave the appliance, be time-synchronised with other systems, and be retained beyond the appliance's lifecycle. It also highlights that missing sessions can signal altered logging, not just inactivity. Mandiant warns that intervals between intrusion and discovery in the BeyondTrust case were measured in weeks, and additional organisations may have been compromised before disclosure.

0 comments Read more at DEV Community