Spenser bananatron

Polyhedral Die Battle Odds

vs →	d4	d6	d8	d10	d12	d20
d4	37.5	25.0	18.8	15.0	12.5	7.5
d6	58.3	41.7	31.3	25.0	20.8	12.5
d8	68.8	56.3	43.8	35.0	29.2	17.5
d10	75.0	65.0	55.0	45.0	37.5	22.5
d12	79.2	70.8	62.5	54.2	45.8	27.5
d20	87.5	82.5	77.5	72.5	67.5	47.5

Here is a list of players to consider for the 2023 fantasy football season, along with their positions, based on various sources:

Top players to draft:

Christian McCaffrey, RB[1][2][3][4]
Dalvin Cook, RB[1][2][3][4]
Alvin Kamara, RB[1][2][3][4]
Derrick Henry, RB[1][2][3][4]
Travis Kelce, TE[1][2][3][4]
Tyreek Hill, WR[1][2][3][4]
Stefon Diggs, WR[1][2][3][4]

The Ownership Tax

When you buy something, you have to look at it, every day.

And when you’re sick of staring at it, stuff it in a closet, or somewhere further away.

What if when we bought our goods, we thought about this tax.

Perhaps we’d stop filling the basement until our foundation cracks.

Plant Intelligence and the Imaginal Realm (Alex)

Why we make things and why it matters (Sherman)

~~The Wisdom of Insecurity~~

~~The most Human Human~~

Built to Sell

Proposed Component Structure

This is an entry/discussion point for a suggestion which follows the first example on the react file structure page, but with more specificity, catered to what we are actually building. This ruleset prioritizes speed of development and context understanding over component conformity & isolation.

The general rules:

Our react front-end's job is to visually draw stuff on a web page. As a result, the file structure should match the structure of the visual behavior of our application.
Be explicit about which components can be shared outside of their domain/page and which can't (common folders exist on all domain levels).
Use your best judgement when you should/shouldn't extract things. We're all grown ups and we're all rowing in the same direction. We have designs and we'll have good guesses about what will be reused and what won't.
We have a convention on words which indicate a page's primary function - maybe this looks

Who is it for?
Who is it not for?
How will you know when it's done?
What are you not willing to compromise on?
Who's involved at the beginning and whose involved at the end?

	require 'sinatra'
	require 'socket'
	require 'timeout'

	# Configuration
	set :bind, '0.0.0.0'
	set :port, 4567

	# Helper to check server status
	def quake_server_status(host = 'localhost', port = 27960, timeout = 2)

	/! TACHYONS v4.12.0 \| http://tachyons.io /
	/*
	*
	* ________ ______
	* ___ __/_____ _________ /______ ______________________
	* __ / _ __ `/ ___/_ __ \_ / / / __ \_ __ \_ ___/
	* _ / / /_/ // /__ _ / / / /_/ // /_/ / / / /(__ )
	* /_/ \__,_/ \___/ /_/ /_/_\__, / \____//_/ /_//____/
	*
	* ---- LITE VERSION (BLUEPRINT SPECIAL) ----

	<html>
	<title>Devise Token Auth Tester</title>
	<body>

	<button onclick=window.sendTestRequest()>Test</button>

	<script>

	window.requestDelay = 2200
	window.apiUrl = `https://localhost:3000/api/whatever`

	// Copy and paste the code below in the javascript console

	document.getElementsByTagName("video")[0].playbackRate = 3
	// (Replace '3' with any value; 2x is current cap through the Youtube UI)