Stabilizing and Modernizing a Legacy Industrial SCADA Platform (Qt 4.7 / VS2003) 1. Project Context Around 2017, I worked on a large industrial SCADA platform used in the power and wind energy industry. The system was built on Qt 4.7.3 and Visual Studio 2003, and it ran inside a legacy Windows environment with heavy operational constraints. The work was not a normal UI project. It was part of a larger production system that included realtime telemetry, backend services, industrial communication, and long-running operational clients. ...

Rethinking Web3 Job Scams: How My 128GB Linux Lab Exposed a Highly Obfuscated Payload The Incident In the volatile world of Web3 recruitment, the “Take-Home Assignment” has become a weapon for social engineering. I recently identified and neutralized a sophisticated “recruitment” scam that used a Next.js project as a Trojan horse. The Forensics Operating within my isolated 128GB RAM Linux Lab, I performed a deep-dive audit of a seemingly innocent “Technical Test” provided by a “Web3 Startup.” ...

In the 12KB Trenches: A 30-Year Retrospective on System Sovereignty and Security Defense The Hook In the modern landscape of Web3, DePIN (Decentralized Physical Infrastructure Networks), and high-security systems, the boundary between resource constraints and security integrity is a critical frontier. While high-level abstractions like ZK-Rollups and Sharding offer structural protection, true system sovereignty is often determined at the level of register states and memory cycles. When facing the core challenges of memory safety and re-entrancy defense, the solution is not always found in massive distributed diagrams, but in precise low-level control: ...

Why Your Cross-Language “Bridge” Is a Ticking Time Bomb — And the 5 Mechanisms That Defuse It A senior architect’s field manual for hardening the most fragile layer in enterprise systems: the boundary between C++ and managed languages. The Uncomfortable Truth About Interoperability Every modern enterprise system is a polyglot. Java orchestrates the business logic. C# renders the UI. Python scripts the glue. And somewhere deep in the stack — often in the financial core, the hardware driver, or the cryptographic engine — sits a C++ library that does the actual heavy lifting. ...

Energy Cloud Governance: Grid Data Reliability As the lead architect for a national-level Energy Cloud platform (handling power trading and microgrid management), I was responsible for transforming a prototype into an industrial-grade infrastructure capable of handling tens of billions of data points with sub-second retrieval latency. 1. Elasticsearch Tuning at the 10-Billion Scale In a production environment with 10.7 billion documents (approx. 700GB), standard configurations failed catastrophically. Through rigorous stress testing (Esrally/fio), I implemented the following optimizations: ...

Reliability Audit: Toyoko INN Reservation System This external audit was conducted to identify mission-critical reliability bottlenecks and security vulnerabilities in a major hospitality reservation system. Operating with zero internal access, I developed automated Python probes to evaluate the system from a “real-world” user perspective. 1. Executive Summary: The Revenue Leak The audit revealed a Desktop LCP (Largest Contentful Paint) of 3.72s, significantly exceeding the 2.5s industry standard. Under weak network conditions (representative of many travelers), this latency spikes to 16.0s, leading to extreme churn risk. ...

Introduction In the first quarter of 2026, I was invited to perform an emergency architectural audit for a regulatory-compliant Web3 startup based in Tokyo. The project aimed to revolutionize the real estate market by fractionating physical properties into tradeable ERC-1155 tokens. On the surface, the platform had a polished UI and a functioning “MVP.” However, underneath the hood, the engineering was a “paper bulletproof vest”—looking strong but fundamentally incapable of protecting the millions of dollars in TVL (Total Value Locked) it was designed to hold. ...

ETL Stabilization: Batch Processing from 70s to 1.5s Background The system was a data fusion platform built with Spring Boot 3 and Java 17, designed to handle massive multi-source heterogeneous sports data. The legacy implementation suffered from extreme performance degradation as data volume scaled. Core Challenges N+1 Query Bottleneck: The legacy logic processed records individually, leading to massive database round-trip overhead. A 500-record batch took over 70 seconds. Database Deadlocks: High-concurrency environments triggered frequent lock contention and deadlocks due to non-indexed deduplication queries. Architectural Bloat: The core service had swelled to 1200+ lines, making it a “distributed monolith” that was impossible to maintain. Architectural Solutions 1. Batch Upsert Engine I refactored the persistence layer, moving away from automated ORM patterns to raw MyBatis XML. ...

Project Context: The “Frozen” Infrastructure In 2014, a major state-owned infrastructure provider faced a critical security crisis. Thousands of legacy terminal units deployed across the country were using aging 3DES cryptographic schemes that no longer met modern compliance standards. However, the hardware was “frozen”—firmware updates were high-risk, and the cost of total replacement was estimated in the millions of dollars. My mission was to architect a “Rescue Layer” that would harden the system’s security without requiring a physical hardware overhaul. ...

Frontend Stabilization Under Production Pressure Context In late 2025, I temporarily took over a problematic Vue 3 + TypeScript IM frontend after the previous frontend developer left. The system had accumulated several P0/P1 issues that were blocking business-side testing and making the client experience unpredictable: Refresh triggered forced logout WebSocket connections were unstable UI flows deadlocked during loading and retry transitions Random white screens appeared under normal usage Cypress automation failed intermittently Authentication state raced against async UI updates Frontend state diverged from backend contracts Int64 and Snowflake IDs were at risk of precision loss in JavaScript Constraints I was not the dedicated frontend specialist on this project. ...