<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>rzkmak</title><link>/</link><description>Recent blog posts on rzkmak</description><generator>Hugo (https://gohugo.io)</generator><language>en-us</language><managingEditor>rzkmak@outlook.com (Rizki Maulana Akbar)</managingEditor><webMaster>rzkmak@outlook.com (Rizki Maulana Akbar)</webMaster><lastBuildDate>Mon, 21 Sep 2026 00:00:00 Z</lastBuildDate><atom:link href="/tags/llm/index.xml" rel="self" type="application/rss+xml"/><item><title>LLM Fundamentals - Self Notes</title><link>/notes/llm-fundamentals-self-notes/</link><pubDate>Mon, 21 Sep 2026 00:00:00 Z</pubDate><author>rzkmak@outlook.com (Rizki Maulana Akbar)</author><description>
Work in progress. This note is a living summary of my LLM fundamentals study material. Sections will be added and refined over time.
Personal summary of the core ideas behind how LLM-based systems work: what actually goes into a request, why prompt order matters, how the context window budget works, what to do when prompting alone is not enough, and what the model file physically is.
# Anatomy of a Chat Request Every chat request is assembled from five components, and your application code is the assembler:</description><guid isPermaLink="true">/notes/llm-fundamentals-self-notes/</guid></item></channel></rss>