Skip to main content
Career11 min read

Writing a 120,000-Word Book While Building Software Full-Time

I wrote a 24-chapter book on trading while building the Nexural platform. Here's how I managed both, what nearly broke me, and why writing made me a better engineer.

By Jason TeixeiraSeptember 1, 2025
WritingProductivityTradingPersonal GrowthDiscipline
Share:
On this page

In December 2024, I finished the first draft of a 120,000-word book on trading. 24 chapters. That's roughly the length of two Harry Potter books.

I wrote it while simultaneously building the Nexural platform — 185 database tables, 69 API endpoints, a Discord bot, and this portfolio site. Full-time engineering. Full-time writing. Full-time trading.

People ask "how?" The answer is less inspiring than you'd expect.

The System

I wrote 500 words per day. Every day. No exceptions.

500 words takes about 30-40 minutes. Some days it was 20 minutes because the ideas were flowing. Some days it was an hour because every sentence felt like pulling teeth. But the minimum was always 500.

At 500 words per day, 120,000 words takes 240 days — about 8 months. That's it. No sprints. No weekends of marathon writing. Just 500 words, every single day.

Why 500 (Not 1,000 or 2,000)

I tried 1,000 words per day in the first week. By day 4, I was burned out and skipped a day. That skip became 3 days. Those 3 days became a week.

500 words is low enough that I never have an excuse to skip. "I don't have time" doesn't work when the task takes 30 minutes. "I'm not feeling inspired" doesn't work because 500 words of bad writing is still 500 words closer to done.

Bad pages can be edited. Missing pages can't.

The Chapter Structure

Every chapter follows the same template:

\\

Reader route

article -> proof -> offer

ReadClusterProofScope

cluster

Fintech & Trading Systems

intent

Career

route

next step

What to do with this

Turn the note into a build path.

If this topic maps to a real business problem, keep reading the cluster, study the academy path, or route the work into a scoped engagement.

Jason Teixeira
Written by
Jason Teixeira
Founder, Sage Ideas Studio · Principal Engineer
livebuild a1556e22026-06-19 03:29Z
// solo studio// no analytics resold// every commit human-reviewed