11 · Life Plan
Read carefully. Build carefully. Revise carefully. Defend what compounds.
Defining vignettes, not chronology
The morning the deep-work block became non-negotiable
There was a specific week — I will not put a date to it — when I noticed that the only writing of mine I respected, looking back, had come from the same two-hour block I had been protecting against everything else for months. The block had become a feature of my life without my noticing. The realisation was that I had to formalise it before something else encroached and took the work with it.
When studying stopped being the answer on its own
For a long time the default mode was to study. To go deeper. To take the next course, to read the next book, to earn the next credential. The shift was not that studying became wrong — it was that building became the more honest mode of learning for me, and that the study-only mode had become a way of postponing the moment of building.
Faith as structural feature, not awkward fact
My practice as a Shia Muslim shapes the rhythm of the work I do — the schedule, the orientation toward long horizons, the disciplines around what is said publicly. I had a period of treating this as a private fact that lived alongside the professional one. The shift was to treat the integration as a positive structural feature rather than an awkward compartmentalisation. The work is better when the integration is admitted than when it is hidden.
The encounter that named what I was already doing
I had been working across multiple domains for years without a frame that fit. The phrase "polymathy in practice" — emphasis on the in-practice — gave me a frame I could defend without making a status claim. The vignette here is small: a conversation in which the right phrase arrived, and I knew immediately what to do with it.
Seven operating principles
The framing throughout my work is the verb, not the noun. I do not claim to be a polymath; I claim to practice polymathically — to keep work moving across genuinely different domains because that is the shape of the problems I want to do. The frame is operational and is therefore checked against actual practice, not against the way the practice presents.
I work with AI tools daily and have written down the constraints I work under so they are defended rather than drifted. The principle is that delegation is only honest when comprehension follows; AI as substitute for knowledge is rejected at the level of practice, not as a slogan.
The Study Log on this site enforces this principle structurally — there is no credential entry without the two paragraphs. The discipline is in writing the second paragraph honestly even when it is uncomfortable.
A strategic separation between what appears on husayngokal.com and what appears under other names in other venues. Not a denial of contested views — a deliberate decision about where each thing belongs. The test is willingness to own the view, by name, in any room.
A check applied across every design, content, and architectural decision. Failure on the five-year test removes the move from consideration. The corollary admits investments that look expensive in the short term because they compound — bespoke marks, carefully written essays, an open changed-my-mind log.
Without the block, the rest of the principles do not survive contact with the week. The block is the architectural commitment from which everything else inherits.
The integration is not declarative. It does not appear as personal exposition for its own sake. It appears where it is relevant to a topic and is treated as a working feature of how I think rather than as a fact about who I am.
Turning points, not annual updates
Compiled the operating brief for husayngokal.com
The act of compiling a single document I would defend, end to end, against revision-by-mood — that is the turning point of this year so far. The brief is the artefact; the discipline of writing it is the actual change.
Started Slipwise as a serious build, not a hypothesis
The shift from "could this work?" to "this is what I am doing this year" was less a decision than a recognition that I had already crossed it. The recognition was the move worth naming.
Earned the Qiskit Advocate credential
Completed CS50AI
Completed the ASTI Higher International Diploma
Published in Springer Nature Quantum Machine Intelligence
First peer-reviewed publication. The paper was on quantum graph neural networks for financial fraud detection. The lesson that carried was not the result but the process — research, when it is real, is slower and quieter than the version of it that students are taught.
Across four nested timescales
A running log of formally revised positions
2026-05-10
Previously: The event store should live in the application layer because the application owns the domain.
Now: The event store should be a separate library because durability of the audit trail outweighs the coupling cost. The argument I lost was right.
2026-04-20
Previously: Public reading logs are performative; reading should be private.
Now: Public reading logs become useful infrastructure when they serve as reference for the author rather than as performance for the reader. The shift is from "for them" to "for me, in public".
What I share, what I do not, on what cadence, and what the boundaries are. I share architectural decisions, position changes, and learning; I do not share client work, family details, or anything that requires context I cannot give in writing. Weekly accountability reviews on Sundays, monthly site-state notes, quarterly goal reviews, an annual retrospective.
The framework is documented to be defended. Without it, building in public degrades into either over-sharing or under-sharing — both worse than not building in public at all.