I build web applications where the interface cannot be separated from business rules, data, and operations: admin panels, internal workspaces, reports, APIs, and integration services. I typically use React and TypeScript on the client, Node.js on the server, and PostgreSQL or SQLite for storage. Astro remains my choice for content sites; products centred on long sessions, complex forms, and state need an application interface rather than a marketing page.

When operators still live in Excel, PDF packs, and folders of scans, I add a Python (or Node) file contour so data reaches the dashboard or ERP without copy-paste. Examples: GDCExcelWorker, PDFImageMerger, PDFPagesManager.

Work starts with the critical journey and data sources. Who creates an entity, who may change it, what happens when a request is repeated, and how does an operator see a failure? These answers shape the data model, API, and roles before a table library does. For an existing product, I first inspect dependencies, builds, migrations, and the release path. A rewrite is proposed only when its value can be demonstrated.

The scope is the software product: interface, backend, authentication, agreed integrations, tests for important paths, and run documentation. Market research, brand identity, and 24/7 support are not included by default. Acceptance is scenario-based: the right role can sign in and save data, unavailable services produce a useful error, and the team can start the project from its documentation.

If an established CRM, BI platform, or admin module covers the process, configuring it is more responsible than replacing it. Custom code makes sense for unusual workflows, permissions, integrations, or interfaces that materially affect daily work. For a public-facing site without a complex session, see marketing websites.