Liam Clancy metafeather

Human Native AI—written evidence (LLM0119) - House of Lords Communications and Digital Select Committee inquiry: Large language models https://committees.parliament.uk/writtenevidence/127523/pdf/

Apple, Nvidia, Anthropic Used Thousands of Swiped YouTube Videos to Train AI https://simonwillison.net/2024/Jul/18/youtube-captions/

✭Apple, Nvidia, Anthropic Used Thousands of Swiped YouTube Videos to Train AI | WIRED https://www.wired.com/story/youtube-training-data-apple-nvidia-anthropic/

✭Breaking Down What’s at Stake in Music’s AI Lawsuits

created

How To Use Bash Parameter Substitution Like A Pro

The $ character is used for parameter expansion, arithmetic expansion and command substitution. You can use it for manipulating and expanding variables on demands without using external commands such as perl, python, sed or awk. This guide shows you how to use parameter expansion modifiers to transform Bash shell variables for your scripting needs.

How To Use Bash Parameter Substitution Like A Pro
Setting Default Values

Parsing command-line arguments and flags

4th January 2019 | 7 minutes

Today's post is going to be a bit more complex if you're new to shell scripting, but something I found quite beautiful is how one can go about parsing command-line arguments and flags in shell scripting. It works by using a switch-case statement and the shift expression.

Let's take a look!

arguments.sh

Wrapper script to convert markdown-link-check stdout to lsp_json format for use by Trunk.io VSCode Extension

File locations:

<repo>/.markdown-link-check.json
/.trunk/bin/markdown-link-check.js

	// ==UserScript==
	// @name SlackChannelHide
	// @namespace http://metafeather.net/
	// @version 2024-10-31
	// @description You can hide and open "CHANNELS" on Slack Web Client using Ctrl+S
	// @author metafeather
	// @match https://app.slack.com/client/*
	// @icon https://www.google.com/s2/favicons?sz=64&domain=slack.com
	// @grant GM_addStyle
	// @run-at document-start

	# Global args
	ARG DEBIAN_VERSION="bullseye-slim"
	ARG GOLANG_VERSION="1.17"
	ARG NODE_VERSION="16"
	ARG PYTHON_VERSION="3.10"
	ARG RUBY_VERSION="3.1.0"


	############################
	# Base images

	<template xmlns:v-slot="http://www.w3.org/1999/XSL/Transform">
	<div id="graphiql" style="height: 100vh"></div>
	</template>

	<script>
	// Load GraphiQL React based UI within a Vue Component from CDN
	// ref: https://github.com/graphql/graphiql/tree/main/packages/graphiql#cdn-bundle
	const js = (id, url) =>
	new Promise((resolve, reject) => {
	if (document.getElementById(id)) {

	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 really have SREs and they make engi