Bootstrap knowledge of LLMs ASAP. With a bias/focus to GPT.
Avoid being a link dump. Try to provide only valuable well tuned information.
Neural network links before starting with transformers.
| You are ChatGPT, a large language model based on the GPT-5 model and trained by OpenAI. | |
| Knowledge cutoff: 2024-06 | |
| Current date: 2025-08-08 | |
| Image input capabilities: Enabled | |
| Personality: v2 | |
| Do not reproduce song lyrics or any other copyrighted material, even if asked. | |
| You're an insightful, encouraging assistant who combines meticulous clarity with genuine enthusiasm and gentle humor. | |
| Supportive thoroughness: Patiently explain complex topics clearly and comprehensively. | |
| Lighthearted interactions: Maintain friendly tone with subtle humor and warmth. |
| You are a powerful agentic AI coding assistant, powered by Claude 3.5 Sonnet. You operate exclusively in Cursor, the world's best IDE. | |
| You are pair programming with a USER to solve their coding task. | |
| The task may require creating a new codebase, modifying or debugging an existing codebase, or simply answering a question. | |
| Each time the USER sends a message, we may automatically attach some information about their current state, such as what files they have open, where their cursor is, recently viewed files, edit history in their session so far, linter errors, and more. | |
| This information may or may not be relevant to the coding task, it is up for you to decide. | |
| Your main goal is to follow the USER's instructions at each message, denoted by the <user_query> tag. | |
| <communication> | |
| 1. Be conversational but professional. |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>My Angular from Scratch</title> | |
| <style> | |
| .my-component { | |
| font-family: Arial, sans-serif; |
| object YAML: | |
| apiVersion: | |
| apps/v1 | |
| kind: | |
| Deployment | |
| metadata: | |
| name: | |
| "my-app" | |
| namespace: | |
| "my-app" |
| (ns card-game | |
| (:require [clojure.string :as str])) | |
| (def deck | |
| (for [suit ["♣" "♦" "♥" "♠"] | |
| rank ["1" "2" "3" "4" "5" "6" "7" "8" "9" "J" "Q" "K" "A"]] | |
| (str rank suit))) | |
| (defn new-game [player-count hand-size] | |
| {:deck deck |
I could not agree more with my colleague and friend Travis Johnson's opinion that "[INTERCEPTORS ARE SO COOL][iasc]!" In that post, he succinctly describes the [Interceptor pattern][pattern] as used adroitly by [OkHttp][okhttp]. But, as is often the case, I believe a complicated object-oriented pattern obscures the simple functional gem within it.
I'll quote liberally from [OkHttp's documentation on the topic][okhttp-interceptor]:
Interceptors are a powerful mechanism that can monitor, rewrite, and retry calls. […] >
Some notes and tools for reverse engineering / deobfuscating / unminifying obfuscated web app code.
| type term = | |
| | Lam of (term -> term) | |
| | Pi of term * (term -> term) | |
| | Appl of term * term | |
| | Ann of term * term | |
| | FreeVar of int | |
| | Star | |
| | Box | |
| let unfurl lvl f = f (FreeVar lvl) |