| name | japanese-tech-writing |
|---|---|
| description | 日本語の技術文書・書籍原稿の文章規範。段落と論証の構成（パラグラフライティング）、論証の厳密さ（ツッコミどころの除去）、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、翻訳調の比喩と擬人化の禁止（「運ぶ」「効く」「開かれた問い」など）、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。 |
| license | Unlicense（https://gist.github.com/k16shikano/67625f2a7d96e3bbdfae8d571a936063） |
日本語で技術的な原稿（書籍の章、記事、解説文）を書く・推敲するときは、以下の規範に従う。
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.
| import base64 | |
| import json | |
| import boto3 | |
| from cryptography.hazmat.primitives.ciphers.aead import AESGCM | |
| s3 = boto3.resource('s3') | |
| bucket = s3.Bucket('my-bucket') | |
| kms_client = boto3.client('kms') |
| Go 13 hrs 56 mins █████████████▌░░░░░░░ 64.6% | |
| Terraform 3 hrs 5 mins ███░░░░░░░░░░░░░░░░░░ 14.3% | |
| SQL 1 hr 32 mins █▍░░░░░░░░░░░░░░░░░░░ 7.1% | |
| TypeScript 1 hr 15 mins █▏░░░░░░░░░░░░░░░░░░░ 5.8% | |
| YAML 1 hr 11 mins █▏░░░░░░░░░░░░░░░░░░░ 5.5% |
| struct Keycode { | |
| // Layout-independent Keys | |
| // eg.These key codes are always the same key on all layouts. | |
| static let returnKey : UInt16 = 0x24 | |
| static let enter : UInt16 = 0x4C | |
| static let tab : UInt16 = 0x30 | |
| static let space : UInt16 = 0x31 | |
| static let delete : UInt16 = 0x33 | |
| static let escape : UInt16 = 0x35 |
Whenever we change our templates we still have to use our build script and this can get annoying. Thankfully with webpack-dev-server and BrowserSync we can fix this:
npm i -D browser-sync browser-sync-webpack-plugin webpack-dev-server
BrowserSync will act like a proxy, waiting for webpack to do its thing and then reloading the browser for us.
| # using such a setup requires `apt-get install lua-nginx-redis` under Ubuntu Trusty | |
| # more info @ http://wiki.nginx.org/HttpLuaModule#access_by_lua | |
| http { | |
| lua_package_path "/etc/nginx/include.d/?.lua;;"; | |
| lua_socket_pool_size 100; | |
| lua_socket_connect_timeout 10ms; | |
| lua_socket_read_timeout 10ms; | |
| server { |
| #!/bin/sh | |
| # インデックスのプレフィックス | |
| PREFIX="logstash-" | |
| if [ $1 ]; then | |
| PREFIX=$1 | |
| fi | |
| # OLDER_THAN日以上経過したインデックスを削除する | |
| OLDER_THAN=30 |
| ... | |
| app.use(function(req, res, next){ | |
| if (app.get('graceful_shutdown') === true) { | |
| res.set('Connection', 'close'); | |
| } | |
| next(); | |
| }); | |
| app.set('graceful_shutdown_start', function() { |
