Tech Domain · Book DevProjects
129 projects in Tech Domain · Book Dev
Published counts URLs that respond; each project label shows its evidence level.
Browse by domain
Browse by outcome
129 projects in Tech Domain · Book Dev · page 5 of 6
Compare religious traditions side by side with neutral, academic framing.
Understanding comparative religion meant reading multiple dense texts with no structured, neutral way to compare beliefs and practices.
Make the variable visible so the observation can be discussed.
Science concepts are easier to discuss when the input, response, and observation are visible together.
Run a small beam check without hiding the inputs and assumptions that shape the result.
Quick engineering checks become hard to inspect when inputs, formulas, units, and caveats are scattered across separate calculators.
Encode or decode Base64 without leaving the browser tab.
Base64 encoding for quick checks meant switching to a terminal or an ad-heavy site that choked on large inputs.
Search clipboard history instead of losing a copy to the next one.
Copying multiple snippets in a row meant losing earlier ones, and OS-native clipboard managers required a desktop install.
See exactly when a cron job will run before deploying it.
Cron syntax is cryptic enough that a wrong expression could mean a missed or duplicated job run in production.
Calculate working days between dates without a spreadsheet formula.
Calculating working days, adding durations, or handling timezones meant reaching for spreadsheet formulas or a clunky calculator site.
Test a mobile deep link without building and deploying the app first.
Testing iOS and Android deep links required a full build-and-deploy cycle just to check the URL format worked.
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 file hash without opening a terminal.
Generating MD5, SHA-1, or SHA-256 hashes for quick verification meant a terminal command or a fragmented online tool.
Format, validate, and convert JSON without four separate browser tabs.
Formatting and converting JSON between YAML and CSV meant juggling several 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.
Catch a broken redirect chain before it goes live, not after.
Redirects across 100+ domains were tracked in spreadsheets, with no visibility into broken chains until something actually broke.
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 voice memo locally 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.
Find any developer tool in the portfolio from one search box.
With 30+ tools spread across different subdomains, finding the right one meant remembering a specific URL.
Encode a URL's query string correctly the first time, including the edge cases.
URL encoding for API calls and query parameters had edge cases — double-encoding, Unicode — that fragmented online tools handled inconsistently.
Debug real webhook payloads without spinning up ngrok.
Testing payment, CI/CD, and form webhooks required a local tunnel just to see what a request looked like.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.