lachlansleight

// This is the old version of my shader - I'm in London atm and don't have the new project that spawns particles to hand
// In this one, there's one particl
// The particles are something like

struct Particle {
    int2 PixelPosition;
    float3 WorldSpacePosition;
}

// compute buffer matched to the particle struct

lachlansleight

// ==UserScript==
// @name         YouTube Shorts Hider
// @namespace    lachlansleight
// @version      0.1
// @description  Hides all evidence of Shorts from the YouTube desktop site
// @author       You
// @match        https://www.youtube.com*/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=youtube.com
// @grant        none
// ==/UserScript==

lachlansleight

The WeekLog Idea System

Justification

Traditional project management systems are designed to solve organizational problems - that is, problems that occur when trying to be productive in organizations of collaborators. As a result of this, they tend to be focused on stable, live projects and be unsuitable for Projects that are undergoing iterative, experimental creation, or for Projects that don't have a fixed end-point in mind, or for Projects for which the stable release represents the end point, rather than the starting point.

This system is designed to be more flexible - to give a conceptual rigor and structure to more experimental, iterative or creative Projects. Because of its flexibility, this system can be a meta system, with more traditional organizational methods living within it. For example, a Scrum Sprint could represent a single 🛠️Elaboration Effort, or a month of Kanban could represent several concurrent 🩹Stabilization Efforts. More on these terms later!

The system was designed wi