Paul Esch-Laurent Pinjasaur

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
Select "Create new custom chat mode file"

`$HOME`, Not So Sweet `$HOME`

Preface
1 What is $HOME to you?
2 Setup
- 2.1 Linux
2.1.4 xdg-user-dirs

Open Source Business Challenges and Reality

Original Japanese note here.

Original Author: Rui Ueyama (creator of the mold linker)

Translated by @windowsboy111

Minimally edited by @lleyton

UPDATE: I am no longer employed by Verily and have subsequently started at Amazon. Most of my advice still holds with a few caveats.

Ever since starting a role at one of Google's sister companies under the Alphabet umbrella, I've had a number of people reach out to me requesting advice, suggestions, and guidance on interviewing and looking for tech jobs in general. Since I don't have time to respond to everyone, I thought I'd share my best advice in one doc. (Please note that I speak only on behalf of myself, and not on behalf of the company I work for.)

How should I prepare to interview at <company>?

This really depends on where you are in the job search process. If you're a year or more out, your focus should be on learning as much as you can at your current company or in school--no matter where you study or work, there is something you can gain from exploring the knowledge readily available to you from teachers and mentors in proximity to your current place in the world. Surround yourself with m

Had 15 github followers in 2019? You can get about $4kAUD of crypto for minimal effort.

Explain this scam

That's legitimately a good default position to hold, however, in this case, the free money is a function of time, and not only charity.

In February 2020, in order to promote Handshake (HNS) to developers, an airdrop was offered to any Github user with more than 15 followers. The Airdrop would give you 4246HNS, at the time worth around at $0.08USD per coin, for a total of $339.68USD, pretty generous!

Today, 4246HNS is worth around $4000 dollarydoos, and there are plenty of github users who haven't claimed theirs.

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

Automatically Empty Google Drive Trash

Adapted from https://www.amixa.com/blog/2019/04/05/automatically-empty-google-drive-trash/

Make sure you use Google's Chrome web browser for best results.
Open Chrome and go to www.google.com.
Make sure you are signed into your Google account. If not, sign in.
You should obviously have Google Drive account up and running.
Visit https://script.google.com/home and click NEW PROJECT
Clear out the default code that appears in the next window, and paste in the following:

	$ grep -P "^[ABCDEFabcdefOoIi]{6,6}$" /usr/share/dict/words \| tr 'OoIi' '0011' \| tr '[:lower:]' '[:upper:]' \| awk '{print "#" $0}'
	#ACAD1A
	#B0BB1E
	#DEBB1E
	#AB1DED
	#ACAC1A
	#ACCEDE
	#AC1D1C
	#BAB1ED
	#BA0BAB

	#!/usr/bin/env bash

	cd $(dirname $0)

	docker run --rm -it -v "$(pwd)":/home/rust/src -v cargo-git:/home/rust/.cargo/git -v cargo-registry:/home/rust/.cargo/registry -v "$(pwd)/target/":/home/rust/src/target ekidd/rust-musl-builder:nightly-2021-01-01 sudo chown -R rust:rust /home/rust/.cargo/git /home/rust/.cargo/registry /home/rust/src/target

	docker run --rm -it -v "$(pwd)":/home/rust/src -v cargo-git:/home/rust/.cargo/git -v cargo-registry:/home/rust/.cargo/registry -v "$(pwd)/target/":/home/rust/src/target ekidd/rust-musl-builder:nightly-2021-01-01 cargo build --release

	/*
	The https://trails.morcmtb.org/ site has way too much crap that I don't care about.
	I just want to quickly see what trails are open.
	This is a cloudflare worker that hits the trails API and builds a concise HTML view of the conditions.
	It could just be statically hosted javascript, but this was also an excuse to try out workers.
	*/
	addEventListener("fetch", event => {
	return event.respondWith(handleRequest())
	})