This portfolio is part portfolio, part systems demo, part attitude check. It shows what I care about when I build: strong runtime primitives, clear operational visibility, low-friction workflows, and enough personality to make the experience memorable.
I love Elixir, the BEAM, and Phoenix because they let me build the whole thing as one coherent system instead of a pile of unrelated services. I do not want five dashboards, three vendors, a separate email platform, a SaaS analytics bill, and a security stack that mostly exists to watch other services fail.
This site is the opposite of that. It is one Phoenix application with a real telemetry layer, instant Slack delivery, lightweight analytics, honeypots, decoys, hidden interactions, and a visual style that leaves room for movie references, operator culture, and playful behavior without compromising utility.
Stack Shape
The portfolio, contact workflow, telemetry, ops review surface, honeypots, and easter eggs live inside the same application boundary. That keeps behavior easier to reason about and removes a lot of failure points.
Delivery
Slack webhooks handle direct notifications for valid contact traffic, suspicious submissions, and internal review events. That cuts out SMTP setup, separate form processors, and analytics tooling I do not actually need.
Runtime
The same runtime that makes serious systems work well also makes playful, stateful, story-driven interactions easier to build. That combination matters to me.
The telemetry here is intentional. I want to know how the site is used, how real contact traffic behaves, where suspicious interaction happens, and which routes attract curiosity. I also want that information to stay useful, lightweight, and immediate.
Valid contact submissions go to Slack. Suspicious contact traffic can be separated from legitimate messages. Decoy interactions and ops-login behavior can be reviewed with more context than a single raw IP line in a log. The point is not surveillance theater. The point is signal quality.
The honeypots are real enough to teach a lesson and believable enough to produce useful data. The easter eggs are there for the opposite reason. They are a nod of respect to curiosity. If someone explores with intent and attention, I want the site to reward that energy instead of acting like personality and security cannot coexist.
Visual Direction
The visual language pulls from roller-rink color, hacker-movie energy, arcade-era playfulness, and the feeling that a site can still have a point of view.
References
The references are not random decoration. They are part of the story layer. I like systems that feel alive, self-aware, and slightly mischievous as long as the engineering underneath stays honest.
Build Philosophy
I do not think serious software has to be joyless. If the runtime is solid and the workflow is clear, there is room for style, humor, hidden layers, and a little bit of chaos in the presentation.