bkono

// Beefed up version that includes multiple tools and a verbose flag for printing the dialogue along the way.
package main

import (
	"context"
	"encoding/json"
	"flag"
	"fmt"
	"math"
	"math/rand"

bkono

package main

import (
	"fmt"
	"log/slog"
	"net/http"
	"slices"
)

type (

bkono

GraphQL

GraphQL Schema

type Customer {
  id: ID!
  email: String!
}

bkono

import axios from "axios";

export default {
  name: "Typefully Create Draft",
  description:
    "Create a draft in Typefully. Supports unscheduled draft, or adding to next available slot.",
  key: "typefully_create_draft",
  version: "1.0.0",
  type: "action",
  props: {

bkono

function f -d "Fuzzy-find and open a file in current directory"
  set file (fzf --height 40% --info inline --border --reverse --preview 'bat {}')
  if test -n "$file"
    nvim $file
  end
end

bkono

// Package ptr implements a simple pointer instrumentation.
// As it is based on Go generics, the minimal Go version is 1.18.
// Credit to https://github.com/candiduslynx/ptr/ and https://gist.github.com/bkono/8f832566e6c2875d7cede15e46aa9d58
package ptr

// Deref will deref the pointer if it can, otherwise it will return either a fallback if provided, or a default value for T
func Deref[T any](pointer *T, fallback ...T) T {
	if pointer != nil {
		return *pointer
	}

bkono

Redirecting GitHub Pages after a repository move

The problem

You have a repository, call it alice/repo. You would like to transfer it to the user bob, so it will become bob/repo.

However, you make heavy use of the GitHub Pages feature, so that people are often accessing https://alice.github.io/repo/. GitHub will helpfully redirect all of your repository stuff hosted on github.com after the move, but will not redirect the GitHub Pages hosted on github.io.

The solution

bkono

                                    Cello Project

            Individual Contributor License Agreement ("Agreement") v1.0

Thank you for your interest in the Cello Project. In order to clarify the intellectual
property license granted with Contributions from any person or entity, Intuit Inc.
(Intuit), the current custodian of the Cello Project, must have a Contributor License
Agreement ("CLA") on file that has been signed by each Contributor, indicating
agreement to the license terms below. This license is for your protection as a

bkono

--- Actions ---
$Copy                                              <M-C>
$Cut                                               <M-X> <S-Del>
$Delete                                            <Del> <BS> <M-BS>
$LRU                                              
$Paste                                             <M-V>
$Redo                                              <M-S-Z> <A-S-BS>
$SearchWeb                                         <A-S-G>
$SelectAll                                         <M-A>
$Undo                                              <M-Z>

bkono

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