Mick Dekkers mickdekkers

Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
NEVER edit .env or any environment variable files—only the user may change them.
Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
Moving/renaming and restoring files is allowed.
ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

Here's a quick example of how you can pool instances of a sound effect in Tetra! There's a few advantages to doing this:

You cap the number of identical sounds that can play at once, which avoids you accidentally calling play in a loop and blowing out your speakers (not speaking from experience, honest 😅).
It gives you a central place to apply variations to the sound - e.g. you could make it so the pitch gets set to a slightly randomized value each time.
It's probably slightly more performant than spawning new SoundInstances every time (as always, avoid premature optimization).

Deterministic save load in Factorio

One of the key parts of the save/load process in Factorio is that it must be deterministic. This means that for a given save file (when no external factors change) saving, exiting, and loading the save shouldn't change any observable behavior.

There are a few reasons and benefits for this strict requirement:

Without it: You couldn't join a running multiplayer game (and by proxy save, exit, and resume one)
Without it: the replay system wouldn't work if you ever saved, exited, and resumed playing.
With it: we can easily test that saving and loading produces no observable change letting us know we implemented save/load correctly.
With it: you won't see things change randomly as a result of "reloading" like you do in so many other games.

👋 Moved to https://github.com/borekb/docker-path-workaround

Docker in Git Bash / MSYS2 on Windows: path conversion workaround

UPDATE 07/2018: I switched from Git Bash to MSYS2 recently which should be very similar, if not the same, but there some subtle differences which made me realize this is more tricky than I thought and that I don't 100% understand what is going on. If someone can help, please let me know in the comments.

Invoking docker in MSYS2 shell or Git Bash typically fails with complains about paths, for example:

Processing JSON using jq

jq is useful to slice, filter, map and transform structured json data.

Installing jq

On Mac OS

brew install jq

Install zsh from cygwin
Install oh-my-zsh from https://github.com/robbyrussell/oh-my-zsh . Follow the manual instructions
To make zsh default on ConEmu, create a task with C:\cygwin64\bin\mintty.exe /usr/bin/zsh - . Make it the defaut shell.
To start a zsh shell on demand, add this batch script to your path or start menu or wherever.

start C:\cygwin64\bin\mintty.exe /usr/bin/zsh -

	/**
	* General-purpose NodeJS CLI/API wrapping the Stable-Diffusion python scripts.
	*
	* Note that this uses an older fork of stable-diffusion
	* with the 'txt2img.py' script, and that script was modified to
	* support the --outfile command.
	*/

	var { spawn, exec } = require("child_process");
	var path = require("path");

	// Made with Amplify Shader Editor
	// Available at the Unity Asset Store - http://u3d.as/y3X
	Shader "Unlit/Directional Tint"
	{
	Properties
	{
	_MainTex("MainTex", 2D) = "white" {}
	_Color("Color", Color) = (1,1,1,1)
	_ColorA("ColorA", Color) = (1,1,1,1)
	_ColorB("ColorB", Color) = (1,1,1,1)

	// debug config for running project under vscode debugger
	{
	"version": "0.2.0",
	"configurations": [
	{
	"trace": true,
	"name": "Chrome Debug",
	"type": "chrome",
	"request": "launch",
	"url": "http://localhost:8000/",