Four fields,
one practice.

Photography is fundamentally about observation — training yourself to notice light, geometry, and moment. It's the most immediate of the four disciplines: you see, you frame, you capture. But the simplicity is deceptive.

Every photograph is a dataset. The sensor captures photons across a spectrum, the lens introduces its own physics, and the resulting file is a matrix of values waiting to be interpreted. Post-processing is signal processing. Long exposure is integration over time. The darkroom was the first image processing pipeline.

This is where photography stops being "just art" and starts bleeding into every other field. The same skills that compose a street photograph — pattern recognition, timing, spatial awareness — are the skills that spot anomalies in a network log or structure in telescope data.

Code is the universal solvent. It dissolves the boundaries between disciplines because it can simulate, automate, and extend any of them. A photography workflow becomes a Python pipeline. A security audit becomes a scanning tool. An astrophysics model becomes a simulation.

But coding is also its own discipline — with its own aesthetics, its own sense of elegance. A well-architected system has the same satisfying inevitability as a mathematical proof or a well-composed photograph. The craft isn't just in making it work; it's in making it clear, maintainable, and minimal.

The real power is in the meta-level: code that writes code, systems that observe themselves, tools that amplify your ability to build more tools. This recursive quality is what makes software engineering feel closer to astrophysics than to accounting.

Security is applied epistemology. It asks: what do we think we know about this system, and where are we wrong? Every vulnerability is a gap between a model and reality. Every exploit is a proof that the map was not the territory.

The offensive mindset — thinking like an attacker — is fundamentally a creative practice. You're not following instructions; you're imagining possibilities that the builder didn't. This is the same cognitive mode as composing a photograph nobody else would take, or asking a scientific question nobody else thought to ask.

Defensive security is architecture. It's building systems that remain correct even under adversarial conditions. This requires understanding not just code, but human psychology, organizational dynamics, and the economics of attack. It's systems thinking at its most paranoid and most necessary.

Astrophysics is the ultimate exercise in remote observation. You cannot touch your subject. You cannot run experiments on a star. All you have is light — photons that left their source thousands or millions of years ago — and mathematics. Everything else is inference.

This constraint forces a kind of intellectual discipline that bleeds into everything else. When you're used to extracting meaning from faint signals across cosmic distances, parsing a network packet or reading a photograph becomes almost trivially direct by comparison.

The scale is also transformative. Once you've internalized that the observable universe is 93 billion light-years across, that every atom in your body was forged in a star, that spacetime itself is a dynamic medium — your relationship to every other problem changes. Not because other problems become small, but because you develop a tolerance for the incomprehensible.

This is also where original research lives. My paper A Cosmology-Linked Low-Acceleration Scale from Galaxy Dynamics, Weak Lensing, and an Information-Theoretic Interpretation explores how the characteristic transition scale in galaxy dynamics is set by the cosmological background — connecting the radial acceleration relation, weak lensing data from KiDS, and an information-theoretic framework into a unified picture of low-acceleration physics.