I was reading through CC MCPs docs ... MCP Notifications kind of did this right? The server/client could update each other automatically. So there was already this channel-like communication.
This is like that but instead of the server/client sending messages it's you.
2 days late to this post so not sure anyone's here, but what fascinates me is finding out how the different segments (or other such insects) are connected. Like, at each of those junctions it seems like a bottle-neck scenario where everything has to be condensed into some "wire" form to then connect to the next segment.
Thanks for the tip. Other ppl are saying "most of us started out like this" but if you haven't played with tailscale etc. (like me). Then this is new and good for learning imo
Semi related: what are your guys workflow to PCB design? I need to build an AFE + BLE MCU for a BCI, and having no EE background, my workflow is KiCAD -> buy components -> breadboard testing -> done?? -> order fully manufactured PCB?
better memory management: I have memories that get overlooked or forgotten (even though I can see them in the archive), then when I try to remind chatGPT, it creates a new memory; also updating a memory often just creates a new one. I can kind of tell that Chat is trying hard to reference past memories, so I try to not have too many, and make each memory contain only precise information.
Some way to branch off of a conversation (and come back to the original master, when I'm done; happens often when I'm learning, that I want to go off and explore a side-topic that I need to understand)
This is like that but instead of the server/client sending messages it's you.
reply