From your first page, this looks cool and needed. But as others have posted, I can't get to your github pages.
Readit Newswek commented on Show HN: Nogic – VS Code extension that visualizes your codebase as a graph marketplace.visualstudio.... · Posted by u/davelradindra
wek commented on Cowork: Claude Code for the rest of your work claude.com/blog/cowork-re... · Posted by u/adocomplete
A CLI chat interface seems ideal for when you keep code "at a distance", i.e. if you hardly/infrequently/never want to peek at your code.
But for writing prose, I don't think chat-to-prose is ideal, i.e. most people would not want the keep prose "at a distance".
I bet most people want to be immersed in an editor where they are seeing how the text is evolving. Something like Zed's inline assistant, which I found myself using quite a lot when working on documents.
I was hoping that Cowork might have some elements of an immersive editor, but it's essentially transplanting the CLI chat experience to an ostensibly "less scary" interface, i.e., keeping the philosophy of artifacts separate from your chat.
I agree that for writing documents and for a lot of other things like editing csv files or mockups, I want to be immersed in the editor together with Claude Code, not in a chat separated from my editors
wek commented on Total monthly number of StackOverflow questions over time data.stackexchange.com/st... · Posted by u/maartin0
I had the opposite experience. I learned so much from the helpful people on StackExchange sites, in computer science, programming, geology, and biology.
Me too. I learned a lot from people on SO. Sometimes the tone was rude, but overall, I was and am grateful for it and sad to see this chart.
A bit hard to read but some fun images and examples. I appreciated his post on capitalism as not a zero sum game.
wek commented on Show HN: Vibe coding a bookshelf with Claude Code balajmarius.com/writings/... · Posted by u/balajmarius
"The gap between intention and execution was small, but it was enough to keep the project permanently parked in the someday pile." Well said!
This is my experience with agents, particularly Claude Code. It supplies sufficient activation energy to get me over the hump. It makes each next step easy enough that I take it.
I'd recommend learning from Jason Lemkin at SAAStr and from Jen Abel. She did two great podcasts with Lenny on Lenny's Podcasts.
Here in Belgium there's a village that's famous for doing this. Currently there's about 100 people there who are living with another family. https://nl.wikipedia.org/wiki/Gezinsverpleging_(Geel) If you translate you can read about it.
Thank you for sharing this.
wek commented on The U.S. Is Funding Fewer Grants in Every Area of Science and Medicine nytimes.com/interactive/2... · Posted by u/karakoram
Funding for basic science and medicen should be a bi-partisan winning issue. It is good for America. It is good for the world. It helps eventually lift the poor. It helps business. Its something the government can and should do that is hard for private business to do. It helps human knowledge. I'm motivated to reverse this trend.
wek commented on Show HN: Open-source Markdown research tool written in Rust – Ekphos github.com/hanebox/ekphos... · Posted by u/haneboxx
A paragraph or two on your motivation for this and the benefits of this approach would be helpful. Thanks!
wek commented on Skills Officially Comes to Codex developers.openai.com/cod... · Posted by u/rochansinha
Skills are the matrix scene where neo learns kungfu. Imagine they are a database of specialized knowledge that can an agent can instantly tap into _on demand_.
The key here is “on demand”. Not every agent or convention needs to know kung fu. But when they do, a skill is waiting to be consumed. This basic idea is “progressive disclosure” and it composes nicely to keep context windows focused. Eg i have a metabase skill to query analytics. Within that I conditionally refer to how to generate authentication if they arent authenticated. If they are authenticated, that information need not be consumed.
Some practical “skills”: writing tests, fetching sentry info, using playwright (a lot of local mcps are just flat out replaced by skills), submitting a PR according to team conventions (eg run lint, review code for X, title matches format, etc)
Nice analogy!