How I Built a Python Workflow for HN Job Filter

#python #automation #tutorial #productivity

Shipping reliable automation tools is mostly about reducing repeated manual work.

In this post I walk through a practical pattern I use to build and ship a focused utility: HN Job Filter.
The goal is simple: solve one painful workflow with a script a developer can run locally in minutes.

What problem this script solves

Most teams lose time in repetitive steps that are easy to automate but expensive to keep doing manually.
For this project, I focused on the parts that usually burn time: setup friction, inconsistent output, and no clear handoff artifact.

The approach is:

Make one script handle the core workflow.
Keep output deterministic and readable.
Package it with a README and sample output so anyone can run it quickly.

Minimal runnable structure

from pathlib import Path

def run_workflow(input_path: str) -> dict:
    text = Path(input_path).read_text(encoding="utf-8")
    lines = [ln.strip() for ln in text.splitlines() if ln.strip()]
    return {
        "line_count": len(lines),
        "char_count": len(text),
        "has_errors": any("error" in ln.lower() for ln in lines),
    }

print(run_workflow("sample_input.txt"))

This keeps the first pass intentionally small. You can run it instantly and verify the output before adding complexity.

Add a useful report layer

import json
from datetime import datetime

def save_report(report: dict, output_file: str = "report.json") -> None:
    report["generated_at"] = datetime.utcnow().isoformat() + "Z"
    with open(output_file, "w", encoding="utf-8") as f:
        json.dump(report, f, indent=2)

data = {"workflow": "strong", "status": "ok"}
save_report(data)

Now the script creates an artifact you can hand off, compare between runs, or feed into another tool.

Packaging pattern that improves conversion

I use the same packaging checklist for every utility product:

one ready-to-run script
README with exact commands
sample output so buyers know what they will get
short receipt text with quick-start instructions

That sounds basic, but it removes purchase friction and support overhead.

Why this matters for real projects

For small automation tools, trust beats novelty.
If a buyer can understand the workflow, run it quickly, and see useful output, adoption goes up.

The current packaged version of HN Job Filter is available here ($7.00):
https://intellitools.gumroad.com/l/hn-job-filter

If you are building similar utilities, focus on repeatability and clarity first, then add more features.

DEV Community