Venso AIData Services
Back to all posts/Tech Blog
WritingMay 4, 20245 min read

Newsletter habits that keep shipping

Notes from running a weekly engineering newsletter: templates, cadence, and keeping the feedback loop alive.

writing
newsletter
community

The newsletter ships every Sunday night. The template is the guardrail: a quick win, a short lesson learned, three links worth reading, and one experiment I am trying next week.

The workflow

  • Collect notes during the week in a running doc
  • Draft on Saturday morning, edit once, ship on Sunday
  • Ask three questions in every send to keep replies flowing

Templates reduce friction. Readers know what to expect, and I know when a draft is done enough. The goal is momentum, not perfection.

Reminder

If the feedback loop goes silent, ask for it directly. The best edits come from the people you are writing for.

Key takeaways
Highlights you can reuse.
A predictable cadence beats a perfect draft
Reusable sections: wins, links, experiments, asks
Feedback loops with 3 open questions in every send
Downloadable template
Copy the checklist and adapt it to your stack.

Includes prompts, runbooks, and rollout steps referenced here.

Shipping an AI feature in a single weekend
The constraints, scaffolding, and observability I lean on to take an idea from notebook to production by Monday morning.
Build log
8 min read
Read
LLM evaluation that does not hurt
A lightweight rubric I use to grade LLM features before users do, with examples for reasoning and tool-heavy prompts.
AI/ML
9 min read
Read
Edge AI with Workers and Rust
Running inference at the edge with predictable latency, shared wasm modules, and a hybrid routing plan for heavier models.
Edge
8 min read
Read