Discover gists

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Commit Message Formats

Default

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

Public Datasets

Agriculture

U.S. Department of Agriculture's PLANTS Database
[U.S. Department of Agriculture's Nutrient

	DNG 1.4 Parser
	This tutorial describes how to build the Adobe DNG SDK on Linux.
	It generates the dng_validate C++ program that can parse any DNG images, a bit like a "Hello world" for DNG image processing.


	Adobe DNG SDK 1.4
	XMP SDK
	DNG SDK
	dcraw issue
	Compatibility issue

	class FKWC_Enable_Coupon {

	public function __construct() {

	add_filter( 'woocommerce_coupons_enabled', [ $this, 'enable_coupon' ], 99 );

	}

	public function enable_coupon( $status ) {
	if ( ! class_exists( '\FKCart\Plugin' ) ) {

	#!/bin/bash

	# Function to display usage information
	usage() {
	echo "Usage: $0 /path/to/input.mp4 [ /path/to/output_directory ]"
	exit 1
	}

	# Check if at least one argument (input file) is provided
	if [ $# -lt 1 ]; then

	<!--
	When an input element gets focused, iOS Safari tries to put it in the center by scrolling (and zooming.)
	Zooming can be easily disabled using a meta tag, but the scrolling hasn't been quite easy.

	The main quirk (I think) is that iOS Safari changes viewport when scrolling; i.e., toolbars shrink.
	Since the viewport _should_ change, it thinks the input _will_ move, so it _should_ scroll, always.
	Even times when it doesn't need to scroll—the input is fixed, all we need is the keyboard—
	the window always scrolls _up and down_ resulting in some janky animation.

	However, iOS Safari doesn't scroll when the input has opacity of 0 or is completely clipped.

	# train_grpo.py
	#
	# See https://github.com/willccbb/verifiers for ongoing developments
	#
	import re
	import torch
	from datasets import load_dataset, Dataset
	from transformers import AutoTokenizer, AutoModelForCausalLM
	from peft import LoraConfig
	from trl import GRPOConfig, GRPOTrainer

	:root {
	--ease-in-quad: cubic-bezier(.55, .085, .68, .53);
	--ease-in-cubic: cubic-bezier(.550, .055, .675, .19);
	--ease-in-quart: cubic-bezier(.895, .03, .685, .22);
	--ease-in-quint: cubic-bezier(.755, .05, .855, .06);
	--ease-in-expo: cubic-bezier(.95, .05, .795, .035);
	--ease-in-circ: cubic-bezier(.6, .04, .98, .335);

	--ease-out-quad: cubic-bezier(.25, .46, .45, .94);
	--ease-out-cubic: cubic-bezier(.215, .61, .355, 1);