Run two Claude Code accounts simultaneously on macOS without re-authenticating by using separate configuration directories.
- Create Separate Config Directories
mkdir ~/.claude-account1 mkdir ~/.claude-account2
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>HLS Demo</title> | |
| <link rel="stylesheet" href="https://cdn.plyr.io/1.8.2/plyr.css"> | |
| </head> | |
| <body> | |
| <video preload="none" id="player" autoplay controls crossorigin></video> | |
| <script src="https://cdn.plyr.io/1.8.2/plyr.js"></script> |
| No. | Nama Kementerian | Nama Bahasa Inggris | Kependekan |
|---|---|---|---|
| 1. | Kementerian Koordinator Bidang Politik dan Keamanan | Coordinating Ministry for Political and Security Affairs | Kemenko Polkam |
| 2. | Kementerian Koordinator Bidang Hukum, HAM, Imigrasi, dan Pemasyarakatan | Coordinating Ministry for Legal, Human Rights, Immigration, and Penitentiary Affairs | Kemenko Hukhamimpas* |
| 3. | Kementerian Koordinator Bidang Perekonomian |
This guide will help you set up a complete LaTeX environment on Windows with MiKTeX, VS Code, and automatic formatting with latexindent.
The purpose of this guidebook is to lay down principles and guidelines for how to write code and work together at Our Machinery.
Each guideline in this document is identified by a unique identifier (OMG-META-1) as well as
a name (Guidelines are identified by unique identifiers). Names may change, but identifiers are
permanent and can be used to permanently and uniquely refer to a specific guideline.
| // To subscribe to an event, pass this JSON text to the client through the WebSocket: | |
| { | |
| "body": { | |
| "eventName": "NameOfEvent" // Replace with an event name listed below | |
| }, | |
| "header": { | |
| "requestId": "xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxxxxxxx", // UUID | |
| "messagePurpose": "subscribe", | |
| "version": 1, // Protocol version (currently 1 as-of 1.0.2) |
First of all, you need to understand you are not writing documentation for you, nor for your current team. You are writing documentation for the future developers that were not there when you first wrote this code. Worst of it, they might think it is bad code for many reasons and won’t understand why you wrote this way.
Taken from: How to write good software technical documentation
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.