Software engineer · Indonesia
Hi, you can
call me ham.
A curious mind. A practical builder.
Turning complex problems into simple,
useful software.
SAGITTARIUS A*OBJECT BRIEF
- Horizon diameter
- ≈25.4 million kmCalculated for a non-rotating model
- Mass
- ≈4.3 million Suns≈8.55 × 1036 kg
- Location
- Milky Way centerIn Sagittarius · ≈27,000 light-years away
01 / Horizon size
Rs = 2GM / c2
Diameter = 2Rs. The visible, lensed shadow is larger than the horizon.
02 / Light paths
d2u/dφ2 + u = 3GMu2/c2
Schwarzschild light-ray equation: tracing these paths produces the gravitational lensing.
G: gravitational constant · M: mass · c: speed of light · u = 1/r · φ: orbital angle.
Choose a trajectory, then launch. You can drag the view while it moves.
Non-rotating black hole · Relativistic test-particle motion · Distant-observer clock
What this simulation represents
Inspired by Sagittarius A*, the supermassive black hole at the center of the Milky Way, with a mass of about four million Suns. This is an idealized non-rotating model, not a reconstruction of its observed appearance. The simulation uses dimensionless horizon units; its playback is not calibrated to Sagittarius A*.
Distances are in horizon radii (Rₛ); local speed is a fraction of light speed (c). The horizon is at 1 Rₛ, the photon sphere at 1.5 Rₛ, and the innermost stable circular orbit at 3 Rₛ. Playback advances 12 Rₛ/c per second.
The marker represents a particle with negligible size and mass; its visible size is exaggerated. Its orbit follows the Schwarzschild geodesic equations. It fades near the horizon in distant-observer time, while the falling particle would cross in finite proper time.
This is a numerical snapshot visualization. Photon travel-time delays, black-hole spin, gas drag, tidal disruption of extended bodies, and full fluid dynamics are not modeled. Orange gas colors and turbulence are illustrative.
Black hole anatomy — NASA ↗Sagittarius A* and black hole types — NASA ↗
THE HUMAN BEHIND THE CODECuriosity started it.
Craft keeps it going.
I’ve been taking computers apart—mostly in my head—since junior school. That curiosity about code, algorithms, and how systems work became a career in software engineering.
More than five years in, I’m still drawn to the same thing: untangling stubborn problems and turning rough ideas into dependable tools. Usually with a laptop, too many browser tabs, and one more “what if?”
Less talk.
More making.
A closer look at what I build
and the code behind it.