今日已更新 130 条资讯 | 累计 34764 条内容
关于我们

标签:#m

找到 10323 篇相关文章

产品设计

LG’s 27-inch Tandem OLED gaming monitor is cheaper than ever

The price of LG’s UltraGear 27GX700A-B 1440p gaming monitor that came out last August has dropped to nearly its best price yet. You can grab it at Amazon for $484.99 or at LG for $499.99 (originally $599.99). That’s a great deal considering this is one of LG’s Primary RGB Tandem panels built with fourth-generation WOLED […]

2026-07-01 原文 →
AI 资讯

A Life in 150 Words, with AI

Of all the things involved in turning a woman's life into a 60-second reel, I assumed that the writing would be the easy part. Surely telling a good story in 150 words is exactly what a large language model should be good at; yet it proved surprisingly difficult. Draft after draft suffered from common AI weaknesses: a tendency to use hyperbole and inspirational language, to generalize, follow generic founder arcs ("built in a basement"), and focus on morbid details. (For this effort, I was using Sonnet 4.6, which I found to be better — more grounded, more true to facts, less inventive — than Opus 4.7 at creating longer bios.) Getting to something publishable took a significant amount of work. That said, the human in this story also found writing good short story arcs surprisingly challenging, so the effort spent on getting the system to do it decently was well worth it. Here's some context, then what I did. I've been publishing short biographies of notable women for a while now, on a website called Tycoona . Why notable women? Because in each field there are so many women who contributed so much and are little known. I've never understood why Corita Kent , the pop-artist nun, isn't as famous as Andy Warhol, why Hetty Green , the Gilded Age value investor called both the "Witch of Wall Street" and the "Queen of Wall Street," disappears into history behind Benjamin Graham and his protege Warren Buffett. The problem I faced is that no one was seeing my bios, so I decided to make short videos or reels in hopes of increasing my reach. Creating the technical infrastructure for the reels on top of my existing system was fun and relatively straightforward. Each reel consists of a series of "beats," and Remotion turns those beats into a vertical reel, complete with on-screen text and royalty-free images & attributions pulled from Wikimedia, Flickr, or Library of Congress. For content, the beat generator relies on the knowledge base of validated facts that my system creates f

2026-07-01 原文 →
AI 资讯

Stop Chunking Documents: The Open Knowledge Format (OKF) for Enterprise AI

Originally published on PrepStack . Everyone's first RAG pipeline is the same four boxes: documents, chunk, vector DB, LLM. It demos in an afternoon and then quietly betrays you in production — stale answers, no relationships, no governance, and a model guessing from fragments. The fix is not a bigger vector index. It is to stop storing documents and start storing knowledge . That is Open Knowledge Format (OKF). To be clear up front, because the title is deliberately provocative: OKF does not kill embeddings. Vectors still do the recall. What OKF kills is blind chunking — slicing opaque documents into context-free fragments and hoping cosine similarity reassembles meaning. On Mattrx , a multi-tenant marketing-analytics SaaS (.NET 9 + Azure SQL + a Python FastAPI AI service), replacing blind chunking with OKF + a Context Engine took the assistant's hallucination rate from 18% to 3% and stale-answer rate from 11% to 1.5% . TL;DR Dimension Documents → chunk → vector DB (before) OKF + Context Engine (after) Unit of knowledge Opaque chunk of text Typed, governed knowledge unit Structure None — chunks are islands Metadata + relationships + schemas Freshness Snapshot, rots silently valid_until + live API refs Rules Buried in prose, ignorable First-class data the engine enforces Retrieval Top-k cosine Hybrid + vector + graph Multi-hop questions Unanswerable Answered via relationships Results after the rebuild: Knowledge base restructured into ~11,000 OKF units (Markdown + metadata + relationships + APIs + schemas + business rules). Hallucination 18% -> 3% ; faithfulness 0.96 ; answer-relevance 0.91 . Context tokens/call 14k -> 3.5k — structure lets the engine attach the right thing, not everything. Outdated-answer rate 11% -> 1.5% ( valid_until + metadata freshness). Multi-hop questions unanswerable -> answered via graph retrieval. Deprecated-plan recommendations recurring -> 0 (business rules enforced as data). The one mental shift: a chunk is a fragment of text with no id

2026-07-01 原文 →
AI 资讯

Why Manual Test Cases Should Live in YAML

Most teams still treat manual test cases as rows in a SaaS database. That worked when cases were written slowly, reviewed rarely, and automation lived in a separate silo. It works less well now. AI can draft cases from screenshots and user stories in minutes. Automation lives next to application code. QA and dev share the same PRs. Auditors ask where test data lives and who changed what. In that world, test cases are data — and the format you choose matters as much as the tool UI. The durable direction is tests as code : plain YAML files in version control, with a thin local layer for humans to browse, run, and review. Not because databases are evil, but because git + YAML matches how we already work with code, AI, and compliance. 1. AI is good at YAML — and YAML keeps your data yours LLMs are unusually good at structured text: YAML front matter plus a Markdown body is a sweet spot. Give the model a schema ( title , tags , priority , steps, expected result) and a screenshot or user story, and you get a draft case in one pass. That matters for more than speed: Boundary cases — ask the model what you might have missed; it can reason about the scenario, not just paraphrase the story. Consistency — the same format every time makes batch generation and review predictable. The deeper point is data ownership . Cases in a vendor DB are convenient until they are not: export limits, API friction, another system to secure, another place sensitive scenarios live. Local YAML in your repo is trivial for AI to read (including Cursor, Copilot, or whatever you use next), diff, and update — without shipping your test catalog to a third party. For many teams, that is a real security and efficiency win — not ideology. 2. Manual YAML beside automation makes coverage measurable When manual cases and automated tests sit in the same repository, a few things become boring in a good way: Tag a case automated: true and point params at a Playwright or Selenium path — one file, one id. Automati

2026-07-01 原文 →
AI 资讯

mcpgen: Turn any OpenAPI spec into an MCP server in seconds

I got tired of manually writing MCP tools for every REST endpoint I wanted to expose to an LLM. So I automated it. mcpgen reads an OpenAPI JSON or YAML file and generates a complete, ready‑to‑run MCP server in Python. 🔧 What it does Parses OpenAPI 3.0 / 3.1 specs Creates one MCP tool per endpoint (with snake_case names) Handles auth automatically (API key, Bearer, etc.) Outputs a clean, human‑readable Python script Zero runtime surprises – just mcp and httpx 🚀 Quick start bash pip install mcpgen mcpgen my-api.json -o my-mcp-server python my-mcp-server/server.py The generated server runs over stdio – ready to plug into Claude Desktop or any MCP client. 🧪 Real‑world test Recently a contributor added an OpenAPI 3.1 fixture (Xquik API) with lookupTweet and getUser endpoints. The tool generated the correct tools, including path parameters and x-api-key auth, on the first try. All 18 tests pass. It works. 🤔 Why you might want it If you’re building LLM agents that need to interact with APIs, mcpgen eliminates the boilerplate. You don’t have to write a single @app.tool() decorator by hand. It also makes it dead simple to experiment – change your API spec, regenerate the server, and you’re done. 📦 Links GitHub: JnanaSrota/mcpgen PyPI: pip install mcpgen MIT licensed, open to contributions 🙏 Feedback If you try it with your own API spec and something breaks (or works beautifully), I’d love to hear about it. Drop a comment or open an issue. Thanks for reading!

2026-07-01 原文 →
开发者

Rockstar workers push to unionize ahead of GTA VI’s launch

Workers at Grand Theft Auto VI developer Rockstar Games have submitted a request for their union, the IWGB Game Workers Union, to be voluntarily recognized, according to a press release. The request follows Rockstar firing more than 30 staffers last year in a move accused of being "union busting." According to the release, IWGB members […]

2026-07-01 原文 →
AI 资讯

Xbox weighs canceling Blade game and shuttering Arkane

Microsoft is set to announce a wave of layoffs for its Xbox studios and employees next week. Sources familiar with Microsoft's plans tell The Verge that the layoffs will lead to studio closures or spinoffs, potential mergers of studios, and canceled games. I understand Microsoft is currently weighing closing at least five studios, including the […]

2026-07-01 原文 →
开发者

What is a quantum computer good for? Absolutely nothing — yet

To this day, we have yet to see a quantum computer conclusively perform a single useful task. Existing machines are simply too small and error-ridden to solve commercially relevant problems. That hasn't stopped Donald Trump's science adviser from promising a "quantum computer powerful enough for scientific discovery by 2028" and Trump from issuing a new […]

2026-07-01 原文 →