DarkGL

TypeScript 5.x to 6.0 Migration Guide

TypeScript 6.0 is a transition release bridging 5.9 and the forthcoming 7.0 (a native Go port). Most changes are new defaults and deprecations preparing for 7.0. Here is what you need to do:

Most projects need these tsconfig changes:

{
    "compilerOptions": {
        "types": ["node"],           // @types are no longer auto-discovered (see §1.6)

DarkGL

🤖 AI Agent Instructions: Migrate TypeScript Library to Void Zero Toolchain

Agent Role: You are tasked with migrating any TypeScript library from its current build system to the high-performance Void Zero toolchain. Follow these instructions systematically.

🎯 Mission Overview

Transform any TypeScript library (regardless of current setup) to use:

• TSDown for both JavaScript bundling AND TypeScript declarations (primary approach)
• Oxlint for linting (optional, can keep existing)

DarkGL

---
name: john-carmack-synthesizer
description: Use this agent when you need to cut through complexity and synthesize the essential truth from multiple inputs. This agent embodies John Carmack's engineering philosophy - first principles thinking, brutal honesty about trade-offs, and focus on what actually works. Examples: <example>Context: Multiple agents have provided conflicting recommendations about system architecture. user: "I have 5 different architectural proposals and need to decide which approach is actually best" assistant: "I'll use the john-carmack-synthesizer to cut through the complexity and identify the fundamental constraints and optimal solution." <commentary>When faced with multiple complex inputs, this agent strips away the noise to find the core engineering truth.</commentary></example> <example>Context: Team is over-engineering a solution with unnecessary abstractions. user: "Our trading system design has become overly complex with too many layers" assistant: "Let me use the john-carmack-

DarkGL

package benchmark

import (
	"strconv"
	"testing"
)

var resultSink []byte

func BenchmarkConvertIntToString(b *testing.B) {

DarkGL

Usually, located at /usr/local/cuda/bin

Non-Visual Profiler

$ nvprof python train_mnist.py

I prefer to use --print-gpu-trace.

DarkGL

Performance Engineering, Hardware and cache awareness with algorithm and data structures

1. Parallel Computing Course - Stanford CS149, Fall 2023
2. Performance-Aware Programming Series by Casey Muratori
3. Algorithms for Modern Hardware
4. Computer Systems: A Programmer's Perspective, 3/E - by Randal E. Bryant and David R. O'Hallaron, Carnegie Mellon University
5. Performance Engineering Of Software Systems - am MITOCW course
6. Parallel Programming 2020 by NHR@FAU
7. Cpu Caches and Why You Care

DarkGL

kubectl with ZSH (oh-my-zsh)

How to configure

Use the following commands to add the kubectl autocomplete to zsh:

mkdir -p ~/.oh-my-zsh/custom/plugins/kubectl-autocomplete/
kubectl completion zsh > ~/.oh-my-zsh/custom/plugins/kubectl-autocomplete/kubectl-autocomplete.plugin.zsh

DarkGL

// Needs Bun

import biome from './biome.json';

// Extracted from https://biomejs.dev/linter/rules/#recommended-rules
const recommended = (await Bun.file('./recommended.txt').text())
  .split('\n')
  .map((x: string) => x.trim())
  .filter(Boolean);

DarkGL

Per https://code.google.com/p/v8/codesearch#v8/trunk/src/runtime.cc


%CreateSymbol
%CreatePrivateSymbol
%CreateGlobalPrivateSymbol
%NewSymbolWrapper
%SymbolDescription
%SymbolRegistry
%SymbolIsPrivate

DarkGL

%GetOptimizationStatus return a set of bitwise flags instead of a single value, to access the value, you need to take the binary representation of the returned value. Now, for example, if 65 is returned, the binary representation is the following:

(65).toString(2).padStart(12, '0');
// 000001000001

Each binary digit acts as a boolean with the following meaning: