Day 005 opens — content from the phone, roots before the hype, Python and math

Day 005 starts a few minutes after midnight. Still in thought mode — writing them down before they turn into fake todos.

Capture first. Ship the useful ones later.

Content from the phone

I want an AI tool that makes creating content easy from the app or the phone — not only when I am at a desk. Draft, shape, publish (or queue) while I am moving. Same lane as Dispatch, the encyclopedia idea, and eventually social — fewer barriers between “idea” and “on the site.”

Before the hype: meta coding and machine learning

I need to learn how meta coding worked and how machine learning worked before the LLM hype cycle. Foundations and history — not only product demos from 2023 onward. Taste needs roots.

Python

Time to start learning Python for real. Rails is home base; Python is how a lot of ML, data, and tooling still talk. Direction, not a certificate marathon.

Math toward a stronger engineer

I want a clear map of content — what math (and related theory) to study so the engineering is not just shipping screens. Sequences, readings, practice problems — a path, not vibes.

Ship an app every two days

Goal: make an app every two days. Ideally one a day — or two every 1.5 days if I am honest about how crazy that sounds.

I know it reads like a dare. I still think it is possible if “app” means a real scoped ship — narrow problem, working surface, public URL or install path — not a six-month platform. Speed forces taste: cut scope, reuse the starter stack, let AI help without skipping verification.

This sits next to the content-from-phone idea and the Rails/React/RN foundation. Cadence is the proof. Crazy on purpose.

These are thoughts. Client wrap, mailers, and phone coding from Day 004 still matter more for the business day. A separate post tonight holds the bigger question: what makes a true engineer?