Speak to Claude Code and get responses read aloud. Fully local STT (Whisper) and TTS (Kokoro), no API keys needed.
You speak → Whisper transcribes locally → Claude responds → (optional) Kokoro speaks response
| # This is an example of metaprogramming in the Elixir language. | |
| # | |
| # We will define a domain specific language (DSL) for the definition | |
| # of a service which is watched by several sensors. | |
| # Each sensor watches some property/functionality of the service and | |
| # returns the result of the check. | |
| # | |
| # To determine if the service is functioning properly, we need functions | |
| # to run all the sensors' code and gather the returned data. | |
| # |
One of my colleagues shared an article on writing (good) Git commit messages today: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
1a. Programming Elixir 1.6 by Dave Thomas
1b. Learn Functional Programming with Elixir by Ulisses Almeida
Programming Phoenix 1.4 by Chris McCord, Bruce Tate, and Jose Valim
Functional Web Development with Elixir, OTP, and Phoenix by Lance Halvorsen
Metaprogramming Elixir by Chris McCord
| #!/bin/bash | |
| SERVER=$1 | |
| NFS_SHARE=$2 | |
| LOCAL_SHARE=$3 | |
| RAMFS_SHARE=$4 | |
| echo "Setting up RamFS" | |
| mkdir /tmp/ramfs | |
| mkdir /tmp/ramfs/$RAMFS_SHARE |
| ================================================= | |
| After software installation | |
| ================================================= | |
| RUN apt-get clean | |
| RUN rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* | |
| ================================================= | |
| Docker on build process, include all files on directory build (include .git with old build) | |
| Solution for reduce size of docker image (but for reuse is not good solution) | |
| ================================================= |
$ git filter-branch --tree-filter 'rm -rf <some-dir>' --prune-empty HEAD
$ git for-each-ref --format="%(refname)" refs/original/ | xargs -n 1 git update-ref -d| #!/bin/bash | |
| # nth-commit.sh | |
| # Usage: `nth-commit.sh n [branch]` | |
| branch=${2:-'master'} | |
| SHA1=$(git rev-list $branch | tail -n $1 | head -n 1) | |
| git checkout $SHA1 |
| #!/bin/bash | |
| # update_build_number.sh | |
| # Usage: `update_build_number.sh [branch]` | |
| # Run this script after the 'Copy Bundle Resources' build phase | |
| # Ref: http://tgoode.com/2014/06/05/sensible-way-increment-bundle-version-cfbundleversion-xcode/ | |
| branch=${1:-'master'} | |
| buildNumber=$(expr $(git rev-list $branch --count) - $(git rev-list HEAD..$branch --count)) | |
| echo "Updating build number to $buildNumber using branch '$branch'." |