Skip to content

Instantly share code, notes, and snippets.

View anglinb's full-sized avatar

Brian Anglin anglinb

View GitHub Profile
@adtac
adtac / README.md
Last active November 29, 2025 09:51
Using your Kindle as an e-ink monitor

3.5 fps, Paperwhite 3
@adtac_

step 1: jailbreak your Kindle

mobileread.com is your best resource here, follow the instructions from the LanguageBreak thread

I didn't really follow the LanguageBreak instructions because I didn't care about most of the features + I was curious to do it myself, but the LanguageBreak github repo was invaluable for debugging

@arekmaz
arekmaz / prisma-effect.ts
Created October 27, 2023 14:59
prisma + effect-ts integration - client which returns effects instead of promises
import { db } from "../services/db.server";
import { Data, Effect } from "effect";
import type { PrismaClient } from "@prisma/client";
import type {
PrismaClientKnownRequestError,
PrismaClientUnknownRequestError,
PrismaClientRustPanicError,
PrismaClientInitializationError,
PrismaClientValidationError,
} from "@prisma/client/runtime/library";
@veekaybee
veekaybee / normcore-llm.md
Last active December 7, 2025 16:13
Normcore LLM Reads

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Foundational Concepts

Screenshot 2023-12-18 at 10 40 27 PM

Pre-Transformer Models

@rain-1
rain-1 / GPT-4 Reverse Turing Test.md
Last active July 10, 2025 23:15
GPT-4 Reverse Turing Test

The reverse turing test

I asked GPT-4 to come up with 10 questions to determine if the answerer was AI or human.

I provided my own answers for these questions and I also asked ChatGPT to answer them.

The result is that GPT-4 was able to correctly differentiate between AI and Human.

@belgattitude
belgattitude / ci-yarn-install.md
Last active October 14, 2025 07:43
Composite github action to improve CI time with yarn 3+ / node-modules linker.
@Fanna1119
Fanna1119 / countries.js
Created October 2, 2022 15:13
object literal for country info using ISO 2 as key
const c = {
"AF": {
"Country": "Afghanistan",
"Alpha-2 code": "AF",
"Alpha-3 code": "AFG",
"Numeric code": 4,
"Latitude (average)": 33,
"Longitude (average)": 65,
"emoji_flag": "🇦🇫"
},
@oliveira-andre
oliveira-andre / enable_wol.md
Last active March 26, 2025 08:45
how to enable wake on lan in mac os and linux to power on your pc by alexa

MAC OS

  • open system preferences
  • open energy saver
  • click on power adapter
  • enable the wake for wi-fi network

this should work only on sleep of mac

Linux

@mjmenger
mjmenger / .bash_aliases
Last active May 1, 2025 22:52
bash aliases I like to have available
# Terraform aliases
# adding time to the commands because I'm very interested
# in how long these activities take with more complex builds
# across disparate platforms
alias tfi='terraform init'
alias tfp='time terraform plan'
alias tfa='time terraform apply'
alias tfaa='time terraform apply -auto-approve '
alias tfd='time terraform destroy'
alias tfda='time terraform destroy -auto-approve '
@lava
lava / tls_reverse_shell.md
Created February 24, 2020 17:59
CI Debugging with a TLS reverse shell

Interactive Debugging on Github Actions

Did you ever run into some issue where a job would behave slightly different in you CI environment than on your local machine? Did you ever wish you could run just a few commands in a shell on your build machine?

These are, of course rhetorical questions. And if you're using Github Actions to run your CI jobs, you'll have noticed that this use case is not supported at all. Can't create a nice walled garden if anyone could just run a CI job, after all. There are some workarounds (e.g. https://github.com/nektos/act), but since they're not officially supported they can be a bit unstable. Also, even they usually don't reproduce the exact environment found on github's servers.

@rxgpt
rxgpt / nodejsperfproblems.md
Last active July 15, 2022 00:51
Sources of latency in Node.js, and how to diagnose them

I used to be responsible for several language agents at AppDynamics, including the Node.js agent. Here's what I learned (caveat: these notes came together in 2016-2017, and the Node world moves very quickly! The community is always adding new sources of telemetry and higher-level abstractions that make it easier to write good Node code.):

Diagnosing common performance problems in Node.js services

"Context" means the user request, route handler, middleware, 3rd-party module, helper, or callback where the problem is. (Many of the functions involved in a user request are anonymous, which means that further narrowing down context is a challenge).

The "best" signal for a particular problem is the one that detects the problem and rules out the most other possibilities (e.g., event loop max tick length can indicate several different problems, and there are better signals that would more quickly narrow down these specific problems).