Original 1975 Microsoft Altair BASIC Interpreter Source Code Released as PDF

·1 views

The original source code for the Altair BASIC interpreter, written in 1975, has been made publicly available as a PDF document. This piece of software represents one of Microsoft's earliest products, developed by Bill Gates and Paul Allen for the Altair 8800 microcomputer. The Altair BASIC interpreter was a landmark program that helped establish Microsoft as a company in the nascent personal computing industry. The document has surfaced via Gates Notes, Bill Gates' personal publishing platform, offering a rare historical look at early microcomputer programming. The release has drawn attention from the technology community as a significant artifact of computing history.

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)

Developer Uses System Design and Gamification to Master Cloud Engineering

A technical writer with cloud infrastructure experience is shifting focus toward becoming a proficient cloud engineer by adopting a system design-based learning approach. Over the past three weeks, they have been studying Linux, Docker, CI/CD, Terraform, and AWS, but found traditional learning methods led to overwhelm and "tutorial hell." Their new strategy centers on understanding how business decisions drive tool choices, using real-world and simulated scenarios for hands-on practice. To make learning more engaging, they are gamifying the process, including playing Bandit, a Linux-based learning game. They are also seeking recommendations for similar gamified tools covering Terraform, AWS, Docker, and Git.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Walden Robotics Built One Content Model to Serve Both Browsers and AI Agents

Walden Robotics developed a website platform using Prismic and Next.js App Router that serves content to both human visitors and automated AI clients from a single shared content model. The site is built from 19 reusable components, with editors assembling pages in a CMS while visitors receive statically generated HTML and automated clients can request structured Markdown. A discovery layer exposes endpoints that direct AI agents to APIs, authorization metadata, and news content without requiring a separate content pipeline. The platform separates page-level content from global records like navigation and announcements, ensuring a single CMS change propagates consistently across the entire site. Security is enforced by signing CMS-defined form fields with HMAC before they reach the browser, with server-side validation preventing tampered submissions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Almanac (YC S26) Builds Live Company-Wiki Agent to Fix LLM Context Failures

Y Combinator startup Almanac, part of the S26 batch, has launched an AI agent system designed to solve persistent context failures in multi-agent workflows. The product maintains a continuously updated company wiki by ingesting activity from tools like Slack, Gmail, GitHub, and calendar apps, then injects relevant context into every LLM call. A three-layer architecture handles tool connectivity, wiki compilation, and a context selector that ranks pages using keyword and semantic search before each agent action. The system enforces permission boundaries at both ingestion and retrieval stages, inheriting access control lists from source tools to prevent cross-department data leakage. Almanac acknowledges the model is not foolproof, noting that user-driven actions like forwarding sensitive emails to public channels can still expose restricted content.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Pi 1.0: How This GitHub-Trending Coding Agent Unifies LLM Tool-Calling APIs

Pi, a self-extensible coding agent developed by the Gatsby team, reached version 1.0 after nearly a year of development and is currently trending at number 8 on GitHub with over 100,000 stars. Its core value lies in a unified multi-provider LLM API that abstracts the differing tool-calling schemas of OpenAI, Anthropic, and Google into a single consistent interface. An agent runtime layer built on top manages multi-step workflows, handling conversation history, tool call state, and execution context across repeated LLM-tool interaction loops. When a tool fails, Pi serializes the error and passes it back to the LLM, which then decides whether to retry, switch tools, or abandon the task — making the LLM the primary orchestrator. The design prioritizes developer convenience over strict execution isolation, and notably lacks built-in retry logic or circuit breakers.

0 comments Read more at DEV Community