I will make a bet. Every knowledge worker will soon all be using a VSCode like app. Because otherwise, they will be replaced by one who does. Imagine every worker connected to the company data, controlling an agent that can also act on his desktop. The working app becomes: A. Files displayed in the middle of the screen B. Chat window (either left or right of the screen) C. Folder directory (either left or right of the screen) That's just VSCode. Not saying it will be literally VSCode used, but a similar app for sure. After some discussions with some very smart people, I was convinced that VSCode is the desktop app of the future.

I love the idea of collaborative ICM's and co-creation for the greater good, but there are some serious concerns imho: - We cant eat Github stars (thats why I'm on GitLab and local GIT) - Not everybody plays nice and honors the Good Intent and Licenses and shares like others - AI certainly doesn't care about licenses because they ingest and don't copy (github-copilot), make it their own and create a new Co-work or tooling - In the past we always had community/opensource editions next to commercial editions to protect community inputs, now we have REA - The maker community I'm part of, we share machine designs and collaborate on development and education, but we are all broke (at least no unicorns). - We have to sketch the "new world order of co-creation" before we start feeding some company's AI again... and yes we have the chance to do it with AI since we have all helped train it. - Sorry for preaching .. I know i'm at least 5 years too late ... so just call it venting

I just saw a YouTube video that discussed the death of MD Files, arguing that HTML files are the better way to go. Wanted to get the community ‘s thoughts on this and how it would impact ICM approach, if at all. Thanks

Using ICM alone makes one person fast. Using it as a shared knowledge base makes a whole team fast and consistent. I call it an organized organisation 😂 The hard part isn't the AI, it's conflict management. I enforce four steps in code, not prompts: - Resolve conflicts: Git or a shared drive, depending on the case - Permissions and visibility: who edits instructions vs. who edits data - Handle stale files: give new information dates and context - Full auditability: every request is logged My setup today: 7 people on community-based research. I'm the maintainer (rules). Everyone else is a member (data). They can suggest rules, but I approve them. The AI even flags broken rules to me: "he wants to do this but can't, check it out". Still unsolved: stale files. Expiry dates or events help, but assigning them when a file is created is the hard part. For now, expired files stay put, the AI traces linked files to infer why, and asks me when unsure. Every failure updates the rules. If you're building team ICMs, I'd love to compare notes. Technical or not, message me. 🤝

My son was born this week, Azrael is his name. Creation is a wild thing, I decided to spend some time (the little time I have) writing with just my own two hands as a celebration of the human life. No ai used in the script or writing, I hope y'all enjoy it. If you do please like and share and comment on YouTube.