6 items
Benn Jordan argues that the ethics of AI use matter most once vibe-coded software is sold, where cheap clones can crowd out expert-built tools without buyers knowing the difference. He proposes two rules for vibe-coded software: open source it so it can be supported and debugged, and label it with a standardized self-rating that runs from NoAI through AI-aux, AI-UI, and AI-dev-A/B/C to fully AI-written AI-V.
A lightweight open source library that renders Mermaid diagram syntax to SVG, themed with CSS variables so colors and fonts change without re-rendering.
The site's comparison against Mermaid.js claims a 230 kB gzipped bundle versus 1.6 MB, sub-millisecond render times, zero direct dependencies, and layouts that adapt on small screens rather than just scaling down. Usage is a single render() call that returns an SVG string.
Explores how Chinese open-weight models like Moonshot AI's Kimi K3 have closed the gap with U.S. frontier models at a fraction of the cost, and the resulting rift in Silicon Valley — Nvidia, Meta, Microsoft, OpenAI, and Google backing an open letter defending open-weight AI, with Anthropic the lone major holdout.
Argues AI progress is real and driven by Moore's law and general computing progress, not by frontier labs, whose anti-open-source arguments are read as fear of commodification rather than safety concerns. Pushes back on "singularity" hype as a distraction, while affirming coding agents give a genuine, if overstated, productivity boost.
A Substack essay exploring how CRAN's reverse dependency checks — which block a package update if it breaks any downstream package — embody a "monorepo mindset" that makes breaking-change authors responsible for their entire dependency graph.
Contrasts CRAN's culture of author-owned migrations with PyPI/npm's publish-at-will model. The author argues CRAN's approach, while slower for individual releases, produces better outcomes for the ecosystem — a point reinforced by their experience at Databricks, where centralizing breaking changes (rather than federating them to consumers) led to faster, more complete migrations with fewer regressions. Particularly pointed for Python ecosystems where library churn and silent breakage are routine.
Jeremy Howard challenges the industry framing of AI adoption as a low-risk bet, arguing that outsourcing thinking to agents causes active de-skilling. He advocates for a human-centric approach where AI amplifies understanding rather than replacing it.
I call Howard's critique 'Jeremy's Wager' — the idea that going all-in on agents isn't a safe Pascal's Wager but a dangerous gamble where the hidden cost is active de-skilling. If AGI doesn't arrive as predicted, you're left with diminished skills and an organization running on spaghetti code nobody understands. His alternative maps directly onto Answer.ai's pedagogy of understanding over abstraction.