3 ms·

A company (mutable ai) was acquired by Google last year for essentially doing this but outputting a wiki instead of a tutorial.

zh2408 2y ago
Their site seems to be down. I can't find their results.
- codetrotter 2y ago
  Were they acquired? Or did they give up and the CEO found work at Google? https://news.ycombinator.com/item?id=42542512 https://news.ycombinator.com/item?id=42542512 The latter is what this thread claims ^
  - nxobject 2y ago
    It sounds like it'd be perfect for Google's NotebookLM portfolio -- at least if they wanted to scale it up.
  - chairhairair 2y ago
    I don’t know the details of the deal, but their YC profile indicates they were acquired.
  - cowsandmilk 2y ago
    you're going to trust the person who started the thread with no idea what happened to the company and then jumped to conclusions based on LinkedIn?
- deleted 2y ago
  [deleted]
kaycebasques 2y ago
I meant to write a blog post about mutable.ai but didn't get around to it before the product shut down. I did however archive the wiki that it generated for the project I work on: https://web.archive.org/web/20240815184418/wiki.mutable.ai/google/pigweed https://web.archive.org/web/20240815184418/wiki.mutable.ai/g... (The images aren't working. I believe those were auto-generated class inheritance or dependency diagrams.) * The first paragraph is pretty good. * The second paragraph is incorrect to call pw_rpc the "core" of Pigweed. That implies that you must always use pw_rpc and that all other modules depend on it, which is not true. * The subsequent descriptions of modules all seemed decent, IIRC. * The big issue is that the wiki is just a grab bag summary of different parts of the codebase. It doesn't feel coherent. And it doesn't mention the other 100+ modules that the Pigweed codebase contains. When working on a big codebase, I imagine that tools like mutable.ai and Pocket Flow will need specific instruction on what aspects of the codebase to document.

zh2408 2y ago

Their site seems to be down. I can't find their results.

codetrotter 2y ago
Were they acquired? Or did they give up and the CEO found work at Google? https://news.ycombinator.com/item?id=42542512 https://news.ycombinator.com/item?id=42542512 The latter is what this thread claims ^
- nxobject 2y ago
  It sounds like it'd be perfect for Google's NotebookLM portfolio -- at least if they wanted to scale it up.
- chairhairair 2y ago
  I don’t know the details of the deal, but their YC profile indicates they were acquired.
- cowsandmilk 2y ago
  you're going to trust the person who started the thread with no idea what happened to the company and then jumped to conclusions based on LinkedIn?
deleted 2y ago
[deleted]

kaycebasques 2y ago

I meant to write a blog post about mutable.ai but didn't get around to it before the product shut down. I did however archive the wiki that it generated for the project I work on: https://web.archive.org/web/20240815184418/wiki.mutable.ai/google/pigweed https://web.archive.org/web/20240815184418/wiki.mutable.ai/g... (The images aren't working. I believe those were auto-generated class inheritance or dependency diagrams.) * The first paragraph is pretty good. * The second paragraph is incorrect to call pw_rpc the "core" of Pigweed. That implies that you must always use pw_rpc and that all other modules depend on it, which is not true. * The subsequent descriptions of modules all seemed decent, IIRC. * The big issue is that the wiki is just a grab bag summary of different parts of the codebase. It doesn't feel coherent. And it doesn't mention the other 100+ modules that the Pigweed codebase contains. When working on a big codebase, I imagine that tools like mutable.ai and Pocket Flow will need specific instruction on what aspects of the codebase to document.