Interfaces people can actually use
Responsive pages, forms, dashboards, and application flows that make the next action clear.
- React and Next.js
- Accessible forms
- Responsive dashboards
Capabilities
Practical work across the layers of a technical problem.
NeedThisDone works across the layers that make a system useful: interface, data model, API, and operations.
Capabilities
A generalist range with concrete edges.
“Generalist” does not mean every tool or every project. It means following the problem across the layers that need to cooperate.
Backends, data, and permissions
Durable records and server-side rules that keep the system honest as the work moves forward.
- Postgres and Supabase
- Auth and RLS
- Durable state
APIs and integrations
Connect the services a project depends on so information can move without manual glue work.
- REST and MCP boundaries
- Payments and email
- External services
Workflows and automation
Turn repeated steps, approvals, and handoffs into a path that is easier to run and review.
- Approval paths
- Scheduled work
- Operational tooling
Systems that hold together
Look across the layers when the hard part is not one component but the connection between them.
- Source-of-truth design
- Failure recovery
- Reviewable results
Testing and delivery
Protect the important paths and make the result easier to check before it moves forward.
- Unit and contract tests
- Accessibility checks
- Release evidence
Working vocabulary
Tools are useful when they serve the system.
These are the tools and boundaries used most often. The important part is choosing the smallest reliable combination for the problem.
ReactNext.jsTypeScriptPostgres / SupabaseREST and MCP APIsRedisPlaywrightVitestGitHub
Start with the technical problem.
You do not need a polished brief. A short description, a link, or a confusing system boundary is enough to begin a useful conversation.