rpgCore taught me that architectural clarity is worth more than raw performance when prototyping complex systems. Here’s how we bridged Python, C#, and Rust into a cohesive game engine.

The Problem Statement

Most game engines are monolithic. Godot is great at rendering, but scripting in C# alone feels limiting. I wanted to explore: what if the engine was polyglot by design?

• Python for high-level game logic (fast to prototype, mature libraries)
• C#/Godot for rendering and visual debugging
• Rust for performance-critical calculations

The catch: making three languages cooperate without spaghetti code.

I built PhantomArbiter to detect and execute arbitrage on Solana. After 400 live trades across 3 months, I lost $4. Here’s what went wrong—and why the technology actually worked.

The Setup

System: Detect price divergence across Solana DEXes (Jupiter, Raydium, Orca, Meteora). Execute buy-low / sell-high atomically via JITO bundles (MEV protection).

Capital: $500 initial. Modest, but real money.

Timeline: 3 months, 400 completed trades.

Result: -$4.23 net.

Why It Failed (Technically)

RPC Latency Kills Speed

Solana blocks come every 400ms. My system sees an arbitrage opportunity, but by the time I submit the bundle, 2-3 blocks have passed. Price has already moved. The spread that looked profitable is now break-even or negative.

When I started as a Data Administrator, I inherited a mess: spreadsheets, manual data entry, no integration between systems. So I built a pipeline to automate 60% of my responsibilities. Here’s what I learned.

The Starting State

The problem: Contact center operations drowning in manual work.

• Lead import: CSV files dropped into email → manually copy into CRM → validate → assign
• Data cleaning: Leads with bad emails, duplicates, missing fields → hours per week in cleanup
• Enrichment: Missing company info, job titles → manual lookups
• Integration: Three separate systems with no data sync (CRM, email, call logs)
• Reporting: Hand-assembled spreadsheets for weekly management review

Time spent: 30 hours per week on data plumbing. 10 hours on actual admin work.

Upcoming Blog Posts

These are the topics I’m planning to write about. They’re drawn from my project experience, lessons learned, and things that don’t fit neatly into project documentation.

Technical Deep Dives

Building PhantomArbiter: Solana Arbitrage at Millisecond Scale

• Real-time WebSocket streaming from DEX feeds
• Multi-strategy detection (Raydium, Jupiter, Orca, Meteora)
• How latency kills profit: why MEV matters
• JITO bundle protection and MEV-aware ordering
• Python + Rust for latency-critical code
• Lessons from 400+ test trades

Why it matters: Shows how to think about real-time systems where milliseconds determine success or failure.