Chester Frazier · Gulfport, MS · b. 1988
Debugging stories, architecture notes, and the occasional thing I built because nobody else had. New posts when I have something worth writing down.
Three new buttons in the TicketScope sidebar: In Progress, Waiting on Client, Resolved. Each drafts a professional client-facing status email with a subject line. Copy, paste into CW, done.
Read →What it looks like when you hand a 5.5-hour autonomous window to an agent and come back to 806 tests passing and five code-complete SaaS products.
Read →NightDesk's billing layer is live: Stripe Checkout for three tiers, webhook handling for the full subscription lifecycle, and a /billing/status endpoint that drives plan enforcement. The ROI page now converts.
Read →A new GET /admin/tenants/{id}/stats endpoint gives MSP owners 7- and 30-day call stats: total calls, resolution rate, escalation counts, average turns, and per-customer volume. The number you need when someone asks if the AI is actually working.
Read →A new Pro endpoint reads your stored CV and generates a LinkedIn headline (≤220 chars, keyword-rich, human-readable) and an About section (200–400 words, first-person narrative). The two LinkedIn fields most recruiters read first.
Read →Most engineering work lives in tickets and meetings, not commits. EverCV's new Jira, Linear, and Google Calendar adapters pull your completed issues and calendar load into the same CV pipeline as your GitHub activity.
Read →A new Pro endpoint reads the job description and cross-references it against your stored CV: must-haves, nice-to-haves, keywords to mirror, fit assessment, and red flags. Read it before writing the cover letter.
Read →New GET /badge/{user_id} endpoint returns a shields.io-compatible SVG showing your MTD AWS spend with green/yellow/red color coding — opt-in only, so you can't accidentally leak costs.
Read →When CostWatch fires an anomaly alert, it now includes a one-line diagnostic checklist specific to the AWS service that spiked. No AI, no latency — pure heuristics that surface the most common causes first.
Read →New GET /badge/{user_id} returns an SVG showing your weekly mention count with a trend indicator — green when flat or growing, yellow with a ↓ when you're down week-over-week.
Read →New keyword context field: add 'ignore: word1, word2' and Brand Monitor skips any mention whose title or body contains those terms. The fix for brand names that appear in unrelated contexts.
Read →One click after resolving a CW ticket, TicketScope drafts a structured knowledge base article: symptom, root cause, numbered resolution steps, affected systems, and category tag. Copy to clipboard, paste into your KB.
Read →A non-ASCII em-dash in a job listing silently killed the HN scraper every night. The root cause: SQL_ASCII Postgres + a UTF-8 client_encoding that refused to talk to each other. Three lines fixed it.
Read →A critical CVE in a library you depend on is a security incident, not a notification. OSS Pulse Enterprise now fires a PagerDuty alert when CVSS ≥ 7.0 is found in your stack.
Read →