Bookmarks

Bookmarks

marckohlbrugge/37signals-skills: Unofficial agent skills + reference guide that teach AI coding assistants to write Rails the 37signals way — extracted from Fizzy, Campfire, and DHH's code reviews
marckohlbrugge/37signals-skills: Unofficial agent skills + reference guide that teach AI coding assistants to write Rails the 37signals way — extracted from Fizzy, Campfire, and DHH's code reviews
Unofficial agent skills + reference guide that teach AI coding assistants to write Rails the 37signals way — extracted from Fizzy, Campfire, and DHH's code reviews - marckohlbrugge/37signals-sk...
·github.com·
marckohlbrugge/37signals-skills: Unofficial agent skills + reference guide that teach AI coding assistants to write Rails the 37signals way — extracted from Fizzy, Campfire, and DHH's code reviews
Tales from the Void: May 2026 Recap
Tales from the Void: May 2026 Recap
Our May 2026 recap covers VoidZero joining Cloudflare, Rolldown reaching 1.0 stable, and more.
·voidzero.dev·
Tales from the Void: May 2026 Recap
kenn-io/agentsview: Local-first session search, analytics, insights, and token use statistics for coding agents, supporting Claude Code, Codex, and more than 20 other agents.
kenn-io/agentsview: Local-first session search, analytics, insights, and token use statistics for coding agents, supporting Claude Code, Codex, and more than 20 other agents.
Local-first session search, analytics, insights, and token use statistics for coding agents, supporting Claude Code, Codex, and more than 20 other agents. - kenn-io/agentsview
·github.com·
kenn-io/agentsview: Local-first session search, analytics, insights, and token use statistics for coding agents, supporting Claude Code, Codex, and more than 20 other agents.
AgentsView
AgentsView
Local-first desktop and web app for AI agent sessions
·agentsview.io·
AgentsView
「幕末」の数学者たち: AIと数学|R. Shimada
「幕末」の数学者たち: AIと数学|R. Shimada
まさに黒船来航といったところでしょうか。 先月、OpenAIは内部モデルを使ってエルデシュの単位距離問題を解決したと発表しました。これは、AIが初めて数学における重要な未解決問題を解いた例であるという意味で、極めて重要な意義を持つと思います。 本記事は、今、数学界で何が起こっているのかを、数学者である筆者が私見も交えつつ解説し、まとめるものです。第一部では数学的内容を、第二部では専門家による評価を、第三部では今後の展望について書いています。 主な参考文献は二つあります。 一つ目はOpenAIによる当該論文(https://cdn.openai.com/pdf/74c24085-19b
·note.com·
「幕末」の数学者たち: AIと数学|R. Shimada
FontSelf
FontSelf
Self-hosted Google Fonts configurator.
·fontself.app·
FontSelf
seydx/node-av: FFmpeg bindings for Node.js. Features both low-level and high-level APIs, full hardware acceleration, TypeScript support, and modern async patterns
seydx/node-av: FFmpeg bindings for Node.js. Features both low-level and high-level APIs, full hardware acceleration, TypeScript support, and modern async patterns
FFmpeg bindings for Node.js. Features both low-level and high-level APIs, full hardware acceleration, TypeScript support, and modern async patterns - seydx/node-av
·github.com·
seydx/node-av: FFmpeg bindings for Node.js. Features both low-level and high-level APIs, full hardware acceleration, TypeScript support, and modern async patterns
When React parent components need to know their children
When React parent components need to know their children
In React, it’s always preferable to maintain a linear data flow. If a parent needs something, lift the state instead of smuggling it back up. All rules are made to be broken, though.
·jayfreestone.com·
When React parent components need to know their children
I wish Deno would keep doing what it does best
I wish Deno would keep doing what it does best
Deno emerged as a solution to the overwhelming configuration requirements of the modern TypeScript ecosystem by offering a zero-config, single-binary experience. By integrating essential tools for formatting, linting, and testing alongside web-standard APIs, it removed the tedious setup rituals that often deterred developers. Recently, however, Deno has pivoted toward deep Node.js compatibility, supporting npm packages and traditional module structures to accelerate adoption. This shift creates a strategic risk where high compatibility might inadvertently discourage developers from targeting Deno’s unique APIs, especially as Node.js adopts Deno’s innovations like native TypeScript support and permission models. Commercial pressures may be forcing a prioritization of rapid growth and compatibility over the patient development of a truly self-sufficient, vertically integrated toolchain. While Deno remains a powerful choice, its convergence with the legacy ecosystem suggests a move away from the radical simplicity that originally defined its mission. The ongoing convergence of runtimes serves as a vital reminder of the trade-offs between technical purity and the demands of commercial viability.
·hackers.pub·
I wish Deno would keep doing what it does best