
Don't follow bots, just build em' 🔨 | @visitalphatown
give(r)
Joined August 2022
- Tweets3.2K
- Following2.2K
- Followers2.8K
- Likes21K
Pinned Tweet
I'm reviving the dead alpha server I created over three years ago.
There's enough people that give a shit about it and frankly, Alphatown had a lot more impact than I originally thought it would.
Especially for people around the world in places that don't tend to have the same level of economic opportunity as the United States.
Alphatown will be an incubator and pass-through for creative ideas. It'll be a jumping pad for hardworking people with integrity who want to do something cool within the crypto-AI space.
We're small and dainty, but don't underestimate what a group of aligned individuals from around the world can accomplish
AT/OUT
Replying to @visitalphatown
Everything we've accomplished as an Alpha group and more importantly community.
Our beginnings have always been humble and community-first. We've prided ourselves in being ethical and giving back to the community in an effort to build good will within this space. (2/5)
Sundayalpha 👾 retweeted
vocal stims run the world bro if you don't have a vocal stim strategy rn you're going to get destroyed
Sundayalpha 👾 retweeted
im deadass max short rn and i read shit like this and i start shaking
i just know how this goes
tmrw nvidia is gonna cure cancer then iran & trump will hug and sing hyperliquid in harmony and im just gonna close for breakeven
.@YieldFields_RH reveal is now just over 24 hours away!!
22nd Oct - 2pm UTC
Floor has pulled back a little from 1.3ETH back to 1.064 ETH, with only 169 (5.1%) listed
Will be interesting to see how the rarity will reprice, asking @bot based on all the info I’ve loaded it up regarding known “utility”, suggestions of revealed floors are :
🌌 Astral (Mythic): 111 = 3.50-6TH
✨ Radiant (Legendary): 222 = 2-3TH
☣️ Blight (Epic): 555 = 1.3-1.6TH
❄️ Frost (Rare): 888 = 1.0-1.2TH
🌿 Meadow (Common): 1,557 = 0.8-0.95ETH
Not sure if I agree here, honestly predicting floors is not my strong suit!
I’m just ready to start getting the game started!
Sundayalpha 👾 retweeted
Delete your CLAUDE.md. Not edit it, not trim it, delete the whole file, along with your skills and your hooks, and see what the model does without them. That's Boris Cherny's actual advice from a recent YC appearance, and the Claude Code team has apparently followed it internally enough times that roughly 80% of their own system prompts are gone. His reasoning: most of those rules patched a weakness in whatever model you ran six or twelve months ago. Newer models often don't have that weakness anymore, so the instruction that used to help is now just constraining a more capable model for no reason. His method is almost embarrassingly plain. Delete everything, work normally for a while, watch where the model actually goes off track, add back exactly one instruction when a mistake repeats, and run the whole cycle again at the next major model release. Keep security and compliance rules. Keep the project quirks a model genuinely can't infer from reading the code. Cut folder structures, dependency lists, and architecture summaries, since a capable model can read those off the repo itself faster than it can read your stale description of them.
This is the same problem the rest of the field keeps rediscovering under different names. Anthropic's own long context guidance, OpenAI's notes on attention tradeoffs inside big windows, and Microsoft Research's GraphRAG papers all circle the same fact: a pile of context that only grows, whether it's a system prompt, a vector store, or a knowledge graph, degrades the thing using it, because stale facts sit next to current ones with no signal about which one wins. DeepSeek Harness takes a different structural swing at the same target, building its agent runtime out of swappable plugins so a stale capability gets replaced instead of buried under new instructions.
What strikes me is how little of this is about model capability and how much is housekeeping nobody assigned themselves. Most teams have a deprecation policy for their actual code. Almost nobody has one for the three paragraphs pasted into an agent's instructions eight months ago and never looked at again. How long is your CLAUDE.md, and when did you last delete anything from it?
teapawt.org/suraj_sharma14/status/…
The creator of Claude Code just told everyone to delete their CLAUDE.md.
Not a typo.
Boris Cherny, at YC:
"Every 6 months delete your CLAUDE.md delete your skills, delete your hooks. See what the model does and it might surprise you."
His reasoning:
• Your old rules were fixing weaknesses of older models
• New models don't have those weaknesses anymore
• So your instructions might now be making Claude worse
The method:
1. Delete CLAUDE.md, skills and hooks
2. Work normally and watch where Claude goes off track
3. Add back ONE instruction only when a mistake keeps happening
4. Repeat after every major model release
What to keep:
• Security and compliance rules
• Project quirks Claude can't figure out from the code
What to cut:
• Folder structures, dependency lists, architecture summaries
• Anything Claude can learn by reading your repo
Most people keep adding rules.
The person who built the tool is removing them.
Bookmark this. How long is your CLAUDE.md?
Sundayalpha 👾 retweeted
My mind is blown by how far ahead Apple is with local LLMs. The new Mac Studio M5 Ultra will have a 512 GB model for around 15-20k. You can chain 6 of them together using thunderbolt 5 and this have over 3 TB of ram and a massive amount of CPU and GPU cores. This means you can run a frontier model with over 2 trillion parameters locally for around 100kish. Nivida is around 500k for the same capability.
Sundayalpha 👾 retweeted
there’s a ridiculous trend going viral on tiktok right now called “malfoid” a harry potter fanfic story where draco malfoy is a girl and in an enemies-to-lovers story line with harry
the AI videos are so good and it’s actively shifting AI sentiment on tiktok to positive (was historically super negative)
Sundayalpha 👾 retweeted
Chinese bride gifts her partner a flagship GPU at wedding — he breaks down in tears
She handed him an ASUS ROG Astral RTX 5090 that costs around $12,000
Sundayalpha 👾 retweeted
If you learn AI Infrastructure Engineering, you will never be unemployed again.
Stage 1: Systems & GPU Foundations
- Learn: C++, Rust, CUDA memory hierarchy, PCIe vs NVLink, thread blocks and warp scheduling.
- Practice: Write a custom CUDA kernel for matrix multiplication from scratch and profile it against cuBLAS.
- Why: You cannot optimize what you do not understand at the silicon level.
Stage 2: Transformer Inference Physics
- Learn: Prefill vs Decode phases, arithmetic intensity, memory bandwidth bottlenecks, KV-cache math.
- Practice: Profile a HuggingFace model with Nsight Systems to identify the exact memory bottleneck during token generation.
- Why: LLM inference is almost always memory-bound, not compute-bound.
Stage 3: Modern Serving Engines & Batching
- Learn: vLLM, SGLang, PagedAttention, continuous batching, chunked prefill.
- Practice: Deploy a 70B model and tune chunk sizes to maximize throughput without starving decode requests during long-context prefills.
- Why: Naive batching leaves 60% of GPU VRAM wasted. PagedAttention fixes this.
Stage 4: KV-Cache & Memory Optimization
- Learn: Prefix caching, KV quantization, CPU offloading, multi-turn cache reuse.
- Practice: Build a routing proxy that directs requests with identical system prompts to the same replica to share KV blocks.
- Why: Reused cache is free speed. It can slash Time-To-First-Token (TTFT) by 80%.
Stage 5: Quantization & Compression
- Learn: FP8, INT4, AWQ, GPTQ, Sparsity, TensorRT-LLM calibration.
- Practice: Serve a model in FP8 vs FP16 and benchmark the exact perplexity drop against the latency and VRAM gains.
- Why: Quantization is the only way to fit frontier models on edge GPUs and protect your margins.
Stage 6: Kernel-Level Engineering
- Learn: Triton, FlashAttention, CUDA graphs, operator fusion.
- Practice: Write a fused Triton kernel for RMSNorm or Softmax and benchmark it against the native PyTorch implementation.
- Why: Python overhead kills inference. Fused kernels save milliseconds that compound at scale.
Stage 7: Distributed Inference & Parallelism
- Learn: Tensor parallelism, Pipeline parallelism, Expert parallelism (for MoE models).
- Practice: Shard a 405B parameter model across 8 nodes and measure the communication overhead between GPUs.
- Why: Single-GPU inference is dead for frontier models. You must master the shard.
Stage 8: Speculative Decoding
- Learn: Draft-target models, Medusa heads, acceptance rates, n-gram drafting.
- Practice: Build a pipeline where a local 3B model drafts tokens for a cloud 70B model to verify in parallel.
- Why: 2x decode speed at zero quality cost is the closest thing to a free lunch in inference.
Stage 9: Multi-Node & Hardware Interconnects
- Learn: NCCL, RDMA, InfiniBand, NVLink, Disaggregated Prefill/Decode architectures.
- Practice: Set up a multi-node cluster and profile the network latency of tensor parallelism across nodes vs within a single node.
- Why: Network latency is the new GPU bottleneck. Disaggregating prefill and decode is the 2026 meta.
Stage 10: Cluster Orchestration & GPU Scheduling
- Learn: Kubernetes GPU operators, Ray, Slurm, MIG (Multi-Instance GPU) partitioning, KEDA.
- Practice: Build a queue-based autoscaler that spins up spot GPUs based on pending inference requests and drains them when empty.
- Why: Idle H100s burn $3+/hr. FinOps and scheduling are now core infra responsibilities.
Stage 11: AI Gateways, Routing & Observability
- Learn: TTFT/ITL SLOs, semantic routing, DCGM metrics, OpenTelemetry for LLMs.
- Practice: Build a gateway that routes simple queries to a quantized local model and complex reasoning to a frontier API based on prompt complexity.
- Why: Routing protects your margins and DCGM metrics tell you when your GPUs are silently throttling.
Stage 12: Public Benchmarks & Teardowns
- Learn: Reproducible methodology, latency/throughput Pareto curves, cost-per-token analysis.
- Practice: Publish a teardown comparing vLLM vs SGLang vs TensorRT-LLM on your specific hardware with full configs.
- Why: Public proof of hardware mastery gets you hired instantly by top AI labs.
Wrappers are a commodity. AI Infrastructure is the physics of scale.
The modern AI Infra Engineer builds the silicon nervous system for global intelligence.
Bookmark and Repost!





















