Edinunzio

To set up a shared Git repository on a network share, you can follow these steps. This process assumes you have access to the network share, and all users who will interact with the repository have appropriate read/write permissions to the shared directory.

Steps to Set Up a Shared Git Repository on a Network Share:

1. Create the Repository Directory on the Network Share

First, navigate to your network share or mount it locally on your machine (this could be /mnt/network_share/ or Z:\network_share\ depending on your OS).

cd /path/to/network/share
mkdir my_project.git

karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

NicolasCARPi

VibeCoded AI-Slop License v1.0

Copyright (c) [YEAR] [AUTHOR]

This software, source code, documentation, configuration, generated artifacts,
and whatever else happened to end up in this repository (collectively, the
"Software") is released under the VibeCoded AI-Slop License v1.0.

1. Permission

mattpocock

agent-proxy — see the bloat in Claude Code's requests

A zero-dependency logging proxy that sits between Claude Code and the Anthropic API. It forwards every request untouched, streams the reply straight back (so the CLI is unaffected), and writes a readable Markdown document for each request — led by a ranked table of what is eating your context.

Run it

wanglf

How to use?

• Copy content of vsix-bookmarklet, create a bookmark in your browser.
• Navigate to the web page of the VS Code extension you want to install.
• Click the bookmark you just created, then click the download button.
  
• After download finished, rename the file extension to *.vsix.
• In VS Code, select Install from VSIX... in the extension context menu.
  

klaaspieter

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.

That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.

jboner

Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference                           0.5 ns
Branch mispredict                            5   ns
L2 cache reference                           7   ns                      14x L1 cache
Mutex lock/unlock                           25   ns
Main memory reference                      100   ns                      20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy             3,000   ns        3 us
Send 1K bytes over 1 Gbps network       10,000   ns       10 us
Read 4K randomly from SSD*             150,000   ns      150 us          ~1GB/sec SSD

evildaemond

Tools

https://github.com/evilmog/ntlmv1-multi

https://github.com/lgandx/Responder

https://github.com/projectdiscovery/notify

How To

geoffreylitt

name	explain-diff-html
description	Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

Explain Diff

Please make me a rich, interactive explanation of the specified code change.

It should have these sections: