Notes on "LLMs"

4 notes in total
Jan 3, 2026

I now use ChatGPT and Amp in a very simple way: I just create new threads and leave them as-is.

Previously for ChatGPT, I created several projects, and when I wanted to talk to it, I’d find and continue a relevant existing thread or create a new one in a project. I’d organize them periodically. Turns out it just looked neat but didn’t actually help. Now I just start a new chat when I think I need to. ChatGPT memorizes context automatically, which is sufficient.

Similarly for Amp, I used to organize my threads very carefully. After the labels feature shipped1, I started to label every thread manually after I completed one. I finally realized this practice doesn’t help — for now. So I deleted all the labels. And when to make a thread public? When I find I need to.

When you start using a tool, use it with the least friction and in the most intuitive way. Any feature that forces redundant manual work isn’t worth the hassle. Only use a feature if you find you need to.

  1. Amp news: Thread Labels

#TECH17 Jan 3, 2026
Dec 25, 2025

Happy holidays! At the end of 2025, I’m starting a blog. I’ve already written several entries and feel confident I can keep it going.

Here I talk about my past attempts, the writers who inspired me, the motivation, the topics to cover, and the approach I’m taking. It’s my version of a blogging manifesto.

#TECH9 Dec 25, 2025
Dec 24, 2025

I gradually realized that a unified formatting rule set is needed when working with multiple AI chatbots and agents.

Output formatting styles vary from model to model. For technical topics, I’ve found that Claude tends to output responses like complete documents, starting with an h1 heading and loves to use horizontal rules to separate sections; Gemini usually skips to h3 headings directly without h2 ones, which in my opinion is not a good practice.

Here are examples I tried on OpenRouter, prompting “Explain the Python programming language.”

Python explanation by GPT-5.2GPT-5.2, starting with an introductory paragraph and followed by sections

Python explanation by Claude Opus 4.5Claude Opus 4.5, a document-like output with an h1 heading at the top and multiple horizontal rules

Python explanation by Gemini 3 FlashGemini 3 Flash, using h3 headings directly

Python explanation by Kimi K2 ThinkingKimi K2 Thinking, also a document-like one

Even worse, from my experience, outputs from different versions of the same model series (e.g. GPT-5 and GPT-5.2) can vary greatly in terms of formatting.

To address this issue, and to unify output styles of different tools I’m using (ChatGPT as my daily driver, Gemini for work, and Amp as my coding agent), I drafted a minimal formatting guide as follows:

Shared formatting rules:

  • Use consistent formatting within the same response
  • Insert spaces between English words and CJK characters
  • Always specify the language for syntax highlighting when using fenced code blocks
  • Do not use horizontal dividers (<hr /> or ---) unless they add clear structural value, especially directly before headings
  • For list items, do not use a period at the end unless the item is a complete sentence

For chat responses:

  • Use “Sentence case” for chat names (auto-generated chat titles) and all section headings (capitalize the first word only), never use “Title Case” in such circumstances
  • Use heading levels sequentially (h2, then h3, etc), never skip levels; Introductory paragraphs may be needed before the first heading in chat responses; Never use h1 for chat responses
  • Avoid filler, praise, or conversational padding (for example “Good question”, “You’re absolutely right”)

For document generation and editing:

  • Use “Title Case” for top-level headings (e.g. h1), typically only once in a document, and “Sentence case” for section headings (capitalize the first word only)
  • Use heading levels sequentially (h2, then h3, etc), never skip levels

I apply these rules to the custom instructions setting in ChatGPT and to AGENTS.md for my coding agent.

Custom instructions setting in ChatGPTCustom instructions setting in ChatGPT

#TECH8 Dec 24, 2025
Dec 23, 2025

GLM 4.7 and MiniMax M2.1. Chinese AI labs first caught the world’s attention with the DeepSeek models in late 2024. Then in the second half of 2025, we saw a wave of Chinese open-source models like GLM 4.6, MiniMax M2, and Kimi K2. People like these models for their low price, open weights, and solid performance — just slightly below state-of-the-art proprietary models1.

Today, the updated GLM 4.7 and MiniMax M2.1 dropped on the same day. As public holidays approach in the US, Chinese AI labs keep pushing forward, making good use of the time 😉

AI is a rapidly changing field. I’m not one to chase every new model release, though I do find myself following this topic more recently. I’m still learning these concepts and trying to find a pragmatic way to use AI tools. I use ChatGPT as my daily driver, Gemini for work (my company subscribes to it), and Amp as my coding agent.

I may not post about every model release in the future, but here are the models on my radar:

  1. For example: Vercel CEO Guillermo Rauch’s post on X, T3 Chat creator Theo’s post on X

#TECH7 Dec 23, 2025
Page 1 / 1