The pattern is locked in. Enter a domain. Learn the system deeply. Identify the inefficiencies. Build systems to fix them. Outgrow the domain. Repeat.
The domain keeps changing. IT support, web development, tutoring, rave promotion, AI operations. The operating system does not change at all. The optimizer brain is constant. Only the material it operates on rotates.
The tutoring proof
The first visible proof was the tutoring business. Started at minimum wage in a small center in Jamaica, Queens. Within weeks, outperformed the other two tutors combined. The senior tutor confirmed it. Left when the hours got cut, launched independent at $20 per hour, scaled to $180 per hour, eventually offered $15,000 project packages with escrow.
Tutoring was not just tutoring. It was curriculum design, marketing, tech stack building, and psychological coaching. Built a website from scratch with Jekyll and Material Design. Built a parent community. Built a referral network that eliminated the need for advertising. Publicly disagreed with the Department of Education on standardized testing strategy because the data supported a different conclusion.
The contrarian principle was codified during this era: whenever I make a big decision, I ask myself what a typical prep center would do, and then I do the opposite. That principle survived every domain change intact.
The rave domain
The same optimizer brain hit the rave scene and found the same thing it always finds: inefficiency everywhere. Finding underground parties was hard for everyone, including locals. The system response: curated flyer sharing, then guest list aggregation, then commission links, then a full event platform. Every subdomain within nightlife got the same treatment. Meta ads from scratch to three-tier funnel in six months. WordPress from blank install to custom architecture. Venue operations from first booking to multi-room production.
The learning approach never changed either. Ask the dumb question first. Challenge the answer. Demand specifics. Build the framework. Automate and move on. Four hundred conversations with ChatGPT following exactly this pattern — the same pattern used to learn SHSAT prep strategies seven years earlier.
The shadow side
The serial optimizer pattern has a cost. The domain outgrowing happens before the previous domain is fully realized. The tutoring business was growing organically through referrals when the CDMX break happened. The CDMX scene was running fine when the NYC focus took over. The software company vision is articulated while the events business is still scaling.
From outside it looks like the pattern keeps working. From inside, the question is whether this is healthy serial iteration or premature domain-hopping. Each domain gets less investment than it could before being handed off or automated. The current build is the most self-referential version: building the system that will run all the previous domains so the operator can move to the next one.
The resume looks nonlinear. CS student, tutor, CDMX break, rave promoter, AI operator. But the through-line is consistent: systems thinker who builds things from scratch and optimizes relentlessly. The domain is just the canvas. The painting is always the same — find the inefficiency, build the system, run the system until the next domain calls. Same brain. Different material. Every time.