I'm thinking of adding a workflow where the agent pulls information from a GitHub issue to create a local bead "epic" for it to start building from it.

It removes the need for having a separate md file for tracking work and also makes it possible to run parallel agents working against the same issues.

I'm very happy with what I saw so far, working on an already existing project.

Articles are just stored directly in a single directory, using links (and thus backlinks) the way to index the articles. AI agents can also use this to easily traverse the documents, helping out in structuring or to retrieve the correct information.

#zettelkasten #docsMCP

I would prefer to avoid X or LI - sadly it's still where many people are. Do you have any good strategies?

I've decided to just start cross-posting to my Bluesky and Mastodon accounts as well and see which works for me.

Good luck with that!

I found it especially useful to incorporate note-taking directly from neovim when mob-programming.
Key mapping to create Zettel, open todo, open journal or quick search the Obsidian vault. 🌟

Makes it clear for everyone what's discussed or decided.

Very relevant question 😅
IDP as in "Internal Developer Platform" this time.

Content can be a demo of a platform feature we created as well as actually creating something which will later be a feature that teams will use.

This time it was mostly #Golang basic tips like tests and mocks while starting implementation.

#neovim is great for showing only the interesting parts

I use both! Especially when using github.com/epwalsh/obsi...

Most notes are done in neovim where a short command searches my vault or adds a Zettel.

In Obsidian I use Excalidraw to add drawing where needed.

Looks like github.com/MeanderingPr...

Renders markdown very nicely. Callouts, tables, etc!

Mitchell announced it would be publicly released in December, so not far out anyway 🙌

mitchellh.com/writing/ghos...

Don't miss out on this crucial competence when starting the journey of creating an internal developer platform or similar!

You have to get the engagement from teams that will use it! Get contributions as early as possible. This will strengthen the progress and you're more likely to hit the target.

Totally agree with your take, especially the docs! 😅
Will be interesting to see how it evolves!

Worth mentioning that Kargo CAN trigger workflows and autopromote when a metric is successful using an opinionated approach with Argo rollouts. Would be nice with a standardized approach!

Vimium to the rescue!
A must-have extension which is available in many browsers 👌

Using the "rendered manifest" pattern, the team also has full visibility of what the updated helm charts include.

The teams still have the possibility to add their own infra, but 80-90% of teams have the same needs. Who doesn't want to have correctly configured infra which is timely updated in their service?