關於我
Hey, I'm Kip 👋
Backend engineer focused on architecture decisions, type safety, and immutable domain modeling.
專注於架構決策、型別安全與不可變領域建模的後端工程師。
Currently a Senior Programmer Analyst at Systex in Taiwan, working on AWS architecture and internal tooling.
目前任職於精誠資訊，擔任高級程式分析師，主要負責 AWS 架構規劃與內部工具開發。
🔧 ImmutableBase
我獨立開發與維護的 PHP 開源套件，用繼承式設計實作不可變的 DTO / Value Object / Sealed Value Object。
這個專案體現的是我對 DDD 實踐、資料正確性、以及「非法狀態不應存在」的堅持。
An open-source PHP library I built and maintain — inheritance-based immutable DTOs, VOs, and SVOs for PHP 8.4+.
It reflects how I think about DDD in practice, data correctness, and making illegal states unrepresentable.
→ Repository ・ Packagist ・ r/php discussion
Stack / 技術棧
Day-to-day: PHP · Laravel · TypeScript · Vue/Nuxt · MySQL · Redis · Docker
Infrastructure: AWS · Nginx · Linux
Practices: DDD · Clean Architecture · SOLID · Design Patterns
What I value / 我重視的事
- Trade-off reasoning over best practices — every design decision has a cost; I'd rather know the cost than follow a rule.
每個設計決策都有代價，我寧可清楚知道代價，也不要盲從最佳實踐。 - Immutability as architecture — not just
readonly, but designing systems where illegal states are unrepresentable.
不只是readonly，而是在架構層面讓非法狀態無法被表達。 - IDE-friendly design — if your IDE can't autocomplete it, the design made a compromise.
如果你的 IDE 補不出來，那這個設計就做了妥協。
Currently exploring / 目前在探索的
- Rust — building my mental model of ownership and zero-cost abstractions
正在建立對 ownership 和 zero-cost abstractions 的心智模型。 - Architecture — moving beyond tactical patterns into bounded context design and architectural boundaries
從戰術模式往戰略層深入，探索 bounded context 設計與架構邊界的劃分。 - Design Patterns — expanding beyond the patterns I use daily into broader structural and behavioral patterns
從日常使用的模式往外拓展，探索更多結構型與行為型模式。
Technology serves the business. Nothing is a silver bullet — not even the things I build.
技術服務於業務，沒有銀彈——包括我自己做的東西。