Skip to content

Instantly share code, notes, and snippets.

@HimDek
HimDek / Install Android apps or apk files in Windows using Windows Subsystem for Android (No Emulator).md
Last active March 12, 2026 09:03
This Guide will show you how to install and run apk files or Android apps in any Edition of Windows 11 using Windows Subsystem for Android. WSA or Windows Subsystem for Android is a Tool that allows Windows to run Android Apps directly without using any emulator.

Install Android apps or apk files in Windows using Windows Subsystem for Android

WSA or Windows Subsystem for Android is a Tool that allows Windows to run Android Apps directly without using any emulator. The problem is Windows Subsystem for Android is currently only available through preview via the Beta Channel of the Windows Insider Program. But if you follow my guide, you don't have to be in Windows Insider Program to try it out. The only thing you need is Windows 11 installed and some patience.

Prerequisites:

  • Windows Subsystem for Android or WSA must be Installed.

Click here to view the guide that shows how to install Windows Subsystem for Android in any Edition of Windows 11 (including Windows 11 Home) non Inider or stable release.

How to Install Android Apps or apk files in Windows Subsystem for Android:

@andriyudatama
andriyudatama / VS Code Disable GPU Acceleration
Last active March 12, 2026 09:02
Disable Hardware Acceleration (GPU) on Visual Studio Code
Visual Studio Code frequently crashes linux. Using NVIDIA GPU
1. Open command pallete (Ctrl + Shift + P)
2. Enter "Preferences: Configure Runtime Arguments"
3. Add config: "disable-hardware-acceleration": true
4. Restart VS Code

Migrating Prompts from Autoregressive to Diffusion LLMs

A practical guide based on migrating 18 production AI operations (~175 test cases) from GPT-4.1-mini to Mercury 2, a diffusion-based LLM. Every rule below was learned from a real failure and validated with automated tests.


How Diffusion LLMs Differ

Autoregressive models (GPT, Claude, Gemini) generate one token at a time, left to right. Each token sees everything before it. They follow instructions well because they process them sequentially while generating.

@mohanpedala
mohanpedala / bash_strict_mode.md
Last active March 12, 2026 08:56
set -e, -u, -o, -x pipefail explanation
@mmozeiko
mmozeiko / debugger_example.c
Last active March 12, 2026 08:56
example for debug api & call stack unwinding & symbol lookup
#include <windows.h>
#include <dbghelp.h>
#include <stdio.h>
#include <assert.h>
#pragma comment (lib, "dbghelp")
int main()
{
STARTUPINFOW si = { .cb = sizeof(si) };
@adhishthite
adhishthite / autoexp-generic.md
Created March 7, 2026 21:28
autoexp — Autonomous Experimentation Loop. Generalized from Karpathy's autoresearch for any quantifiable metric project.

autoexp — Autonomous Experimentation Loop

Generalized from Karpathy's autoresearch. Same loop, any domain.


The Idea

An AI agent runs an infinite hill-climbing loop: modify → run → measure → keep or revert → repeat. No human in the loop. Wake up to a TSV of completed experiments.

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

  • Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
  • Select "Create new custom chat mode file"
"""
The most atomic way to train and run inference for a GPT in pure, dependency-free Python.
This file is the complete algorithm.
Everything else is just efficiency.
@karpathy
"""
import os # os.path.exists
import math # math.log, math.exp

Proxmox VE tips

Just some tips I gathered over time. All in one easily reachable place so I can share it wherever I want.

Please note that unless you see a shebang (#!/...) these code blocks are usually meant to be copy & pasted directly into the shell. Some of the steps will not work if you run part of them in a script and copy paste other ones as they rely on variables set before.
The { and } surrounding some scripts are meant to avoid poisoning your bash history with individual commands, etc. You can ignore them if you manually copy paste the individual commands.
I chose to write things "in the open" that way so there's still some control and things don't become a black box.

Table of contents