A Hero's Way

Technical writer turned front-end developer

Making complex things clear and usable.

From trophy guides to front-end development, clarity has been the through-line.

Explore my journey

I started writing trophy guides after finding inefficient or abandoned resources—and changed requirements that existing guides never covered. Improving that experience grew into years of hands-on UX/UI work, then into front-end development and systems thinking.

2018–2025

Documentation & UX/UI

Started writing guides in late 2018. Developed my approach to usable, maintainable documentation on TrueTrophies (2018–2024) and Blogger (2020–2025).

Sep 2025–May 2026

Web & mobile development

Began formal study, then continued through self-directed learning as my pace and learning style moved beyond the coursework.

Sep 2025–Oct 2026

Systems thinking

Developed the structural framework behind my portfolio, connecting content, interface, and the systems that support them.

Foundational guide projects

Dev Log: Operation Outer Haven | Tactical Systems Analysis & Full-Stack Development

Dev Log: Operation Outer Haven

Subject: Tactical Systems Analysis & Full-Stack Development


What began as a search for better trophy guides gradually evolved into something much larger: a long-term exploration of systems analysis, information architecture, software development, and documentation engineering.

This entry documents the progression from pattern recognition and data analysis to the development of independent tools, documentation platforms, and long-term knowledge systems.


Phase I: Pattern Recognition (2018 - 2025)

Long before developing PSTrophyGuides, I found myself naturally drawn toward identifying patterns, relationships, and hidden systems within complex environments.

  • Rainbow Six Siege Analysis: Developed the ability to identify operators through limited information such as weapon audio, uniform details, environmental cues, and tactical positioning.
  • Independent Research: Began investigating cognitive processing, learning styles, and information management through self-directed research and observation.
  • Documentation Interest: Recognized that much of the available gaming documentation lacked organization, maintenance, and long-term reliability.

Phase II: Building Infrastructure (2020 - Present)

Frustration with outdated documentation eventually led to the creation of PSTrophyGuides, a platform focused on guide maintenance, information preservation, and user experience.

  • Guide Maintenance: Established verification workflows for live-service titles where updates and balance changes frequently invalidate older documentation.
  • Information Architecture: Developed search systems, content categorization, DLC organization, and component-based guide structures designed around accessibility and discoverability.
  • Version Preservation: Implemented archive structures that preserve historical versions while allowing ongoing modernization and platform improvements.

Phase III: Tool Development & Automation

As the documentation ecosystem expanded, attention shifted toward building supporting software capable of solving recurring workflow challenges.

  • Backlog Tracker: A C# desktop application developed to simplify completion tracking and game management workflows.
  • Guide Integration: Exploration of systems capable of connecting game libraries to relevant documentation resources.
  • Scalability Planning: Designing structures capable of supporting thousands of games across multiple platforms without sacrificing usability.

Documentation Philosophy

Modern games are no longer static products. Live-service models, licensing changes, platform differences, and frequent updates require documentation that evolves alongside the software itself.

  • Dead by Daylight: Tracking licensing changes, DLC availability, platform differences, and gameplay updates.
  • Disney Dreamlight Valley: Organizing large collections of recipes, villagers, quests, and collectibles through structured categorization systems.
  • User Transparency: Clearly distinguishing paid content, platform limitations, and version-specific information.

Current Mission Status

Operation Outer Haven continues through the modernization of legacy documentation, expansion of reusable component systems, and development of tools that reduce friction for completion-focused players.

  • Guide modernization initiatives.
  • Component-driven site architecture.
  • C# application development.
  • Knowledge preservation and archival workflows.
  • Search and navigation refinement.
Guides should age like documentation, not forum posts.

No comments:

Post a Comment