AI tools for
newsrooms.

# Vibe coding quick start checklist

Pre-flight checklist for AI-assisted coding sessions. Print this out or keep it open during your first few projects.

---

## Before you start

- [ ] **Define a specific goal** — Write down exactly what "done" looks like in one sentence
- [ ] **Gather your data** — Have sample files ready, know your data format
- [ ] **Choose your LLM** — Pick one and stick with it for this session
- [ ] **Create project folder** — Clear name, organized structure
- [ ] **Start a changelog** — Use the CHANGELOG-TEMPLATE.md file
- [ ] **Test your environment** — Can you run "Hello World" in your language of choice?
- [ ] **Set a time limit** — Protect yourself from rabbit holes

---

## During the session

### Prompting best practices

- [ ] Start with the big picture, then drill into details
- [ ] Include your environment info (OS, language version, key libraries)
- [ ] Provide sample input/output when possible
- [ ] Ask for code in chunks, not all at once
- [ ] When stuck, ask "What might be causing this?" not just "Fix this"

### When code breaks

- [ ] Copy the **full error message**, not just the last line
- [ ] Paste it back to the AI with context: "I ran this code and got this error"
- [ ] If same error 3+ times, step back and explain the bigger goal
- [ ] Check if the error is your environment, not the code

### Red flags

- [ ] Code getting too complex? Split into smaller scripts
- [ ] Scope creeping? Note the new idea for later, stay focused
- [ ] Going in circles? Take a break, return with fresh eyes
- [ ] AI giving same wrong answer? Try rephrasing or different LLM

---

## Before you stop

- [ ] **Test with real data** — Not just the sample
- [ ] **Document what you built** — Update the changelog
- [ ] **Note what's unfinished** — Clear next steps for future you
- [ ] **Save working state** — Commit to git or backup the folder
- [ ] **Clean up** — Remove test files, add comments to unclear code

---

## Quick reference

### When to use which language

| Task | Language |
|------|----------|
| Data cleaning/analysis | Python |
| Statistical analysis | R |
| Interactive web visualization | JavaScript |
| File automation | Bash/Python |
| Database queries | SQL |

### Current best LLMs for coding (Dec 2025)

| Need | Recommendation |
|------|----------------|
| Coding and writing | Claude 4.5 Opus |
| Front-end design, large docs | Gemini 3.0 Pro |
| OpenAI coding tasks | Codex (GPT 5.1) |
| Free, getting started | Claude.ai free tier |

---

*From [Center for Cooperative Media](https://centerforcooperativemedia.org) AI Tools for Newsrooms*

# LLM comparison chart for journalism projects

> Last updated: December 2025. The AI landscape changes fast—verify current pricing and capabilities.

---

## At a glance

| Model | Best for | Speed | Cost | Free tier? |
|-------|----------|-------|------|------------|
| Claude 4.5 Opus | Best for coding and writing | Slower | $$$ | Limited |
| Claude 4.5 Sonnet | All-around tasks, best balance | Fast | $$ | Yes |
| Gemini 3.0 Pro | Front-end design, large documents | Fast | $$ | Yes |
| Codex (GPT 5.1) | OpenAI coding tasks | Fast | $$ | Limited |
| GPT 5.1 | Deep research, complex reasoning | Slower | $$$ | Limited |
| GitHub Copilot | In-editor suggestions | Real-time | $10/mo | Students |

---

*From [Center for Cooperative Media](https://centerforcooperativemedia.org) AI Tools for Newsrooms*

# Project Name — Changelog

> Use this template to document each vibe coding session.

---

## [YYYY-MM-DD] Session Title

### Goal
<!-- What you set out to accomplish this session -->

### What worked
-

### What broke
- **Error:**
- **Fix:**

### Code changes
- `filename.py` — Description

### Next steps
- [ ]

---

*Template from [Center for Cooperative Media](https://centerforcooperativemedia.org) AI Tools for Newsrooms*

# Lessons learned — [Project Name]

> Use this template to document what you learned from a completed or abandoned project.

**Project:** [Name]
**Date range:** [Start] – [End]
**Status:** [Completed / Abandoned / On hold]

---

## Project summary
<!-- One paragraph: What was this? What problem did it solve? -->

## What worked
### Technical wins
-

### Process wins
-

## What didn't work
### Critical failures
-

### Technical debt
-

## The real problem
<!-- What was *actually* needed vs. what you initially set out to build? -->

## What I'd tell past me
1.
2.
3.

## Recommendations
### If continuing this project
1.

### If starting fresh
-

---

*Template from [Center for Cooperative Media](https://centerforcooperativemedia.org) AI Tools for Newsrooms*