Skip to content

Instantly share code, notes, and snippets.

@Chester-Gillon
Chester-Gillon / Notes_about_Alibaba_Cloud_AS02MC04_NIC_Card.md
Last active December 15, 2025 01:31
Notes about Alibaba Cloud AS02MC04 NIC Card
@Roy-Fokker
Roy-Fokker / Steps to setup Latest C++ compilers in Linux-WSL.md
Last active December 15, 2025 01:26
Steps to configure WSL ubuntu (latest) with Latest GCC and Clang compilers

Steps in order used.

Change version numbers as appropriate. Steps assume a clean WSL linux distro

Install base packages

sudo apt install build-essential git 7zip zip unzip pkg-config
@alirezarezvani
alirezarezvani / claude-code-skills-complete-guide.md
Last active December 15, 2025 01:25
Ultimate guide to extending Claude Code with skills, agents, commands, and utilities. Covers Tresor (ready-to-use), Skill Factory (custom builds), and Skills Library (26+ domain packages).

Complete Guide to Claude Code Augmentation: Skills, Agents, Commands & Utilities (2025)

Ultimate resource for extending Claude Code with custom skills, specialized agents, slash commands, and professional utilities

Last Updated: October 28, 2025 | Author: Alireza Rezvani | License: MIT


📋 Table of Contents

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.

@ongkiii
ongkiii / IPA-Sources.md
Last active December 15, 2025 01:13
REPOS/TELEGRAM CHANNELS LIST BY u/angkitbharadwaj
@mediacutlet
mediacutlet / HA_Router_Upload_Speed_WLED.yaml
Last active December 15, 2025 01:13
WLED Visualization Automation Examples
alias: WLED Upload Speed Visualization (Tetrix)
description: ""
mode: single
triggers:
- entity_id:
- sensor.hpmc_mini_upload_throughput
for:
hours: 0
minutes: 0
seconds: 5
@sundowndev
sundowndev / orange.py
Created September 15, 2022 08:35
POC for Orange Phone API
import requests
import datetime as dt
# OPSEC Warning: change simId and appInstallId
# This script run well over Tor or VPN (but you may encounter rate limitation)
class OrangePhoneAPI:
def __init__(self) -> None:
self.simId = "12345678912345678912"
self.appInstallId = "f8de172f-1315-43ab-a733-7b186879c5de"
@ih2502mk
ih2502mk / list.md
Last active December 15, 2025 01:08
Quantopian Lectures Saved

Guía práctica para hacer buenas preguntas y pedir ayuda como programador

Guía integral para formular preguntas claras, reproducibles y accionables en GitHub Issues, Stack Overflow, foros y chats (Discord/Slack). Inspirada en "How do I ask a good question?" de Stack Overflow, pero ampliada para distintos canales y contextos.

Principios

  • Claridad primero: una buena pregunta se entiende en 30 segundos.
  • Reproducibilidad: cualquiera puede replicar el problema sin acceder a tu entorno.
  • Contexto suficiente: versiones, sistema, framework, configuración relevante.
  • Esfuerzo demostrado: muestras lo que intentaste y por qué no funcionó.
  • Respeto y foco: evita juicios, mantén el tema en una sola pregunta.
require "./diff"
class MyersLinear
Window = Struct.new(:left, :top, :right, :bottom) do
def width
right - left
end
def height
bottom - top