2025-10-08 Wed

  • AI/Coding
  • #Ideas
    • DevContainer/Idea/Agentic System to Setup DevContainer
    • Maybe it's obvious, maybe it's not. We should be working more on targeted, paid agents.
      • Ex 1 - I keep seeing Claw Code in YouTube Transcripts. Maybe someone could create a targeted agent that would trawl through an AI transcription and clean-up incorrect transcriptions based on certain priors about the domain. For example, as a first step it would generate a summary of the target area, then generate a hypothesis about often miss-transcribed technical words or proper nouns, then clean it up.
      • Ex 2 - EdTech firms could work with universities and companies to develop repositories of paid agents that each have domain-specific, micro-topic insights. When you encounter a scenario in your business that you could use some insight on, you could rent an agent to look up the relevant theories and apply them to your situation.
        • In time, perhaps there might even be some sort of protocol inspired by BGP or Border Gateway Protocol which would let companies negotiate sharing of their agents.
      • Basically every tool - whether it's a coding tool, a conceptual instrument, etc - could, over time, in the right setting be a specialized service that pays for itself over time.
  • Who are your go-to AI coding YouTubers/influencers that actually know their stuff?" : r/ChatGPTCoding
    • AllAboutAI — ~214 K subscribers
      • Frequently cited for clear explanations and coverage of current AI tools.
      • Regular updates on emerging AI assistants and dev tools.
    • Corbin Brown — ~119 K subscribers
      • “First YouTuber I saw when I got into AI coding tools.”
      • “Has a full playlist on building out functional backends.”
    • Sam Witteveen — ~102 K subscribers
      • “Google engineer that actually understands how these things work.”
      • “Provides Colab notebooks and news on the latest AI coding features.”
    • Aladdin Persson — ~89.2 K subscribers
      • Known for technical, in-depth AI tutorials.
      • Often praised for educational clarity and practical coding walkthroughs.
    • IndyDevDan — ~45.4 K subscribers
      • “Exceptionally well done. I learned about mastering prompt engineering, why XML tags are better than Markdown, and a host of other things.”
      • “As less clickbaity as it can get — delivers value and avoids cringy fast pacing.”
      • “Pretty much the only AI YouTuber I can stand.”
    • Echohive — ~12.1 K subscribers
      • “Echohive is also great.”
      • Linked by multiple users as a valuable AI coding resource.
    • codingthefuturewithai — ~6.82 K subscribers
      • Mentioned as a solid follow-up recommendation alongside IndyDevDan.
      • Mixed opinions: some find it clickbaity, others appreciate the content depth.
    • Marvijo Software — ~4.64K subscribers
      • “Shares full-stack builds showing AI integration end-to-end.”
      • Praised for practical, real-world coding examples.
    • Codewello — ~3.52 K subscribers
      • Listed among creators who demonstrate real AI integration projects.
  • Discovered that GitHub and Docker have curated lists of MCP Servers - GitHub/MCP/Registry Docker/MCP/Registry
  • https://farnots.github.io/RedditToMarkdown/ is a tool that can convert a Reddit thread to markdown, useful for LLM stuff
Linked references — 1 page

Open the linked references

2025-10-05 Sun

  • Typescript/Concept/Barrel File - as with Py/init.py files, I prefer if developers don't try to use them to hide details or reshape the import structure. Updated My/Pref/Dev/Tool/PL/JS/TS accordingly.
  • poml - created Diataxis conceptual overview for Microsoft's Prompt Orchestration Markup Language, discovered through rulesync issue #136 where Person/dyoshikawa suggested POML for DRYing out prompt fragments with includes and substitutions. My main comment upon looking at it is, "why would anybody use this instead of Jinja?" The main drawback of these DSLs is that they tend to make SMEs uncomfortable. This doesn't even attempt to fix that, in my opinion; it's still going to be just as confusing or even more confusing than XML or plain Markdown. But one thing that's intriguing about it is the idea that it's a simple coding framework designed for the things needed in Prompt Templates that doesn't require a too much of programming language harness (e.g. jinja really only makes sense in a python project).
  • Person/dyoshikawa - created person page for dyoshikawa, creator of rulesync and ccsettings, student at Open University of Japan
  • BiomeJS - created Diataxis conceptual overview for this Rust/Library web development toolchain that unifies formatting, linting, and code analysis. Discovered through rulesync's use of it in their biome.json and devcontainer configuration. BiomeJS aims to replace ESLint and Prettier with a single, faster tool (35x faster than Prettier) built in Rust. Markdown is on their roadmap but not implemented yet; see Language support | Biome. I've been searching for a customizable auto-formatter for Markdown for a while so I will be interested to see when this support gets added.
  • archive.ph - created page for this web archiving service that bypasses paywalls and login walls, particularly useful for accessing Medium articles without login requirements
  • SerenaAI - created Diataxis conceptual overview for this AI Coding toolkit that provides semantic code understanding to LLMs via Model Context Protocol and Language Server Protocol. Discovered through rulesync's devcontainer configuration. Serena offers over 30 specialized tools for code manipulation and maintains persistent project knowledge in .serena/memories/ for cross-session context. Architecture combines LSP for symbolic code understanding with MCP for LLM-agnostic tool integration. Supports 15+ programming languages and works with Claude, Codex, Gemini, etc.
Linked references — 2 pages

Open the linked references

2025-10-04 Sat

  • rulesync/log/25/10/04 Sat - Issues with gitignore - issues with git/.gitignore -
    • rulesync/log/25/10/04 Sat - Issues with gitignore

      • 2025-10-04 Sat - git/.gitignore issues

        • Yesterday I discovered that the rulesync/gitignore command implies a usage of rulesync in which the configuration files for any given tool are treated as compiled build artifacts. I was curious about trying out this workflow, so I ran it, which added a bunch of rules to .gitignore for each AI/Coding/Tool - CursorAI, Claude/Code, etc.
        • Today, on another computer I discovered the classic problem with introducing git/.gitignore rules after some subset of files have been tracked to the repo. I asked Claude Code about it.

          • AI/Response

            • The .gitignore patterns (lines 24-25 and 29-31) will only prevent untracked files from being added, but they don't affect files that are already in the git repository.
            • Here's what happened:
              • 1. These files were previously committed to your repository
              • 2. When you ran rulesync generate, it modified these already-tracked files
              • 3. Git shows them as modified because they're already being tracked
              • 4. The .gitignore patterns don't apply to files already in git's tracking
            • To fix this, you have two options:
              • Option 1: Remove these files from git tracking (recommended if you want rulesync to manage them independently):
                • git rm --cached .cursor/rules/*.mdc .github/instructions/*.instructions.md CLAUDE.md .claude/memories/*.md
              • Option 2: Keep them tracked and commit the changes (if you want these in version control):
                • `git add .cursor/rules/ .github/instructions/ CLAUDE.md .claude/memories/

                  git commit -m "chore: update generated AI tool rules"`

          • So, what do I want to do?

            • Option 1 - Remove AI configuration files in repo

              • Pros
                • Some Search tools (like PyCharm) can respect git/.gitignore, and it would be convenient to not pollute the search space with a bunch of duplicate information.
                • It will be clearer to AI coding tools that respect gitignore which are the "canonical" versions of the files, which will be particularly useful in the common use case of asking AI tools to updating AI rules files.
              • Cons
                • Sometimes when I talk to people about how I accomplish certain things with AI, it's helpful to be able to hyperlink them to the exact prompt I use, and for many, it would be less confusing if that rule were in the format that they know.
                • I have to regenerate them regularly, which implies running them in a post-checkout hook.

            • Option 2 - Keep AI configuration files in repo

              • Pros
                • No need to regenerate them each time; one would regenerate every time a rule is updated, and then commit the changes
                • I can refer coders (be they human or AI) to a file in github that has the version of my rule in their framework of choice.
              • Cons
                • Often times I update AI configuration files in the middle of a task. Explaining to AI how to carefully stage only the items related to an AI configuration change when the git stage is dirty might be tricky and unreliable.
          • I ended up filing rulesync/GitHub/Issue/25/10/Feature request rulesync githook
    • rulesync/GitHub/Issue/25/10/Feature request rulesync githook
Linked references — 1 page

Open the linked references

2025-10-03 Fri

  • Uni/Harvard/HILT/Conf/25
    • Developing Talent in Young People by Benjamin S. Bloom | Goodreads #Book
    • question - if everyone got an A by rule, would that have a positive, negative or neutral effect on engagement?
    • it would be cool to document all the "co-curriculars" and the "lesson plans" with respect to the goals of teachers there (examples: learning from other students, metalearning about note-taking, etc)
    • great point - Poll/Everywhere in the classroom produces engagement, but then people take their phone out and check their texts, which is then a source of #Distraction
  • Book/Developing Talent in Young People by Person/Benjamin S. Bloom
    • Added to knowledge garden for reference on talent development through structured learning environments
  • Spotify/How To/Go to song in playing playlist tl;dr - click on the now playing view at right's title link
  • VSCode/Git/How To/Navigate Diff Changes Like JetBrains untested, but drafted at least. old issue for me!
  • VSCode/YouTube/22/12/Extremely helpful guide to merge conflict was conceptually useful but didn't help me with my problem, which was that a 3-way merge in vscode that had zero conflicts didn't have a "done" or a "continue" button.
  • git/commit/Conventional/gitmoji updated with comprehensive documentation about Conventional Emoji Commits, including examples and guidelines for ticket references in non-ticket projects
  • My/Pref/Dev/Tool/SCM updated with notes about ticket references being optional for non-ticket repositories
  • Created rulesync rules for commit conventions and journal updates in .cursor/rules/logseq-cursor-rules/
  • Added two new pages for documenting the VSCode Claude Code extension:
    • VSCode/Extension/Anthropic/Claude Code - Contains overview, features, requirements, and installation info
    • VSCode/Extension/Anthropic/Claude Code/Docs - Contains detailed usage documentation
    • Note: Limited information about renaming chats in VSCode Claude Code - documentation to be updated when more information is available
  • OpenAI/Academy created to document the OpenAI-backed education technology startup focused on AI/ML education
  • Added .rulesync/rules/logseq-page-naming-reference.md with clear examples of correct file naming vs. link format for Logseq pages
Linked references — 2 pages

Open the linked references

Earlier