Query Traba's data sources directly. Two backends:
Default is Postgres prod. Pass dev, prod, or bq as the first word to override.
A small feedback loop that nudges Claude Code to capture non-obvious learnings as reusable skills/rules at the end of every session, instead of letting them evaporate.
Three pieces:
continuous-learning.sh) — fires when Claude tries to end its turn. On the first stop in a session it blocks and tells Claude to run /retrospect first. A /tmp marker file tracks that the prompt has been delivered, so the second stop attempt (after retrospect runs, or after Claude decides there's nothing to capture) goes through cleanly. The marker expires after 5 minutes so it doesn't bleed across unrelated sessions.
name: worker-interview-research description: | Workflow for producing a research briefing on a Traba worker ahead of a Worker Interview Program call. Use when: (1) user asks for "deep research" / a "briefing" / "writeup" on a named worker, (2) user references the Worker Interview Program or asks who to prep for an interview, (3) user wants to understand a worker's experience on the app before a call. Covers: which prod tables to hit (and the gotchas), how to frame the worker as
To tag a commit and use the commit date for the tag:
git checkout <commit hash>
GIT_COMMITTER_DATE="$(git show --format=%aD | head -1)" git tag <tag name>
To fix commit timestamps:
git filter-branch --env-filter 'export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"'
Hi, thanks for your interest in ACM's backend development team! Your task is to write a design doc for a "quest system" that integrates into the membership portal and then schedule an interview that'll be some mix of design review, technical, and behavioral.
First you'll need to understand how the portal works at the API and database layers—the portal doesn't currently have a service layer—and then design appropriate API and database changes for the required functionality. Your priority should be a working design, not a clever one; bonus points if you explain why yours is definitively the best or if you consider multiple designs and explain the tradeoffs of each. There's no right answer and this is an exercise intended to see how you approach some functionality you'd reasonably be expected to implement as a backend developer for ACM—there's no limit to how deep your changes to the portal can go. The portal's being completely rewritten so don't worry about any current constraints (e.g. what
Sumeet Bansal
CSE 131 PA4
fibonacci.boa
(def fib (n : Num) : Num
(if (< n 3)
1
(+ (fib (- n 1)) (fib (- n 2)))
| (* FA18 CSE 130 Midterm Practice *) | |
| (* FA14 *) | |
| type expr = Const of int | Var of string | Op of string * expr * expr | |
| let rec rename_var e n1 n2 = | |
| match e with | |
| | Const c -> Const c | |
| | Var s -> if s = n1 then Var n2 else Var s | |
| | Op (a,b,c) -> Op (a, rename_var b n1 n2, rename_var c n1 n2) |
| from bs4 import BeautifulSoup # for parsing HTML | |
| import os # for managing files | |
| import sys # for cleaner stdout | |
| import urllib.request # for downloading images | |
| from fpdf import FPDF # for generating PDFs | |
| # page content saved as HTML file | |
| inputfile = 'MUS-17-Tricia-Rose-reading.html' | |
| output = inputfile[:-5] + '.pdf' |