- Home
- Projects
Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy
129 projects in this portfolio, currently collected under Tech Domain · Book Dev — from web tools and mobile apps to internal systems.
Published counts projects that are running; internal tools have no public demo. Each label shows its evidence level.
Browse by outcome
120 projects · page 5 of 5
File text you reuse into a searchable list instead of losing it to the next copy.
Copying multiple snippets in a row meant losing earlier ones, and OS-native clipboard managers required a desktop install.
See when a cron expression will next run before deploying it.
Cron syntax is cryptic enough that a wrong expression could mean a missed or duplicated job run in production.
Count the days between two dates or shift a date without a spreadsheet formula.
Counting days between dates or adding a duration meant reaching for spreadsheet formulas or a clunky calculator site.
Keep the deep-link URLs for an app's routes in one searchable list.
Deep-link URLs for app screens were kept in scattered notes, so the right link was hard to find when handing it off.
Compare two blocks of text without installing a desktop diff tool.
Comparing code snippets or configs meant switching to a desktop tool or pasting into a heavy enterprise diff app.
Generate a SHA hash of text without opening a terminal.
Generating SHA hashes for quick verification meant a terminal command or a fragmented online tool.
Format, minify, and convert JSON to and from YAML in one tab.
Formatting JSON and converting it to YAML meant juggling single-purpose tools across different sites.
See real client-side latency, not just server-side benchmarks.
Choosing deployment regions needed latency data, but most tools measured from the server, not from an actual user's browser.
Write and preview markdown side by side without switching tools.
Writing markdown for blogs and docs meant switching between a separate editor and a separate previewer, with no live sync.
Minify HTML, CSS, or JS without setting up a build pipeline.
Minifying a quick code snippet for embedding required build tooling just for a one-off task.
See binary, hex, and decimal side by side while typing.
Converting between number bases for low-level debugging meant reaching for a calculator app or terminal command every time.
Write and test a redirect rule before it goes into real config.
Redirect rules were tracked in spreadsheets, with no quick way to check which rule a path would hit.
See a regex match highlighted live instead of guessing why a pattern failed.
Debugging a regex pattern with existing tools meant no real-time visual feedback on what was actually matching.
Transcribe a short voice take in the browser without paying for a transcription service.
Transcribing meeting notes required a paid service, even though browser speech recognition APIs already existed with no friendly interface built around them.
Summarize a long document without uploading it to a third-party API.
Summarizing research papers or transcripts required an API key or subscription just to compress text that stayed on the user's own machine.
Keep the small utilities you use in one searchable drawer.
With many small tools spread across different subdomains, finding the right one meant remembering a specific URL.
Encode or decode a URL or query value with the right function, and read its query parameters.
URL encoding for API calls and query parameters had edge cases — double-encoding, Unicode — that fragmented online tools handled inconsistently.
See every portfolio MCP server and its tools in one place.
MCP servers across the portfolio lived on many subdomains, with no single place to see what each one offered.
Reuse a working AI prompt instead of rewriting it from memory.
Effective prompts for recurring tasks were scattered across chat histories and notes, wasting time rediscovering what already worked.
Suggest a related project and show exactly why it was picked.
Manually linking related projects didn't scale, and visitors had no quick way to find a next project that fits what they want to do.
Check the tone of a piece of text without a paid NLP subscription.
Gauging sentiment in feedback or social mentions required paid NLP services or a complex model setup for a simple tone check.
Try a risky idea in a sandbox instead of cluttering a production codebase.
Promising technical experiments needed an isolated space to test, since ad-hoc trials were cluttering the main production codebase.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.