veekaybee

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

Pre-Transformer Models

gremau

Trello Parser

Download

Open a terminal, run this:

sudo curl https://gist.githubusercontent.com/gremau/290ab394c9bf2d6d03c18444ff60c225/raw/trello-parser.py -o /usr/local/bin/trelloparse && sudo chmod +x /usr/local/bin/trelloparse

Usage

$ trelloparse -h

usage: tp [-h] input output

wbotelhos

require 'sidekiq/api'

# 1. Clear retry set

Sidekiq::RetrySet.new.clear

# 2. Clear scheduled jobs 

Sidekiq::ScheduledSet.new.clear

fogleman

import turtle

def turn(i):
    left = (((i & -i) << 1) & i) != 0
    return 'L' if left else 'R'

def curve(iteration):
    return ''.join([turn(i + 1) for i in range(2 ** iteration - 1)])

if __name__ == '__main__':

sasaki-shigeo

class Turtle {
  float x = 0;
  float y = 0;
  float dir = 0;
  boolean pen_down = false;
  int weight = 1;
  color pen_color = #000000;
  
  Turtle(float x, float y, float dir) {
    this.x = x;

zsup

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.

tonycoco

require "spec_helper"

describe ExampleController do
  context "GET #index" do
    let(:resources) { FactoryGirl.create_list(:resource) }

    before do
      get :index
    end

nataliefreed

// Turtle Graphics in Processing
// Natalie Freed, February 2013
// This program shows another way to think about moving
// through Processing's coordinate system. Instead of placing
// points on a grid, you can imagine yourself as being somewhere
// on the grid, facing a direction. You can move forward or turn.
// The drawn line follows behind you.

PVector loc; //current location
float orientation; //current orientation

imsickofmaps

How we use git-flow

The commands

First make sure you have a develop and master branch. If you only have develop run

$ git checkout -b master

Make it work locally

willurd

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000