SShortSingh.
Back to feed

Preserving the Evidence Behind Procurement Decisions, Not Just the Working Comparison

0
·7 views

A supplier comparison changes over time as revised offers, quantities, and delivery terms come in, so the working document must stay flexible. The decision record, however, needs to capture exactly what was compared when the choice was made. The article describes an anonymized procurement design that separates the original supplier document, its normalized interpretation, the working comparison, and a frozen decision snapshot. Using an invented example, it shows how a per-pack price and a per-unit price can be misleading without an equivalence rule covering specification, unit, and conditions. The author argues that snapshots should be taken at the point a human acts on a comparison, with later corrections recorded as amendments rather than silent rewrites. The piece makes no claims about measured savings or new deployments.

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 ·

Context Engineering: Treating the Model's Input as a Budget to Design

As context windows expanded to hundreds of thousands of tokens, developers shifted from crafting one perfect prompt to deliberately managing everything a model receives. This covers system instructions, retrieved documents, tool outputs, conversation history, and persistent memory. The article warns that stuffing a large window with irrelevant material dilutes attention and can reduce accuracy even when the needed information is present. It recommends selecting relevant retrieved chunks instead of full documents, pruning accumulated tool output and history in long agent loops, and keeping memory curated. The guidance is aimed at builders of retrieval-augmented generation systems and agents beyond the demo stage.

0
ProgrammingDEV Community ·

Turkey's Pardus Linux: History and Philosophy of a Homegrown Open-Source OS

Pardus is a Linux-based operating system distribution developed in Turkey and built on free and open-source software principles. Its goals include meeting user needs, promoting open-source use, and reducing the country's dependence on foreign technology. The system is widely used in public institutions and schools, including on interactive whiteboards. Its name comes from the scientific name of the Anatolian leopard, giving the project a local identity. Development began in 2003 at TÜBİTAK's BİLGEM research center, with the decision made to create a GPL-licensed Linux distribution, and implementation started in early 2004 under UEKAE.

0
ProgrammingDEV Community ·

Mirra: A Telegram Bot That Adds Light Activities to Couple and Family Chats

A developer has built Mirra, a Telegram bot aimed at couples, families and friends who want more shared fun within their existing chats. It offers conversation starters and small joint activities, such as a question answered privately and revealed together, or families collecting memories and photos into a shared chronicle. Couples start the bot in a private chat and invite a partner by link, while family mode runs inside a group chat. The core features are free, with optional paid extras, and the couple and family features are available in English, while the friends mode is still being translated beyond Russian. The developer is seeking feedback on whether the partner invitation and family group setup are clear.

0
ProgrammingDEV Community ·

Merging Order Books Across 25 Exchanges Reveals Walls Single Venues Hide

A trader describes repeatedly losing trades to price levels that looked strong on one exchange but were minor across the market. By summing order books from roughly 20 to 25 venues, including gold markets, after normalizing contract sizes and price grids, they found that a single exchange often held only a fraction of total liquidity. The process proved technically demanding due to inconsistent contract units, slightly different prices across platforms, and constant WebSocket maintenance. The trader now checks aggregated depth between entry and stop or target levels, and watches liquidation clusters before trading. The author also promotes their own aggregation site, AggPro.