AI/Coding

• #Articles
  • OReilly/Blog/25/02/The End of Programming as We Know It

• Cursor

  • #Articles
    • Person/Geoffrey Huntley/Blog/25/02/You are using Cursor AI incorrectly...
    • Person/Oskar Wickstrom/Blog/25/02/Machine: Learning; Human: Unlearning
    • Person/Rob Shocks/Build with AI Resources/Cursor AI Rules - The Missing Manual
    • Person/Rob Shocks/Build with AI Resources/AI Dev Project Setup Prompts

  • #Ideas

    • CursorAI/Idea/Proj Rules GitHub CLI AI SLDC
  • Docs
    • CursorAI/Docs/@ Symbols
  • #MCP
    • Person/Kevin Leneway/YouTube/Build Cursor on Steroids in 20 Minutes with MCP
  • Reddit
    • Reddit/cursor/Cursorrules, Rules for AI, or Project Rules 2024/02
    • Reddit/cursor/25/02/Hidden Gem - Open search results in Composer
    • Reddit/cursor/25/02/How I solved Cursor's hallucination problems with Supabase using 2 MCP Protocols
  • People
    • Person/Geoffrey Huntley
    • Person/Oskar Wickstrom
    • Person/Rob Shocks
  • #Video #Tutorial
    • Person/Rob Shocks/YouTube/25/02/Master Cursor AI App Dev with Rules
• #Events
  • OReilly/Event/25/05/Coding with AI - The End of Software Dev As We Know It - an event on 2025-04-24 Thu
• #Tools
  • CLI
    • Codeweaver - CLI for turning codebase structure into Markdown for transmitting to AI/LLM

• GitHub/Projects/Q/What is the difference between Github Milestones and Github Projects
• GitHub/CLI/gh/issue/develop

• Person/Daniel Miessler/Website/Telos
• Person/Daniel Miessler/Blog/24/10/How My Projects Fit Together

• #Decision
  • Logseq/Best Practice/Entity should be parent namespace of identity on other sites
  • Logseq/Best Practice/Utilize Date Namespacing Under Entity Name

• Person/Daniel Miessler
• Person/NetworkChuck

• Person/Marc Backes/Blog/24/01/Unlock sudo with TouchID on your Mac

• SemVer/vs Pride Versioning

• tldw.tube

• Bruno #API Client https://www.usebruno.com/

• #Discovered
  • CursorAI/Forum/Post/24/02/created apps with cursor but nearly giving up because project rules ignored
  • CursorAI/Forum/Post/24/02/My Best Practices for MDC rules and troubleshooting
  • Person/John Nathaniel Marquez
  • Person/Doug Silkstone
• #Learned
  • CursorAI/Command/Show Composer History
  • CursorAI/Technique/Composer/Keep it Short
  • Person/Brian Madison/GitHub/cursor-xml-rules-trial
  • CursorAI/Project Rule/How to Activate a Project Rule

• opennote.me

• #Discovered
  • Glamour used by GitHub/CLI for styling cli with stylesheets
• #Learned
  • GitHub/CLI/gh/api can make any kind of authenticated github API query. This greatly eases the burden needed to make API requests, since it goes through a standard authentication pipeline
  • GitHub/CLI/gh/completion
    • utilized this to set up completions in zsh
      • GitHub CLI | Take GitHub to the command line

• Developed a CursorAI workflow for submitting merge requests with cursor
  • see mr-create.mdc and other adjacent files in this MR
  • 
  • 
  • 
    • at this point, I had to pop out the terminal and answer the interactive prompt

    • ? Where should we push the 'codekiln/issue23-create-`alits-core`-package' branch?  [Use arrows to move, type to filter]
      > codekiln/alits
        Skip pushing the branch
      ? Where should we push the 'codekiln/issue23-create-`alits-core`-package' branch? codekiln/alits
      
      Creating pull request for codekiln/issue23-create-`alits-core`-package into main in codekiln/alits
      
      remote: 
      remote: 
      To https://github.com/codekiln/alits.git
       * [new branch]      HEAD -> codekiln/issue23-create-`alits-core`-package
      branch 'codekiln/issue23-create-`alits-core`-package' set up to track 'origin/codekiln/issue23-create-`alits-core`-package'.
      https://github.com/codekiln/alits/pull/25

  • 2025-02-12 06:48 - 9d2c6767 - docs: create a MR description for create alits-core package #23 #git/commit

• Person/David Zhang, co-founder of Aoomni
• JIRA/CLI
  • could be really powerful with CursorAI for providing context
  • I wonder if someone has made a Dev Container feature for this
  • tried, initially failed, then succeeded jira init received unexpected response 401 unauthorized from jira cloud behind SSO - Unable to generate configuration: invalid character '<' looking for beginning of value · Issue #822 · ankitpokhrel/jira-cli

• Cursor
  • CursorAI/Project Rule/Bug/Not Able to Find and Replace in Project Rule
  • CursorAI/Project Rule/How To/Create new Project Rule from Keyboard
  • CursorAI/How To/Give Instructions to Agent to Execute a VSCode Command
• Github CLI
  • GitHub/CLI/How to/Create a Gist on GitHub from the command line
    • created GitHub/Gist from CursorAI/Project Rule/markdown-output

    • gh gist create --public .cursor/rules/markdown-output.mdc -d "How to correct markdown output with cursor"
      - Creating gist markdown-output.mdc
      ✓ Created public gist markdown-output.mdc
      https://gist.github.com/codekiln/71f9497eaece99ba4d1c95b89d40b315

• GitHub/CLI/How to/Update an Issue from a local markdown file
  • #Example

    • gh issue edit 23 --body-file gh/issue23-create-alits-core-pkg.md 
      https://github.com/codekiln/alits/issues/23

• Jira
  • JIRA/How To/Extract Jira code from Branch name pre-commit hook
• Linux
  • dotfile/.netrc
• Zsh
  • Zsh/How To/Remove History Entry and Reload History on All Terminals

• Work log in Person/codekiln/GitHub/alits

• Python/Library uv

• GitHub/codekiln/dev-container-test
  • VSCode/Docs/remote/faq/Can I run VSCode Server on Older Linux Distributions

    • When it started up, I saw this warning: [10160 ms] !!! WARNING: Using legacy server, please check https://aka.ms/vscode-remote/faq/old-linux for additional information !!!
      • That link now redirects to the docs page linked above, which says,

        • Starting with VS Code release 1.86.1 (January 2024), the minimum requirements for the build toolchain of the remote server were raised. The prebuilt servers distributed by VS Code are compatible with Linux distributions based on glibc 2.28 or later, for example, Debian 10, RHEL 8, or Ubuntu 20.04. VS Code will still allow users to connect to an OS that is not supported by VS Code (OS that does not provide glibc >= 2.28 and libstdc++ >= 3.4.25) until February 2025
          

    • I saw GitHub/microsoft/vscode/issues/204269 Disappointment with Latest VSCode Update
    • I also saw StackOverflow/VSCode server unexpected Missing GLIBC gt eq 2.28
    • #Observation for now, DevContainer working, but it makes me wonder if it will soon break by the end of the month
      • #Q what version of glibc is available on Mac/OS?
        • Ans: I think it has nothing to do with macOS per se, it's about the image that you use, and I'm using mcr.microsoft.com/vscode/devcontainers/typescript-node:1-22-bookworm
        • node ➜ /app (main) $ ldd --version

          ldd (Debian GLIBC 2.36-9+deb12u9) 2.36
          Copyright (C) 2022 Free Software Foundation, Inc.
          This is free software; see the source for copying conditions. There is NO
          warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
          Written by Roland McGrath and Ulrich Drepper.
          

        • node ➜ /app (main) $ cat /etc/os-release

          PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
          NAME="Debian GNU/Linux"
          VERSION_ID="12"
          VERSION="12 (bookworm)"
          VERSION_CODENAME=bookworm
          ID=debian
          HOME_URL="https://www.debian.org/"
          SUPPORT_URL="https://www.debian.org/support"
          BUG_REPORT_URL="https://bugs.debian.org/"
          
  • 2025-02-08 16:58 - 32609957 - chore: basic devcontainer setup almost there #git/commit
    • Upon logging in this morning, I made a commit with the current dev container setup
    • Dev Container/Issue/Extension Not Found
      • result: filed Dev Containers not installing valid VS Code Extension - Minimal Reproduction - Bug Report - Cursor - Community Forum Software/Bug/Report

• added VSCode/Command/Dev Containers/Show Container Log

• a reference for turbo, pnpm with monorepo

• Apparently, it is possible to create a node.script Node for Max object and then bundle it in an c74/M4L/.amxd, but the docs on how to do that are centered on c74/max/standalone installations, not c74/M4L.
• the key insight is that all js files in the context of c74/js must have unique file names

• Live Javascript API: Observe multiple properties from one LiveAPI object - Max For Live Forum | Cycling '74 #c74/js #c74/M4L
  • note: Person/Zack Steinkamp also commented here

• ts-node
• c74/Node for Max API
  • const maxAPI = require("max-api");

• #Filed Person/codekiln/GitHub/alits; work log there

• CursorAI/Docs/tab/advanced-features
  • Cursor has the ability to accept just a single word at a time in Tab mode.

• DevContainer/CLIs have a CLI
  • containers.dev/templates - https://containers.dev/templates - a list of DevContainer templates, which are not repo templates for github, but their own thing - https://containers.dev/implementors/templates/
• GitHub/gitgitWi/nodejs-monorepo-devcontainer-template
  • fairly personal template for DevContainer
• PNPM devcontainer multiple project setup : r/node
• https://consoledonottrack.com/
  • export DO_NOT_TRACK=1

• here's how to list the commands in the image. node, it contains yarn, npx

  • docker run --rm node:22 ls -l /usr/local/bin
    
    total 94264
    lrwxrwxrwx 1 root root       45 Jan 21 05:32 corepack -> ../lib/node_modules/corepack/dist/corepack.js
    -rwxr-xr-x 1 root root      388 Jan 22 19:53 docker-entrypoint.sh
    -rwxr-xr-x 1 root root 96522032 Jan 21 05:30 node
    lrwxrwxrwx 1 root root       19 Jan 22 19:53 nodejs -> /usr/local/bin/node
    lrwxrwxrwx 1 root root       38 Jan 21 05:32 npm -> ../lib/node_modules/npm/bin/npm-cli.js
    lrwxrwxrwx 1 root root       38 Jan 21 05:32 npx -> ../lib/node_modules/npm/bin/npx-cli.js
    lrwxrwxrwx 1 root root       27 Jan 22 19:53 yarn -> /opt/yarn-v1.22.22/bin/yarn
    lrwxrwxrwx 1 root root       30 Jan 22 19:53 yarnpkg -> /opt/yarn-v1.22.22/bin/yarnpkg

• this is based on the assumption that you want to open up each repo individually
  • which isn't always the case
• some comments say that git can't be used in this case

  • But now you can't use git inside your devcontainer, which is a bit of a dealbreaker. 🙁 Any way to have the best of both worlds?
    

• This is a part of YouTube/@code/Playlist/Getting Started with Dev Containers

• notes

  • Monorepos in a Dev Container

    • The configuration sets up a Dev Container for working with a monorepo in VSCode.
    • Key settings:
      • "remoteUser": "node" → Runs the container as the node user instead of root.
      • "workspaceMount": "source=${localWorkspaceFolder},target=/workspace,type=bind" → Binds the local workspace folder to /workspace inside the container.
      • "workspaceFolder": "/workspace" → Sets the workspace folder inside the container.
    • This setup ensures that:
      • The workspace is correctly mounted inside the container.
      • The correct user permissions are applied.
      • It supports working with multiple repositories in a shared development environment.
• 📌 Docs Reference
  • VS Code Dev Containers Documentation
  • VS Code Remote - Containers