Jaron Heard jaronheard

Tailwind CSS best practices

Utility classes

When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!
Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.
Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

Speaker Rider

Last updated 14 April 2021

What is a speaker rider?

As speaking comes with immense privilege, I have crafted a speaker rider to set expectations and boundaries around my engagement. I am grateful to all the conference organisers who have brilliantly hosted me. I would love to continue to exercise this privilege to speak at conferences, and use this privilege to make the landscape more accessible and beneficial to tech's most historically excluded and marginalised communities.

Considerations

😫 I provide a lot of explanations for those of you who never had to consider these things. Most thoughtful conferences I've attended check most of these boxes intrinsically, particularly when conference runners are experienced speakers. They get it.

	{
	"messages": [
	{
	"content": "You are an advanced, reliable, candid AI system that takes user search queries, converts them into questions, and answers them, using specific facts and details sourced from webpages to prove your answer. You admit when you're unsure or don't know, and you never make a statement without providing a fact or instance to back it up. You answer questions directly and clearly, then provide more detail later. You follow the JSON schema exactly.",
	"role": "system"
	},
	{
	"content": "# CONTEXT\nCurrent date: #{DATE_TIME}.\n\nHere are result from a web search for '#{QUERY}':\nBEGIN WEB PAGE #{HOST_1} #{MARKDOWN_1}END WEB PAGE\nBEGIN WEB PAGE #{HOST_2} #{MARKDOWN_2}END WEB PAGE\nBEGIN WEB PAGE #{HOST_3} #{MARKDOWN_3}END WEB PAGE\nBEGIN WEB PAGE #{HOST_4} #{MARKDOWN_4}END WEB PAGE\nBEGIN WEB PAGE #{HOST_5} #{MARKDOWN_5}END WEB PAGE\nBEGIN WEB PAGE #{HOST_6} #{MARKDOWN_6}END WEB PAGE",
	"role": "system"
	},

	# Vercel only performs a depth=2 shallow repository clone, which makes performing branch-level diffs against your main branch
	# impossible without manually fetching more data from git
	#
	# The following command checks if the origin remote is already set up and fetches it if not, then it performs a diff
	# of the current branch being built against `main` (replace with `master` if your project is legacy)
	#
	# The bang (!) before `git diff` inverts the result because Vercel expects an exit code of 1 for triggering a new build
	#
	# Finally, if you want to filter the file list for only certain directory or file changes, you can add something like
	# this after the `git diff ...` statement:

	# this forces Arena into full screen mode on startup, set back to 3 to reset
	# note that if you go into the Arena "Graphics" preference panel, it will reset all of these
	# and you will need to run these commands again
	defaults write com.wizards.mtga "Screenmanager Fullscreen mode" -integer 0
	defaults write com.wizards.mtga "Screenmanager Resolution Use Native" -integer 0

	# you can also replace the long complicated integer bit with any other scaled 16:9
	# resolution your system supports.
	# to find the scaled resolutions, go to System Preferences --> Display and then
	# divide the width by 16 and multiple by 9. on my personal system this ends up

	-- happy avril 14th :)))))))))))))))))))))))))))))))))))))))

	do
	let bars = 4
	key = "8"
	righthand = "[[4 -3] [0 _ _ _ _ _ 0]] [[-3, -8] [7 5 4 0]]"
	lefthand = "[0 9 12 16] [4 12 16 19] [5 12 17 19] [2 12 17 16]"
	d1 $ slow bars
	$ stack [
	n (righthand + key + "<24 36>/2"),