searls

#!/usr/bin/env bash

# Usage:
#
#   First, be sure you're running `git bisect start --no-checkout`, so you can
#   checkout the bisect head yourself and do some pre-flight stuff like rewind
#   migrations
#
#   $ git bisect good
#   Bisecting: 22 revisions left to test after this (roughly 5 steps)

searls

#!/usr/bin/env bash

# Useful when you want to git bisect in a rails app and know
# you need to `bin/rake db:migrate VERSION="SOMETHING"` before
# you check out the next commit so the database is in the right
# state, but you don't know what SOMETHING is.

# Usage:
#
# $ migration_version_at_ref <REF>

tenderlove

# Okasaki style Functional Red Black Tree
# https://www.cs.tufts.edu/comp/150FP/archive/chris-okasaki/redblack99.pdf
#
# leaves and root are black
# BST
# No red node has a red child
# Every path from the root to a leaf has the same number of black nodes

module RBTree
  class Leaf

conor-f

### github_heatmap_writer.py
#
# Overview:
#   This script will let you write short phrases on your Github contributions
# heatmap on your profile for a particular year. It does this by modifying the
# commit date/time.
#
# Usage:
#   - Make a Github repo (public or private) and clone it locally.
#   - Modify this script to specify what year you want to display on and what

infews

#!/usr/bin/env ruby

# Smarter be for ruby projects that prioritizes local project binstubs
# - uses zsh when needed, assuming MacOS Catalina or later
# - save on your path
# - drop the .rb
# - chmod +x
# - always type `be <command>` and the right thing should happen
#
# - inspired by Justin Searls (@searls)

tomhicks

const audioCtx = new window.AudioContext();
const oscillator = audioCtx.createOscillator();
oscillator.connect(audioCtx.destination);
oscillator.type = "sine";

let numItems = 0

oscillator.frequency.setValueAtTime(
  1,
  audioCtx.currentTime

tomhicks

/*
Copy this into the console of any web page that is interactive and doesn't
do hard reloads. You will hear your DOM changes as different pitches of
audio.

I have found this interesting for debugging, but also fun to hear web pages
render like UIs do in movies.
*/

const audioCtx = new (window.AudioContext || window.webkitAudioContext)()

searls

Here's a neat trick.

I treat my git clones as disposable between computers, but keep my project-specific dotfiles (usually containing environment variables, individual configurations, and so on) synced across devices in iCloud. Then, this script is just a matter of adding symlinks for each of the dotfiles I've saved for each of my projects to each of their clones.

So if my dotfiles are saved like this:

$ tree -a ~/icloud-drive/dotfiles/project-dotfiles/
/Users/justin/icloud-drive/dotfiles/project-dotfiles/
├── searls

munificent

#include <time.h> //  Robert Nystrom
#include <stdio.h> // @munificentbob
#include <stdlib.h> //     for Ginny
#define  r return    //    2008-2019
#define  l(a, b, c, d) for (i y=a;y\
<b; y++) for (int x = c; x < d; x++)
typedef int i;const i H=40;const i W
=80;i m[40][80];i g(i x){r rand()%x;
}void cave(i s){i w=g(10)+5;i h=g(6)
+3;i t=g(W-w-2)+1;i u=g(H-h-2)+1;l(u

amrabdelwahab

What is wrong with Ruby? - Research project

Introduction

Our industry has a tendency to follow hypes without backing it with solid constructive claims. Over the past few years, trashing Ruby was one of these hypes, I also find that the so called "Senior Engineers" tend to promote hypes to appear more opinionated without really trying to explain the logical claims behind it, leaving the community beginners and new joiners really confused.

Goals of the project

• Solidifying the claims behind the hype (Because I believe it stems from real problems, not just an empty hype) and eventually passing this to Ruby core team as an input from the community.
• Explain these problems in a much simpler language to beginners and community new joiners.

Initial Focal points