Technology / Working stack

Tools are leverage.
Judgment is the system.

This is not a badge wall or a fixed stack. It is a living view of the technologies we have used, how they enter the work, and the ideas we are forming about what they make possible.

01 / In the work

Broad capability.
Applied with intent.

Experience matters here as a pattern of use: where a technology is strong, what it changes, and how it can combine with the rest of the system.

Intelligence

Codex

How it enters the work: Agentic software development, structured analysis, research, and the workflows that connect an idea to working code.
Our current perspective: The most valuable shift is not faster typing. It is being able to give capable systems context, tools, and a meaningful outcome to pursue.

Intelligence

Claude

How it enters the work: Deep reading, synthesis, writing, alternate-model review, and thoughtful exploration of complex material.
Our current perspective: Different models reveal different edges. We value the ability to compare reasoning, voice, and approach instead of forcing every problem through one lens.

Applied AI

Microsoft Copilot

How it enters the work: Bringing AI into everyday productivity, enterprise information, and the tools where professional work already happens.
Our current perspective: AI earns adoption when it reduces the distance between a question and the work required to answer it without creating another disconnected destination.

Data & systems

Supabase

How it enters the work: Postgres-backed products, authentication, content systems, storage, and secure APIs that can grow with an initiative.
Our current perspective: A strong backend should make an experiment fast to begin and responsible to operate. Useful speed includes data ownership, clear boundaries, and resilience.

Knowledge

Notion

How it enters the work: Operational memory, research, planning, specifications, and shared context for people and AI systems.
Our current perspective: Documentation becomes leverage when it stays close to decisions and can be found, understood, and acted on by the next collaborator, human or agent.

Product engineering

Next.js · React

How it enters the work: High-quality web products and brand experiences that can move from an expressive interface to a durable application.
Our current perspective: The interface is part of the product’s intelligence. Technical credibility and a memorable experience should reinforce one another.

Delivery

Vercel

How it enters the work: Versioned collaboration, reviewable change, automated delivery, previews, and dependable product iteration.
Our current perspective: Shipping is a system. Small, inspectable changes and fast feedback create more room for ambition, not less.

Decision systems

Microsoft PowerBI

How it enters the work: Turning operational data into clear models, useful reporting, and decisions people can trust.
Our current perspective: A dashboard is not the outcome. The outcome is reduced uncertainty and a clearer next action.

Work systems

Azure DevOps

How it enters the work: Planning, delivery coordination, traceability, and the practical mechanics of complex cross-functional work.
Our current perspective: Process should preserve context and momentum. When the system becomes the work, it is time to simplify the system.

02 / How we choose

The tool matters.
The composition matters more.

CorbysReckoning stays deliberately broad because modern products are rarely created by one platform in isolation.

Use, then opine

We form a point of view through applied work, not feature lists, trend watching, or borrowed certainty.

Compose the advantage

The breakthrough is often in how tools are combined: model, data, interface, workflow, and human judgment acting as one system.

Stay tool-curious

The stack will change. The durable capability is learning quickly, choosing deliberately, and keeping the problem more important than the platform.

Broad capability.Applied with intent.