AWAQU :: ABOUT
The person behind the project files

About

Awaqu is a place for documenting things I build, study, test, and occasionally abandon.

My name is Carlos Radriguez. Awaqu is the public archive for projects that emerge from my interests, work, frustrations, questions, and attempts to make useful things.

The projects are not limited to one industry or discipline. Some begin as software built for my own use. Others begin as research questions, personal systems, data experiments, or ideas that seem worth testing.

The common thread is a preference for understanding systems in enough detail to make them more useful.

Background

My professional background includes financial crime investigation, anti-money laundering work, fraud analysis, customer-facing hospitality, sales, and fitness.

Outside of work, I have spent years studying Japanese, training with kettlebells and strength systems, building personal software, analyzing data, and experimenting with ways to make information easier to capture, understand, and use.

That mix is reflected in the project archive. A routine tracker may sit beside a Japanese reading tool, a 3D anatomy system, a food-value analysis project, or an application built around sunrise and sunset.

Areas of Interest

Personal Systems

Routines, tracking, longitudinal data, and tools that help make everyday behavior more legible.

Fitness & Human Performance

Strength training, anatomy, exercise selection, programming, mobility, and performance data.

Language & Learning

Japanese, contextual study, information capture, and tools that connect real-world exposure with deliberate learning.

Data & Investigation

Patterns, financial crime, pricing, comparison systems, and the practical use of structured information.

Why Awaqu Exists

Not everything needs to become a company, but useful work should not disappear simply because it is unfinished.

Awaqu gives these projects a permanent place to exist outside of local folders, private notes, and long development conversations.

Some projects may eventually become public software. Some may be open-sourced. Some may remain personal tools. Others may stop developing entirely. The archive is intended to document that process honestly.