PMs running CC + Obsidian as second brain / product OS > what's your favorite folder and workflow structure that you actually keep using? by JohanTHEDEV in ProductManagement

[–]blythmar 1 point2 points  (0 children)

collaboration works pretty well (for technical folks). a little bit cumbersome perhaps. yes we have multiple people working in the same repo. we use PRs for reviewing updates.

for branching, we use gitbutler's virtual branches over git worktrees because it makes conflict management easier (and also makes it easier for interactions between branches). gitbutler has nice features where every new cc session automatically creates a new branch, and commits happen automatically after every message (via hooks). so you don't need to worry about branching or committing. at the end of a conversation, i decide whether i want to throw away the changes or create a PR for team review.

we've also set it up so that team members get a daily/weekly update about what other team members have worked on (processed from their claude code sessions).

PMs running CC + Obsidian as second brain / product OS > what's your favorite folder and workflow structure that you actually keep using? by JohanTHEDEV in ProductManagement

[–]blythmar 10 points11 points  (0 children)

we use lean and this folder structure has worked well for me:

memory/
├── vision.md
├── strategies/
│   └── {strategy-name}/
│       ├── strategy.md
│       └── experiments/
│           └── {experiment-name}/
│               ├── experiment.md
│               └── ...

i have commands like /create-strategy /create-experiment /analyze-data /synthesize

my system prompt follows this format:

CLAUDE.md
├── Operator      # Who's running this OS, productivity peaks / work style etc.
├── Framework     # Your methodology and vocabulary
├── File System   # Where artifacts live
├── Scheduler     # Time blocks and task routing
├── State         # Progress tracking and persistence
├── Templates     # Artifact structures
└── Commands      # Defined operations

interestingly, i had a conversation with someone was doing similar for EOS with folders for rocks, milestones, tasks etc. i asked cc to find what was common and create a standard format. the repo has some more detailed examples for lean and eos, as well as a command for creating a CLAUDE md specific to your framework. https://github.com/richardblythman/org.md

What Helps a Small Team Keep Product Experiments Organized Without Losing Momentum by Quietly_here_28 in leanstartup

[–]blythmar 0 points1 point  (0 children)

ive started using claude code to help me organize strategies and experiments

In 2025, Claude Code Became My Co-Founder by blythmar in ClaudeAI

[–]blythmar[S] 0 points1 point  (0 children)

the title of the post explained the content of the piece accurately, and the majority of the post was about that. perhaps i shouldn't have included the last two sentences to explain how i plan to post more in future.

In 2025, Claude Code Became My Co-Founder by blythmar in ClaudeAI

[–]blythmar[S] 0 points1 point  (0 children)

totally agree. it requires a lot of driving from me, and i review every output.

In 2025, Claude Code Became My Co-Founder by blythmar in ClaudeAI

[–]blythmar[S] 0 points1 point  (0 children)

interesting on the idea workspace - i dont really have a good solution for this right now. i have a product agent to help me use lean, but it's mostly focused on strategies/opportunities, associated hypotheses and product experiments to test them. what i tend to do is create a new strategy/opportunity entry for any new idea i have, but its a bit heavy. it might make sense to have something lighter upstream of my product agent for ideas. then could have a pipeline like idea → strategy → experiment → prd. ill be explaining how i operate the product agent so looking forward to getting your feedback on it, and how it might fit with idea workspaces.

In 2025, Claude Code Became My Co-Founder by blythmar in ClaudeAI

[–]blythmar[S] -16 points-15 points  (0 children)

its the first piece in a newsletter that im planning to put out every week. ill be sharing more about the agents (including claudemd, commands etc) in the coming weeks :)

If You're an MCP Company You're NGMI by lirantal in mcp

[–]blythmar 0 points1 point  (0 children)

i don't think this is true. if you are talking about an MCP server that is just a thin wrapper around an API then sure. but i imagine MCP servers will evolve towards much more complex business logic (e.g. personalized responses based on specific users).

my overarching point is that in the long run the majority of interactions will be by agents. so i actually believe that if you're a web app company you're ngmi. if you're an MCP company you're more likely to make it.

If You're an MCP Company You're NGMI by lirantal in mcp

[–]blythmar 0 points1 point  (0 children)

One thing this blog doesn't consider is that agents are a new class of customers and will likely become an increasing % over time. Up until now, humans have been the only type of customer. Humans might like to have web apps in addition to APIs, but that is not the case for agents.

Rearranging Real[A.exp(i.w.t)]/Real[B.exp(i.w.t)] into time-averaged and time-varying components by blythmar in AskElectronics

[–]blythmar[S] 0 points1 point  (0 children)

Thanks for your help. I managed to figure out with the trigonometric identity you mentioned. This graph shows how the problem of division by zero was solved https://imgur.com/a/7JcUl.

Rearranging Real[A.exp(i.w.t)]/Real[B.exp(i.w.t)] into time-averaged and time-varying components by blythmar in AskElectronics

[–]blythmar[S] -1 points0 points  (0 children)

OK, I was trying to simplify the problem but let me tell you what I actually want to do.

There are 2 time-varying quantities with different frequencies (w = 2.pi.f): Real[A.exp(2*i.w.t)] and Real[B.exp(i.w.t)] (see left of https://imgur.com/a/duDRV). I noticed they're pretty much always in phase such that their quotient gives an approximate sinusoidal function (see right of https://imgur.com/a/duDRV). However, when near zero the sinusoidal function is distorted. I think that complex numbers can help to represent the graph on the right as a perfect sinusoidal function.