Discover gists

Thinking Architecturally

Source Resources

Thinking Architecturally - Nathaniel Schutta - youtube
Thinking Architecturally: Lead Technical Change Within Your Engineering Team - oreilly book
Infrastructure & Ops Superstream Series: CI/CD - oreilly video
Building Evolutionary Architectures - oreilly book

Notes (Thinking Architecturally - Nathaniel Schutta youtube video)

Here are the mods I recommend. These are all compatible with the latest versions of SMAPI and Stardew Valley on Linux/macOS/Windows. See the player's guide to using mods if you're interested.

Quality of life

I think the best mods are those which improve the game while maintaining its balance, lore, and style.

AutoGate
Gates open automatically when you approach and close behind you.
Better Sprinklers Plus
Customise the sprinkler radius, with a proportional change to their cost. If you're willing to mine all the ores you'll need, that makes the basic sprinklers useful early in the game and lets you do more than just watering crops every day.

My Minimal TypeScript Monorepo Setup for ESM Libraries

After a deep dive looking up best practices for TypeScript monorepos recently, I couldn't find anything that suited my needs:

Publish individual (typed) packages to NPM with minimal config.
Supports fast unit testing that spans the entire project (e.g., via Vitest)
Ability to have an interactive playground to experiment with the API in a real-time (e.g., via Vite)

Most solutions point to TypeScript project references,

Step 1 - Make a Discord Webhook

Find the Discord channel in which you would like to send commits and other updates
In the settings for that channel, find the Webhooks option and create a new webhook. Note: Do NOT give this URL out to the public. Anyone or service can post messages to this channel, without even needing to be in the server. Keep it safe!

Step 2 - Set up the webhook on Github

Navigate to your repository on Github, and open the Settings

The Revealing Module Pattern in Javascript

Zach Caceres

Javascript does not have the typical 'private' and 'public' specifiers of more traditional object oriented languages like C# or Java. However, you can achieve the same effect through the clever application of Javascript's function-level scoping. The Revealing Module pattern is a design pattern for Javascript applications that elegantly solves this problem.

The central principle of the Revealing Module pattern is that all functionality and variables should be hidden unless deliberately exposed.

Let's imagine we have a music application where a musicPlayer.js file handles much of our user's experience. We need to access some methods, but shouldn't be able to mess with other methods or variables.

	<!-- livebook:{"persist_outputs":true} -->

	# Distribute

	## Section

	A small toy to show how you might, given a stream, do a "fan out", processing different elements in separate streams. Powered by simple primitives like `Stream.resource` and `spawn_link`.

	```elixir
	defmodule Distribute do

	<div id="section">
	<div class="article">
	<p>Bacon ipsum dolor amet sirloin jowl turducken pork loin pig pork belly, chuck cupim tongue beef doner tri-tip pancetta spare ribs porchetta.
	</p>
	<p class="moretext">
	Brisket ball tip cow sirloin. Chuck porchetta kielbasa pork chop doner sirloin, bacon beef brisket ball tip short ribs.
	</p>
	</div>
	<a class="moreless-button more" href="#">Read more</a>
	</div>

	/*****************************************************************************
	* QuantCup 1: Price-Time Matching Engine
	*
	* Submitted by: voyager
	*
	* Design Overview:
	* In this implementation, the limit order book is represented using
	* a flat linear array (pricePoints), indexed by the numeric price value.
	* Each entry in this array corresponds to a specific price point and holds
	* an instance of struct pricePoint. This data structure maintains a list

	# Platform: OS X
	#
	# Role: pull last repository changes, then build and run on a connected iOS device
	#
	# Usage: ./buildandrun-ios.sh [version] [--run-only]
	#
	# Parameters:
	# version version number (e.g. "v0.2", "v4rc3", etc.) for your Unity build name
	# --run-only set this if the Unity project was already build and you don't want to rebuild it
	#