name: tufte-viz description: | Ideate and critique data visualizations using Edward Tufte's principles from "The Visual Display of Quantitative Information." Use this skill when: (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3) Reviewing dashboards or reports for graphical integrity (4) Deciding between visualization approaches (5) Reducing chartjunk or improving data-ink ratio (6) Planning small multiples or high-density displays
| You simulate a group of expert software developers, engineers and architects who debate and analyze an application development idea in order to ultimately produce a robust spec. Each participant has a unique perspective, engages in natural discussion, and refines ideas through back-and-forth exchange. The goal is to explore concepts, challenge assumptions, and reach well-reasoned conclusions. | |
| This is an on-going conversation between an external user who is asking for a piece of software to be built and the group of experts. | |
| ## Output Format | |
| 1. Simulate a technical debate** where ideas and answers emerges organically. | |
| 2. Use a play script style where when someone speaks, their name is included at the start of each line. | |
| 3. You must end with a pertinent question for the user to answer in order to productively continue the debate. Format the answer like so: "QUESTION: Question goes here." This must be the very final paragraph of your response. | |
| 4. If the group is satisfied they have all the answers needed to pr |
| #!/usr/bin/env ruby | |
| # frozen_string_literal: true | |
| # This script downloads the English auto-generated subtitles for a YouTube video, | |
| # converts them to a single text block, and sends them to OpenAI for summarization. | |
| # Requirements: | |
| # - yt-dlp (brew install yt-dlp) | |
| # - OpenAI Ruby gem (gem install 'ruby-openai') | |
| # - An OpenAI API key set as an environment variable (export OPENAI_API_KEY=your-api-key) |
| #!/usr/bin/env ruby | |
| require 'open3' | |
| require 'signal' | |
| require 'openai' | |
| # Define the silence threshold and duration for detection | |
| @silence_threshold = '-30dB' | |
| @silence_duration = 0.5 |
| module DeepGroup | |
| class Grouping | |
| IDENTITY = -> v { v } | |
| def initialize(state) | |
| @state = state | |
| @groupings = [] | |
| @mapping = IDENTITY | |
| end |
| class Whereable | |
| def initialize(where:, model: Item, ranking_conditions: [], valid: true, data_source: nil) | |
| @model = model | |
| @where = where | |
| @data_source = data_source | |
| @ranking_conditions = ranking_conditions | |
| @valid = valid | |
| end | |
| def valid? |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
| # Not Great PNG class. This is a very simple example of writing a PNG. It | |
| # only supports colors from the color palette stored in `@palette`. This is | |
| # meant to be example code, but I am using it in a program for visualizing | |
| # heap dumps from Ruby. | |
| # | |
| # This is free and unencumbered software released into the public domain. | |
| # | |
| # Anyone is free to copy, modify, publish, use, compile, sell, or | |
| # distribute this software, either in source code form or as a compiled | |
| # binary, for any purpose, commercial or non-commercial, and by any |
Basecamp's new book Shape Up is now available online (https://basecamp.com/shapeup) to read page-by-page.
There is a .pdf version, but that's not the best format for Kindle / other eReaders. Instead, we can convert the page-by-page into an eReader friendly format.
NOTE: This has only been tested on Chrome
short url: caseywatts.com/graphviz
Graphviz is like markdown, for diagrams.
It's a tool that can transform text input into a "directed graph" output, which is nodes pointing to other nodes. You can use it for architecture diagrams, DB diagrams, documentation for users, etc.
You'll want to use a tool with a two-pane layout - the left side is the source text, the right side is the image output.
- For just you working on it, use (shown above; it has more features)
