Pavel Larkin plar

🧠 Ultimate LLM Codebase Brain Dump Prompt

This prompt is designed for GPT-5, Claude Opus 4.1, Cursor, Claude Code, and cursor-agent to perform a deep, structured analysis of any codebase without pasting the entire repo into chat.

It guides the LLM to:

Browse and discover the codebase using built-in repo tools
Read only the necessary files in intelligent order
Analyze the system at high, mid, and low levels
Identify features, their business purposes, how they work, and how they interact
Output a complete master knowledge document inside codebase-analysis-docs/

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Foundational Concepts

Pre-Transformer Models

Go (Golang) GOOS and GOARCH

All of the following information is based on go version go1.17.1 darwin/amd64.

GOOS Values

GOOS	Out of the Box
`aix`	✅
`android`	✅

What I Wish I'd Known About Equity Before Joining A Unicorn

Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.

This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

Effective Engineer - Notes

By Edmond Lau
Highly Recommended 👍
http://www.theeffectiveengineer.com/

What's an Effective Engineer?

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

	FROM python:3.7-slim-stretch AS build

	RUN \
	apt-get -q update \
	&& apt-get -q install -y --no-install-recommends \
	build-essential \
	libssl-dev \
	&& rm -rf /var/lib/apt/lists/* \
	&& pip install -U pip

	package main

	import (
	"fmt"
	"net"
	"os"
	"syscall"
	)

	const (

	import os, gi
	gi.require_version("Gst", "1.0")
	from gi.repository import GObject, Gst

	Gst.init(None)
	pipeline = Gst.Pipeline()

	# Variables.
	youtube_stream_key = "your_key_here"
	encoder_speed = "ultrafast"

	package main

	import (
	"crypto/tls"
	"golang.org/x/crypto/acme/autocert"
	"log"
	"net"
	"net/http"
	)