I make software that feels considered.
Hi!, More than a decade of building systems taught me that the interesting work lives somewhere between a good decision, a clean boundary, and a very well-timed coffee.
View text version
PROFILE
Hi, I’m Pratya — an IT Project Manager, System Analyst, and hands-on Software Developer based in Thailand. I build software, design systems, and spend an unreasonable amount of time experimenting with AI agents. I’ve worked across requirements, architecture, development, testing, delivery, and maintenance for more than a decade. .NET is still home.
JOURNEY
A career path through enterprise software, without stepping away from the technical work.
2022–Present · Project Manager: Soft Square 1999 Co., Ltd. — Project, resource, and schedule planning; Stakeholder coordination and delivery; Effort estimation and quality control; .NET technical consultation and hands-on problem solving
2017–2022 · Assistant System Analyst → System Analyst: Soft Square 1999 Co., Ltd. — Requirement gathering and analysis; Functional and technical specifications; System design and development; Testing, go-live, and maintenance
2014–2017 · Software Developer → Senior Software Developer: Soft Square 1999 Co., Ltd. — Application analysis and system design; Enterprise web development; Unit and system testing; System and user manuals; Go-live and maintenance support
WORKSHOP
Current daily tools sit beside the technologies that built the earlier chapters.
CURRENT / DAILY: C# · .NET · ASP.NET Web API · Angular · PostgreSQL · SQL Server · GitHub · AI Coding Agents · Clean Architecture · CQRS
ENGINEERING: Requirement Analysis · System Design · Agile / Scrum · Project Delivery
LANGUAGES: VB.NET · VB6 · SQL · VBA
WEB / BACKEND: .NET Framework · ASP.NET Web Forms · ASP.NET MVC · JavaScript · jQuery · AJAX · Electron
DATA / TOOLS: Oracle · Visual Studio · VS Code · Azure DevOps · TFS · TortoiseSVN
DELIVERY: CMMI Level 2 · Waterfall · Agile · Scrum
ARCHIVE
The archive keeps professional history available without turning the journey into a wall of cards.
PROJECT ARCHIVE: Historical enterprise work — browse one entry at a time.
2024–2025 · Smart Logistic Web Application: Oil & Gas E&P client · .NET / SQL Server
2022–2024 · Expedient Production Report System (EPRS): Oil & Gas E&P client · field reporting integrated with PLC / PI System data
2021 · LCT Web Application — Maintenance: Oil & Gas E&P client · analysis, development, and support
2019–2020 · Robotic Application for Stroke Patient: Chulalongkorn Hospital / Thai Red Cross Society · remote-control rehabilitation robot software
2017–2018 · Material Balance Application — Maintenance: Oil & Gas E&P client
2016–2017 · Casing Pressure Management Enhancement: Oil & Gas E&P client
2016 · REFLEX Web Application System: Oil & Gas E&P client · analysis, development, and support
2016 · Bottom Hole Pressure: Oil & Gas E&P client · pressure-data tracking
2015 · Hire of Labor Timesheet Validation System: Oil & Gas E&P client · offshore labour-rate calculation
2015 · Electronic Stock Authorization Request: Oil & Gas E&P client · workflow system
2015 · Rig View: Oil & Gas E&P client
2014–2015 · Casing Pressure Management: Oil & Gas E&P client · high-pressure information management
2014 · iOEP Migration: Project-data migration to Microsoft Project 2007
CREDENTIALS.DB: Education and certifications collected along the way.
Bachelor’s Degree, Information Technology: School of Informatics, Walailak University · 2010–2014
Claude 101: Anthropic · 2026
Good Clinical Practice: NIDA · 2021
MCSD: App Builder: Microsoft · 2016
MCSA: Web Applications: Microsoft · 2016
MCPS: Microsoft Certified Professional: Microsoft · 2016
Programming in HTML5 with JavaScript and CSS3: Microsoft · 2016
MCSD: Web Applications: Microsoft · 2016
THE GATE
Thanks for taking the long way around. I’m Pratya. I build software, and sometimes software that builds software.
Turning experience into the next way of building.
$ currently-thinking-about
→ What 12+ years across requirements, architecture, code, testing, and delivery can teach AI-native teams.
→ Keeping .NET, clean boundaries, and practical engineering useful while workflows become more agent-assisted.
→ Making software delivery visible enough for people to understand, trust, and improve it.
→ Where humans should stay the decision makers — especially when the boring work gets automated.
→ Building systems that ship, then finding a better way to build the next one.
Elsewhere on the internet.
No contact funnel. Just a few places to find me or start a conversation.