惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
罗磊的独立博客
小众软件
小众软件
T
Tailwind CSS Blog
宝玉的分享
宝玉的分享
博客园_首页
N
Netflix TechBlog - Medium
B
Blog
Recent Announcements
Recent Announcements
Y
Y Combinator Blog
Blog — PlanetScale
Blog — PlanetScale
L
LangChain Blog
F
Fortinet All Blogs
The GitHub Blog
The GitHub Blog
Stack Overflow Blog
Stack Overflow Blog
C
Check Point Blog
Last Week in AI
Last Week in AI
Jina AI
Jina AI
V
V2EX
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 叶小钗
博客园 - 【当耐特】

nedshed.dev

You need a Windows Remote Desktop, not an OpenClaw Tragic blimps, cooking mice, and epic penguins NBA x Ghibli The Auteur, The Cat, and The Flood of GPUs Disneyland on VHS The new stuff is always simple Surrendering to grooves in latent space Assertions are just temporarily embarrassed snapshots Rich Hickey's Glossary and Decision Matrix Bootstrapping boundaries Breaking changes and broken brands version = f(changelog)
Meet Gitcasso — Syntax Highlighting for GitHub Comments
Ned Twigg · 2025-10-10 · via nedshed.dev

In this YouTube episode, I walk through Gitcasso - a browser extension that fixes the messy parts of GitHub comments.

  • 🎨 Syntax highlighting for Markdown comments

  • 🧭 Quick navigation between open PRs and issues

  • 💾 Optional draft recovery (no more lost work!)

Then we go under the hood: how Gitcasso was built using Claude Code, Playwright, and AI-assisted coding. You’ll see how snapshot testing makes it easy to develop against a large corpus of use cases, and how slash commands can make the entire development process nearly automatic.

  • source code

  • install for chrome, install for edge

  • 0:00 syntax highlighting

  • 0:27 quick navigation between open PRs and issues

  • 1:09 draft autosave

  • 2:02 how it was built

  • 3:06 using the corpus viewer

  • 4:37 using a claude slash command

  • 5:55 using playwright

  • 8:06 fixing a bug using playwright and claude slash commands

  • 9:37 how the corpus viewer works

  • 10:20 development system design

    I think our job as software developers now is to design and describe a camera that captures the problem domain, and then design and describe a camera that captures the output of your solution. Once you’ve described these systems of lenses, mirrors, and cameras; AI can build them for you. And when you have this ability to image the problem and the behavior of your solution, then AI can build a solution or help you build a solution really effectively. And you can you can oversee it easier because you have these cameras to work with. (edited to replace “pipe” with the better concept of “camera”)

  • 11:00 precommit script

  • 11:23 snapshot tests

  • 13:22 outro, thanks for watching