SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

How the ISBN System Shaped Book Publishing Since 1970

0
·2 views

The International Standard Book Number (ISBN) was introduced in 1970 as a universal system to identify and catalog books. The system was designed to streamline book distribution, retail, and library management across the publishing industry. Despite its widespread adoption by publishers and booksellers, individual books themselves are indifferent to whether they carry such identifiers. The article explores the history and practical significance of ISBNs in modern publishing. It raises questions about how metadata systems like ISBNs serve human organizational needs rather than any inherent property of the books themselves.

Read the full story at Hacker News

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 ·

flutter_modifier_ui tackles Flutter's widget nesting and performance issues

Flutter's composable widget system often leads to deeply nested code structures, nicknamed 'pyramids of doom,' which cause costly rebuilds when parent states change. The open-source package flutter_modifier_ui addresses this by replacing nested widget trees with a linear, chainable modifier API that improves code readability. It also introduces compile-time scope guards that prevent common runtime layout errors, such as using Expanded outside a Flex container. For performance, the package uses structural caching to skip redundant layout recompilation when properties are unchanged, and a widget teleportation mechanism to update only dynamic content without redrawing static layout nodes. Developers can integrate the package by adding flutter_modifier_ui to their pubspec.yaml and accessing full documentation on pub.dev.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why Email Unsubscribes Often Fail and How to Verify They Actually Worked

Clicking unsubscribe only sends a request to a sender — it does not guarantee emails will stop. In the US, CAN-SPAM law gives senders up to ten business days to honour opt-outs, meaning mail can legitimately continue arriving even after a valid request. To confirm compliance, users can log the sender's address and unsubscribe date, then run a targeted Gmail search two weeks later to check for continued delivery. Spam folders must be searched separately, as standard Gmail searches exclude them, which can create a false impression that a sender has complied. Seasonal senders and list resales further complicate verification, making periodic re-checks necessary rather than a one-time confirmation.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Engineer tests AI agent on real DevOps tasks, finds useful but unreliable results

A software engineer spent several months assigning real DevOps work to Claude Code, an AI agent, across eight distinct tasks including CI log analysis, on-call response, and pull request review. A key finding was that the same PR reviewed twice by the AI produced different and sometimes contradictory verdicts, highlighting the tool's non-deterministic nature. The engineer concluded that AI agents should act as advisory reviewers only, never as gatekeepers with merge or deploy rights. Strict constraints proved essential to safe usage: the agent was limited to file edits and draft PRs, barred from committing to main, and restricted to a single attempt per failure. The overall takeaway was that AI is genuinely useful for repetitive, low-stakes DevOps toil, but human oversight and hard guardrails remain non-negotiable.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer builds zero-dependency crash-safe key-value store in Rust, exposes benchmark flaws

A developer built StoneKV, a crash-safe, log-structured embedded key-value store written entirely in Rust with no external dependencies, as an entry for Track D of the Zero Dependency Hackathon. The project's core design revolves around a single durability guarantee: once a write operation returns successfully, the data has been appended to a write-ahead log and fully synced to disk. The developer focused heavily on adversarial testing, uncovering edge cases including a deleted key that could resurrect after a crash and a benchmark figure that appeared impressive but was later found to be inaccurate. Record integrity is enforced using CRC32 checksums, and the store detects incomplete final log entries on restart, replaying valid data and truncating corrupted tails. The author explicitly notes the guarantee covers process crashes only, and makes no claims about behavior during sudden power loss or storage-controller failures.

0 comments Read more at DEV Community