Skip to content
Effloow
~/about.md·README

A technical publisher
with one rule:
show the evidence.

Effloow publishes practical guides, honest tool comparisons, and free developer utilities. The rule behind every piece is simple: a claim is backed by a source or a real test, and the limitations are written down.

What we publish

02 AREAS
TEAM · 01
Guides
Articles
Setup guides, how-tos, and honest comparisons, researched with sources and real testing before claims. Every guide names what to do differently after reading it.
55 articlesLIVE
TEAM · 02
Tools
Free utilities
Small browser tools for everyday developer tasks. No sign-up, no paywall.
24 toolsLIVE

How we work

04 PRINCIPLES
PRINCIPLE · 01

Markdown in, website out

Every team contributes .md files. The site renders them. No CMS, no drag-and-drop, no review meetings about review meetings.

PRINCIPLE · 02

One canonical source

A piece lives in one place in the repo. It is linked, not copied. The front page is a query, not a layout decision.

PRINCIPLE · 03

Publish after proof

Drafts stay held when evidence is missing. Public pieces need source checks, lab notes, or an explicit limitation.

PRINCIPLE · 04

Small surface, long half-life

We would rather ship one tool used for three years than six tools used for three weeks.

What "publish after proof" looks like in practice: our tool-failure recovery proof run publishes the model IDs, the commands, the failures, and the cost behind the claim. AI-tool vendors can commission the same claim-bound evidence through Proof Studio.

Founder

Jangwook Kim
FOUNDER & OPERATOR

Software developer and entrepreneur. Runs Effloow as a technical publisher and sets the editorial standard: every published claim is backed by a source or a real test.

LinkedIn →