npm install --save-dev vitest jsdom- React Testing Library
npm install --save-dev vitest jsdom| #!/usr/bin/python | |
| # Python port of keepass2john from the John the Ripper suite (http://www.openwall.com/john/) | |
| # ./keepass2john.c was written by Dhiru Kholia <dhiru.kholia at gmail.com> in March of 2012 | |
| # ./keepass2john.c was released under the GNU General Public License | |
| # source keepass2john.c source code from: http://fossies.org/linux/john/src/keepass2john.c | |
| # | |
| # Python port by @harmj0y, GNU General Public License | |
| # |
How to build a production-ready, team-scoped deployment pipeline using fabric-cicd, Azure DevOps, and Fabric-native Variable Libraries
Microsoft Fabric has rapidly matured as an end-to-end analytics platform, but one area that still challenges many teams is how to operationalize deployments. Without a proper CI/CD strategy, teams resort to manual workspace promotion, inconsistent environments, and configuration drift between DEV, UAT, and PROD — exactly the kind of technical debt that slows data engineering teams down.
---
name: rubber-duck
description: Use when stuck on a problem — structured debugging: rubber duck, web research, AI consultation, then escalate.
version: 1.0
---
Invoke this skill when explicitly asked, or whenever you repeat the same approach, hit the same error twice, or fail to make progress after 2–3 attempts.
This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
| """ | |
| 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 |
| // big | |
| mat_picmip "2" | |
| r_rootlod "2" | |
| lod_transitiondist "200" | |
| r_3dsky "0" | |
| mat_antialias "0" | |
| mat_aaquality "0" | |
| mat_powersavingsmode "1" // 30fps lock but way less cpu usage | |
| // mcore |
| #define IM_A_LITTLE_POLYGLOT /* | |
| gcc $0 && ./a.out; exit | |
| */ | |
| /* | |
| 1. Save as foo.c | |
| 2. chmod +x foo.c | |
| 3. Run with ./foo.c | |
| */ |
Add this file to your AI assistant's system prompt or context to help it avoid common AI writing patterns. Source: tropes.fyi by ossama.is