Click any tag below to further narrow down your results
Links
Most LLM failures come from poorly written system prompts, not model selection. This guide covers the specific structures (XML tags for Claude, markdown for GPT), token budgeting strategies, and five patterns that consistently work—like making roles absurdly specific, showing exact output schemas instead of describing them, and explicitly telling models when to admit they don't know something. Testing matters too: run your prompts through happy paths, edge cases, and adversarial inputs multiple times before deploying.
VirtualBuddy runs macOS 12+ and ARM-based Linux virtual machines on Apple Silicon, automatically downloading or using custom IPSW/ISO images. It offers APFS-based snapshots, file and clipboard sharing, recovery mode, and beta device support via Xcode packages. You can customize hardware, save VM states, and build the app from source with Xcode 16.
Uncle Bob says he no longer reads the code generated by his AI agents to maintain productivity. Instead, he surrounds them with strict tests and metrics—unit tests, Gherkin tests, QA procedures, mutation testing, coverage—to ensure high confidence in their output.
This piece jokes about relying on “hope” instead of tests or planning in software projects. It pokes fun at developers who ship code and cross their fingers rather than following structured workflows.
This document lists documented failures of a stateless text-prediction process and prescribes strict rules to prevent them. It covers avoiding emotional language, unverified completion claims, misattributing test failures, bypassing quality gates, stubbing features, fabricating facts, and rushing implementations. Each rule demands explicit evidence, verification steps, and clear disclosure.
A Lobste.rs thread where developers share untested ideas—from building GUI toolkits with an accessibility-first architecture to enable better testing and scripting, to using 32-bit pointers on 64-bit systems for memory savings, and applying property-based approaches to infrastructure. Contributors discuss tools like AccessKit, the x32 ABI, and the benefits of driving design by fundamental properties rather than legacy constraints.