Shinjae Kang profile photo

Shinjae Kang

Programmer & Software Architect · Jakarta, Indonesia

Hi, I’m Shinjae Kang

I’m a programmer and software architect based in Indonesia, building software across web, backend, desktop, mobile, and operations. The modoo-id GitHub organization contains Modoo projects I developed and treat as part of my engineering portfolio.

My work sits at the intersection of practical product engineering and infrastructure: Laravel, VueJS, Tailwind CSS, PHP, DevOps, .NET, C#, WPF, VB, HTML, CSS, WordPress, and Flutter. I care less about framework hype and more about systems that survive real users, real teams, and real maintenance.

I’ve lived and worked in Jakarta for more than 15 years, which gives this site its point of view: a Korean developer operating inside the Southeast Asian tech scene, connecting ideas, tools, and business context across both worlds without reducing either side to stereotypes.

Professional focus

AreaWhat I care about
Software architectureBoundaries, maintainability, rollback paths, and systems that are still understandable six months later.
Web product engineeringLaravel, VueJS, Tailwind CSS, PHP, WordPress, and Modoo Laravel/Vue SaaS projects behind real business software.
DevOps & automationCron jobs, CI/CD, artifact checks, deployment discipline, and workflows that prove they worked.
AI agents & developer toolsAgent workflows, model portability, verification gates, and the difference between a demo and a production-adjacent system.
Desktop and legacy systems.NET, C#, WPF, VB, Windows utilities, serial communication tools, and older systems that still matter.
Regional contextKorea to Southeast Asia technology, teams, constraints, and opportunities.

Core stack

  • Backend / Web: Laravel, PHP, WordPress
  • Frontend: VueJS, Tailwind CSS, HTML, CSS
  • Operations: DevOps, cron workflows, deployment checks, artifact verification
  • Laravel SaaS projects: Modoo Smart, Permit, Order, PickPack, Ingredient, Apps, Catalog, Website, and documentation systems
  • Desktop / Windows: .NET, C#, WPF, VB, Windows shell extensions
  • Mobile / Cross-platform: Flutter
  • Automation / AI: AI agents, publishing pipelines, verification gates, model/tool evaluation

Experience map

This site is built around a simple bias: software advice should come from contact with real maintenance.

  • If an automation exits successfully but creates no usable artifact, it failed.
  • If a framework solves the demo but hides the exit path, it is expensive.
  • If an AI agent writes code but leaves no testable boundary, it is not an engineering workflow.
  • If a tool looks impressive but cannot survive local constraints, team habits, or budget reality, it is not ready.

That is the lens I use when writing about AI, devtools, frontend systems, backend architecture, and infrastructure.

What I build

I keep a small set of public projects and tools under my personal GitHub account, and Modoo project repositories under the modoo-id organization. Together they show the range of work behind this blog: Laravel/Vue SaaS projects, documentation systems, Windows utilities, desktop tooling, networking helpers, serial communication testers, and the zemna.net publishing stack itself.

See the curated list on the Portfolio page, visit github.com/zemna, or browse github.com/modoo-id.

What this site is

  • A long-running personal blog about AI, software development, dev tooling, and operations
  • An English-first publication with Korean and Bahasa Indonesia mirrors
  • A working lab for the zemnanet design system and the zemnanet content pipeline
  • A practical record of what I am testing, adopting, rejecting, and rebuilding

What I usually write about

  • AI agents and automation that need real verification, not just green dashboards
  • Laravel, Vue, Tailwind, PHP, and the everyday stack behind maintainable web products
  • DevOps, reliability, cron jobs, artifact checks, and production-adjacent workflows
  • The Korea to Southeast Asia developer bridge: tools, markets, teams, and local constraints
  • How senior developers should evaluate new tools without getting trapped by hype

What this site is not

  • A company blog. The opinions here are mine.
  • A paid newsletter. No sponsors, no ads, no affiliate links.
  • A posting-everything firehose. Quality gates run on every post before it ships.

Where else to find me

Disclosure

Some posts on this site are drafted with AI assistance. The text, opinions, code samples, and final edits are mine. When AI assistance is more than mechanical, such as suggesting a research direction, the post will say so in a note at the bottom.