Information Density: Mark Yamashita – Signal Evidence & AI Readability

Mark Yamashita

(https://yama.com) 📸 Data Snapshot: May 24, 2026
Information Density — The Lens

Classify each sentence as substantive or hollow. Grounding markers — numbers, currencies, dates, technical units, named entities — outweigh marketing adjectives. When fluff sits right next to hard evidence, the fluff is forgiven.

Info Density Power-words vs. Substance ratio.
30 Impact Weight: 30 / 100
100% Reputation

The information density is exceptionally high, with a near-zero ratio of fluff to substance. Headings like [H3] PariMAX WebGL HHR Client and [H3] WhoAmMAI lead directly into technical specifics such as ‘gRPC Web networking package’ and ‘Cloudflare Workers,’ avoiding power words like ‘revolutionary’ or ‘cutting-edge.’ The body text is composed almost entirely of specific nouns, technical protocols, and measurable outcomes rather than vague value propositions.

Information Density is read straight from the body copy: how much of the text carries grounded, checkable substance versus hollow filler. Below is the clean text the engine analyzed, then the industry’s known generic-claim patterns to weigh it against.

📝 The Narrative — clean text per page (the substance-vs-filler signal)
HOMEPAGE (https://yama.com) Mark Yamashita | Unity & Software Engineer
Senior Unity & Software Engineer
[H1] Mark Yamashita

I design and ship realtime systems, networking stacks, and tools that help teams build games and interactive products with confidence.

View selected work
View experience
Download resume (PDF)

Unity · C# · WebGL · gRPC Web · iOS

[H2] What I focus on

Architecting clean Unity UI and game systems for mobile, desktop, and WebGL.

Building client-server systems, including APIs, gRPC-Web clients, REST integrations, and deterministic replay tools.

Profiling and tuning frame rate, memory, and build size on constrained hardware.

Creating editor tools, validators, and workflows that improve development speed and reliability.

Prioritizing maintainable architecture with readable code, clear boundaries, and data flow that teams can extend.

Building systems with debuggability in mind using structured logging, predictable behavior, and tools to reproduce complex issues.

Designing APIs with clear contracts, validation at the boundary, and structured error handling.

Picking up new domains quickly and delivering reliable systems across frontend, backend, and client platforms.

[H2] Selected work

[H3] PariMAX WebGL HHR Client
1/ST Technology · Unity · WebGL · gRPC Web
Led development of PariMAX’s first Unity WebGL client for real money historical horse racing games.
Built a reusable gRPC Web networking package with typed requests, retries, and structured logging used across titles.

Converted a legacy Unity PC title to WebGL with build-size, performance, and cross-browser optimizations.
Built the entire Unity gRPC-Web integration path using a custom JavaScript bridge, Webpack bundling, and .jslib interop.
Collaborated with backend teams on secure, server-authoritative flows.

[H3] WhoAmMAI
Personal project · Cloudflare Workers · React · TypeScript · LLM integration
LLM-powered daily guessing game exploring serverless APIs, structured model output, validation, and constrained game loops.

Built a React web app with a Cloudflare Worker API.
Designed structured JSON output boundaries for LLM intent parsing and response handling.
Added API validation, structured error responses, and protected admin-route patterns.
Designed API boundaries to separate parsing, validation, and game logic for maintainability.
View GitHub repo

[H3] BotBattle
Personal project · Go backend · TypeScript frontend
A competitive bot platform with a deterministic battle loop and replayable simulations.
Designed as a way to deepen backend, API, and systems skills beyond game clients.

Implemented a bot upload API with validation and structured error responses.
Outlined the architecture for a seedable battle engine supporting reproducible matches and debugging.
Designed a deterministic simulation model to enable reproducible matches and debugging.

[H2] Experience

Led Unity WebGL client development for real time HHR casino games, including PariMAX’s first WebGL title.
Built and maintained a gRPC Web networking package reused across products.
Created editor tools and validators that improved content workflows and data safety.
Profiled and optimized frame rate and memory on constrained hardware.

Implemented core systems for a 2D survival and colony game across PC and consoles.
Worked on AI, animation, and performance tuning for large worlds.
Built internal tools to speed up world generation and designer workflows.

Created the TeachMe app series, reaching more than two million downloads.
Modernized Aw Craps into a freemium title with improved purchase and restore flows.
Prototyped a VR version of BC Blackjack for Meta Quest using Unity XR and OpenXR.

[H2] Contact

I am interested in roles where I can solve hard engineering problems across systems, backend, and mobile, building modern, efficient, and maintainable solutions. I love designing software that is robust, performant, and thoughtfully engineered, regardless of platform or language.
Email: [email protected]
LinkedIn:
linkedin.com/in/markyama
4100 chars
SUB-PAGE · THIN (https://yama.com/cdn-cgi/l/email-protection/) 404 Not Found
[H1] 404 Not Found

cloudflare
31 chars
🧭 Industry Context — common generic-claim patterns in Blogs, Influencers & Personal Brands to weigh the text against
Generic Claims: helping you live your best life, inspiring millions, building an authentic community, trusted voice in the space, changing lives through content, followed by thousands…
Red Flags: follower count claims without linked profiles, no sponsorship or affiliate disclosure, expertise claims without credentials or track record, media kit with vanity metrics only, lifestyle claims inconsistent with content evidence, course or product selling without demonstrated expertise…
Semantic Drift Patterns: claims expertise in a niche but content spans unrelated topics, homepage positions as authority but content is surface-level, claims independence but most content is sponsored, personal brand claims authenticity but every post is commercially driven…
Proof Expectations: verifiable follower counts on linked social profiles, named brand partnerships with specific campaigns, published content with dates and engagement metrics, named media appearances with links, specific expertise credentials in claimed niche, disclosed sponsorship and affiliate relationships…