This guide is unmaintained and was created for a specific workshop in 2017. It remains as a legacy reference. Use at your own risk.
Workshop Instructor:
- Lilly Ryan @attacus_au
This workshop is distributed under a CC BY-SA 4.0 license.
This guide is unmaintained and was created for a specific workshop in 2017. It remains as a legacy reference. Use at your own risk.
Workshop Instructor:
This workshop is distributed under a CC BY-SA 4.0 license.
| #!/usr/bin/env bash | |
| # shellcheck disable=SC2034 | |
| # shellcheck disable=SC1091 | |
| # shellcheck disable=SC2154 | |
| # PADD | |
| # | |
| # A more advanced version of the chronometer provided with Pihole | |
| # SETS LOCALE |
| import smtplib, email, os | |
| from email.mime.base import MIMEBase | |
| from email.mime.multipart import MIMEMultipart | |
| from email.mime.text import MIMEText | |
| from email import encoders | |
| from picamera import PiCamera | |
| from time import sleep | |
| from datetime import datetime | |
| import RPi.GPIO as GPIO |
| https://github.com/billw2/rpi-clone | |
| sudo apt install git | |
| git clone https://github.com/billw2/rpi-clone.git | |
| cd rpi-clone | |
| sudo cp rpi-clone rpi-clone-setup /usr/local/sbin | |
| lsblk | |
| sudo rpi-clone sda |
I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
So below I made a list of leetcode problems that are as close to grokking problems as possible.
| package main | |
| import ( | |
| "fmt" | |
| "sync" | |
| ) | |
| // ---------------- INTERFACES AND STRUCTS ---------------- | |
| // Fetcher defines an interface for fetching URLs |
Companion prompts for the video: OpenClaw after 50 days: 20 real workflows (honest review)
These are the actual prompts I use for each use case shown in the video. Copy-paste them into your agent and adjust for your setup. Most will work as-is or the agent will ask you clarifying questions.
Each prompt describes the intent clearly enough that the agent can figure out the implementation details. You don't need to hand-hold it through every step.
My setup: OpenClaw running on a VPS, Discord as primary interface (separate channels per workflow), Obsidian for notes (markdown-first), Coolify for self-hosted services.
Prompts to recreate each piece of the OpenClaw system. Use these with any AI coding assistant.
1. Personal CRM "Build a personal CRM that automatically scans my Gmail and Google Calendar to discover contacts from the past year. Store them in a SQLite database with vector embeddings so I can query in natural language ('who do I know at NVIDIA?' or 'who haven't I talked to in a while?'). Auto-filter noise senders like marketing emails and newsletters. Build profiles for each contact with their company, role, how I know them, and our interaction history. Add relationship health scores that flag stale relationships, follow-up reminders I can create, snooze, or mark done, and duplicate contact detection with merge suggestions. Link relevant documents from Box to contacts so when I look up a person, I also see related docs."
2. Meeting Action Items (Fathom)