dbtek

# venv_wrapper, manage all virtual environments under ~/.venv/
# Include the following in .bashrc / .bash_profile / .zshrc
# See https://gist.github.com/dbtek/fb2ddccb18f0cf63a654ea2cc94c8f19
#
# Usage:
# $ mkvenv myvirtualenv   # creates venv under ~/.venv/
# $ venv myvirtualenv     # activates venv
# $ deactivate            # deactivates venv
# $ rmvenv myvirtualenv   # removes venv
# $ rmvenv env1 env2      # removes multiple venvs

fanurs

# When to reinstall?
# - When VS Code cannot connect to remote server via the SSH extension
# - New extensions cannot be installed on remote server

# 1. Connect to remote server (without using VS Code, of course).

# 2. Remove the ~/.vscode-server directory
cd ~
rm -rf .vscode-server/

nicolasdao

Exhaustive list of SPDX (Software Package Data Exchange) licenses: https://spdx.org/licenses/

Table of Contents

• TL;DR - The BSD 3 Clause License Should Do
• In a Nutshell
• 3 Main Types of Open Source Licenses
  • 1. MIT
  • 2. Apache
  • 3. GPL
• The BSD License Case

arindam89

1. https://dev.to/trojanmocx/five-projects-carefully-unhinged-and-fully-deployed-2430
2. https://www.tech5ense.com/p/cloud-devops-5-core-skills-for-2026
3. https://www.xda-developers.com/used-notebooklm-to-learn-about-advanced-python-tricks-in-excel/
4. https://gist.github.com/Mihir2423/1ff5326e652b149b9cc800d4030ded95
5. https://medium.com/@Krishnajlathi/7-underused-rust-features-every-senior-developer-knows-7b8bb8da684f
6. https://medium.com/@ArkProtocol1/rust-webassembly-angular-the-upgrade-nobody-talks-about-c640c755e74b
7. https://www.infoq.com/news/2026/01/duckdb-iceberg-browser-s3/
8. https://medium.com/@lubnaaly12/i-posted-this-python-script-with-zero-expectations-then-it-exploded-4850c7b0ac04
9. https://medium.com/h7w/my-favorite-sql-tricks-for-cleaning-messy-real-world-data-c08683c8b386
10. https://thenewstack.io/technology-we-saved-and-tech-we-lost-in-2025/

darkmanlv

Плагины для онлайн просмотра:
1️⃣ Онлайн Stream: http://arkmv.ru/vod

2️⃣ Онлайн Prestige: https://bwa.to/plugins/prestige.js

3️⃣ Stream 2: http://llpp.in/v/vod.js

4️⃣ Онлайн Мод: https://nb557.github.io/plugins/online_mod.js

5️⃣ Онлайн MODS's: http://lampa.stream/modss

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.

ReaganS94

Teaching ChatGPT new tricks: a step-by-step guide to Skills

You've already spent some time learning how to write good prompts. You know that giving ChatGPT clear instructions, explaining what you want, and providing enough context can make a huge difference in the quality of its answers.

But there's a problem.

What happens when you find yourself writing the same instructions over and over again?

Imagine that every time you want ChatGPT to explain a difficult concept, you have to remind it to use simple language, provide examples, avoid unnecessary jargon, and ask you questions to check whether you've understood.

PeiceOfToast

iptv-org → Dispatcharr → Jellyfin — the complete hand-held walkthrough

What you end up with: a US TV channel lineup in Jellyfin, with a program guide that fills itself in every night, without you touching it again.

Who this is for: you've heard of Docker and Jellyfin but have never touched Dispatcharr. No Linux wizardry assumed. Every command is explained, and every step tells you what you should see before you continue.

Time: 30 minutes for a working setup (Quick Path), 60–90 minutes if you also build your own guide grabber (Proper Path). Most of that is waiting.

Difficulty: copy-paste. If a step ever looks wrong, stop and read the box under it — the failure modes are all covered.

phortuin

Based on this blogpost.

To sign Git commits, you need a gpg key. GPG stands for GNU Privacy Guard and is the de facto implementation of the OpenPGP message format. PGP stands for ‘Pretty Good Privacy’ and is a standard to sign and encrypt messages.

Setting up

Install with Homebrew:

$ brew install gpg