Aldo Prianandi / Indonesia

Small tools for work that repeats.

I make browser automations, internal utilities, and content systems around tasks that keep coming back.

Browser

Reduce repeated web work.

Checking, filtering, filling, comparing, and QA loops.

Internal

Build small utilities around real workflows.

Scripts, lightweight dashboards, backend glue, deploy workflows, and tools people can reuse.

Content

Make production less manual.

Reusable systems for carousels, course material, and media assets.

Public project

Cinethetic

Cinethetic demo carousel preview rendered from structured content
Demo: one JSON carousel rendered through a reusable visual system.

A Remotion carousel renderer that turns structured content into reusable social slides. The public repo is tagged at v0.1.0 with demo themes, docs, CI, and release checks.

View repository

Public

One content model, multiple rendered directions.

Cinethetic keeps slide meaning in JSON and renders the same demo carousel through Manifest, Terminal, Brutalist, and Neoprint themes.

Audience

A football content channel with public traction.

Bolakokgitu shows the distribution side: a 400K+ cross-platform audience, a large short-form library, and repeatable reach built through a consistent publishing system.

Backend

Enough system context to connect the tool.

Work has touched PHP/Yii2, Node.js, Hono with Bun, PostgreSQL, Supabase, Google Cloud, AWS, and CI/CD auto-deploy workflows.

Method

Useful tools start from annoying repeat work.

The pattern is map the loop, build the smallest reusable tool, then verify with real output before polishing.

Start with the annoying part of the process.

Use AI, scripts, browser tooling, and real output to move faster.

Bring enough backend, database, and deployment context to make the tool fit the system around it.

Keep each tool scoped: clear input, useful output, repeatable run.

Have something repetitive?