boat@localhost:~/about

$ man boat(1)

boat(1) — user commands

NAME

Boat — Senior Full Stack Developer

SYNOPSIS

boat [--full-stack] [--cloud] [--security] [--ship]

DESCRIPTION

Hi, I'm Boat (Jirayu) — a senior full stack developer with about ten years in the field. I still write the code: Vue and React on the client, Laravel and Node on the server, then the GCP / Kubernetes / Cloudflare layer that keeps it online.

Delivery is part of the job, not a side quest. I write CI workflow YAML, automate the boring path, cover flows with e2e, and ship behind feature flags and A/B tests. I work Agile with teams that actually merge.

I care about clean interfaces, durable systems, and the details that make software feel fast and intentional — including network security, not as a later ticket. This site itself is a playground: Next.js, Tailwind, and a CRT terminal skin.

OPTIONS

--frontend
Vue, React, Next.js, Tailwind — UIs people actually use.
--backend
Laravel, Node, Postgres/MySQL, Redis, queues and workers.
--cloud
GCP, kubectl, Docker, Terraform, Helm, Cloudflare, Nginx.
--quality
E2E, unit/integration, A/B tests, feature flags, PHPStan/Psalm.
--security
Network security, TLS/WAF, IAM and secrets as part of the feature.
--process
Agile delivery, CI YAML, automation — ceremony only when it helps.

FILES

~/skills · ~/contact

$ history --decade

  1. [~2016] First production deploys

    PHP web apps, MySQL, and learning what “it works on my machine” really costs.

  2. [~2018] APIs and SPAs

    Laravel backends, Vue on the client, Redis where a request shouldn’t wait.

  3. [~2020] Cloud and pipelines

    GCP, Docker/Kubernetes, Cloudflare, and CI workflow YAML instead of tribal knowledge.

  4. [~2022] Quality in the critical path

    E2E coverage, feature flags, A/B tests, and network security in the same PRs.

  5. [now] Still hands-on

    Full-stack product systems: review, unblock, and still type the diff myself.

$ cat ~/.profile

  • # Ship small, ship often — big-bang releases are a last resort.
  • # Make the boring path the safe path: CI, flags, tests, rollback.
  • # UI should feel fast; APIs should stay boringly reliable.
  • # If you can’t kubectl it calmly, it isn’t done.
  • # Security is part of the feature, not a follow-up ticket.

$ printenv HOW_I_WORK

  • → Agile without the cargo cult — standups that unblock, not theatre.
  • → Write the workflow YAML so humans don’t have to remember the happy path.
  • → Feature flags and A/B before betting the whole release.
  • → Review code, unblock teammates, still own the PR.

$ id

name
Boat
role
Senior Full Stack Developer
uptime
10 years
status
open to interesting work
mail
jirayu.bsk@gmail.com
./skills./contact
~/about--:--:--