Researcher Claims to Solve 20 Erdős Problems Using Parallel AI Accounts

·1 views

A researcher has reportedly tackled 20 open problems from the famous Erdős mathematical problem set using AI assistance. The approach involved running 20 separate Codex accounts simultaneously in parallel. The project is documented on the website starfleetmath.com and was shared on Hacker News. Erdős problems are longstanding unsolved challenges in mathematics posed by prolific Hungarian mathematician Paul Erdős. The claim has attracted attention in the math and AI community, though details on verification remain limited.

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)

Knowledge-and-Memory-Management v0.0.2 Adds Portable Agent Knowledge Pipelines

Version 0.0.2 of the open-source Knowledge-and-Memory-Management toolkit has been released, focusing on portability and modularity for developers building autonomous AI agents. The update replaces hardcoded file paths with an $AGENT_HOME environment variable, allowing knowledge pipelines to run consistently across different systems and environments. The toolkit is split into two modules: a knowledge_collector that ingests content from web pages, YouTube videos, and articles, and a memory_manager that handles storage, retrieval, and time-based decay of entries. All collected data is normalized into a standard dictionary format and stored under paths relative to $AGENT_HOME, enabling easier containerization and deployment. The memory manager also supports semantic embedding-based indexing and allows developers to swap storage backends such as SQLite or PostgreSQL without modifying collection logic.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Scaling Up Servers Made the App Slower — Here's Why That Happens

A software engineering analysis highlights a counterintuitive failure mode where automatically scaling up server instances can worsen performance rather than improve it. In the example described, a system's autoscaler tripled compute resources from 12 to 40 instances in response to rising latency, yet latency continued to climb. The piece argues that scaling infrastructure is not a simple dial that can be turned up to fix performance problems. Instead, the author contends that scalability must be treated as a deliberate architectural design choice made early in development. Without the right underlying design, adding more hardware can amplify bottlenecks and increase costs without delivering any benefit.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

25-Year Platform-First Advocate Argues AI Agents Demand Feature-First Codebases

A veteran software architect with 25 years of experience building platform-first systems argues that the approach is no longer effective in an AI-driven development environment. He cites data showing roughly 60% of features on a six-month roadmap become obsolete before launch, and a McKinsey 2025 survey finding that 88% of organizations use AI but only 6% see real bottom-line impact. The author contends that AI agents perform best when tasks are small, bounded, and self-contained, conditions that traditional horizontal platform architectures fail to provide. He advocates for vertical slice architecture, popularized by Jimmy Bogard, which organizes code by feature rather than technical layer, giving agents a single folder with everything needed to complete a task. McKinsey's May 2026 report describing overnight agent-driven development cycles, dubbed the '24-hour sprint,' reinforces his case that delivery models must change to fully realize AI productivity gains.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

TypeScript 7 breaks ESLint, ts-jest and ts-morph due to unstable programmatic API

TypeScript 7 introduces tsgo, a Go-based port of the TypeScript compiler under Project Corsa, delivering roughly 10x faster builds compared to the JavaScript predecessor. However, the programmatic API that tools like typescript-eslint, ts-jest, and ts-morph rely on to perform AST traversal and type introspection is not yet stable and is expected to land only in version 7.1. As a result, typescript-eslint fails at install due to peer dependency conflicts, ts-jest breaks with transform errors, and ts-morph may silently produce incorrect output. Developers are advised to keep TypeScript pinned to 6.x for existing tooling while installing the separate @typescript/native-preview package solely for fast type-checking in CI pipelines. The side-by-side setup is recommended until TypeScript 7.1 delivers a stable programmatic API that the broader ecosystem can safely adopt.

0 comments Read more at DEV Community