drewcsillag

Feature Implementation Workflow

Task: $ARGUMENTS

---

Setup

1. Derive a kebab-case slug from the task description (e.g., "rename an SD" → rename-sd)
2. Create and checkout git branch: {slug}

karpathy

# -----------------------------------------------------------------------------
# AI-powered Git Commit Function
# Copy paste this gist into your ~/.bashrc or ~/.zshrc to gain the `gcm` command. It:
# 1) gets the current staged changed diff
# 2) sends them to an LLM to write the git commit message
# 3) allows you to easily accept, edit, regenerate, cancel
# But - just read and edit the code however you like
# the `llm` CLI util is awesome, can get it here: https://llm.datasette.io/en/stable/

gcm() {

Hellisotherpeople

You probably don't know how to do Prompt Engineering

(This post could also be titled "Features missing from most LLM front-ends that should exist")

Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".

Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.

Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system

KayLerch

module.exports = Object.freeze({
    translation: {
        welcome: 'Howdy',
        images: [ 
            {
                background: 'https://image/en-US.png' 
            },
            {
                background: 'https://image/en-US2.png' 
            },

luciopaiva

#!/usr/bin/env node

const
    path = require("path"),
    fs = require("fs");

/**
 * List all files in a directory recursively in a synchronous fashion
 *
 * @param {String} dir

Piasy

brew options ffmpeg

brew install ffmpeg \
--with-chromaprint \
--with-fdk-aac \
--with-fontconfig \
--with-freetype \
--with-frei0r \
--with-game-music-emu \
--with-libass \

lucasweb78

#!/bin/bash

wget -c --no-cookies --no-check-certificate --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" "http://download.oracle.com/otn-pub/java/jdk/8u77-b03/jdk-8u77-linux-x64.rpm" --output-document="jdk-8u77-linux-x64.rpm"

sudo rpm -i jdk-8u77-linux-x64.rpm

sudo alternatives --install /usr/bin/java java /usr/java/default/bin/java 20000

export JAVA_HOME=/usr/java/default

sebsto

sudo wget http://repos.fedorapeople.org/repos/dchen/apache-maven/epel-apache-maven.repo -O /etc/yum.repos.d/epel-apache-maven.repo
sudo sed -i s/\$releasever/6/g /etc/yum.repos.d/epel-apache-maven.repo
sudo yum install -y apache-maven
mvn --version

pospi

/**
 * Service to manage geoJSON layering with Leaflet.js' angular directive, which only allows 1 set of geoJSON data.
 *
 * Assuming you have a leaflet directive with its 'geojson' attribute set to `geojson`, usage is as follows:
 *     var layers = new GeoJSONLayers();
 *
 *     layers.addLayer('myLayer', geoJSON, function(feature) { return { fillColor: '#00F' }; });
 *     $scope.geojson = layers.get();
 *
 *     layers.removeLayer('myLayer');

natelandau

#  ---------------------------------------------------------------------------
#
#  Description:  This file holds all my BASH configurations and aliases
#
#  Sections:
#  1.   Environment Configuration
#  2.   Make Terminal Better (remapping defaults and adding functionality)
#  3.   File and Folder Management
#  4.   Searching
#  5.   Process Management