- Home
- Projects
- Explore by Domain
- Tech Domain · Book Dev
Tech Domain · Book DevProjects
31 projects in Tech Domain · Book DevFocus: Dev & AI Tools
Published counts URLs that respond; each project label shows its evidence level.
Browse by domain
Browse by outcome
31 projects in Tech Domain · Book Dev in Dev & AI Tools · page 1 of 2
Find a reused code pattern in seconds instead of digging through old repos.
Frequently reused code — Docker configs, CI templates, CSS utilities — was scattered across repos and gists with no fast way to find it again.
Grab a color palette that's already accessibility-tested, not just aesthetically nice.
Palette sites varied wildly in quality, and none guaranteed the combinations actually passed WCAG contrast checks.
Convert a color between HEX, RGB, HSL, and OKLCH without switching tools.
Converting colors between formats meant bouncing between different single-purpose converter sites, each missing accessibility checks.
Design a LINE rich menu visually instead of calculating tap-area pixels by hand.
LINE rich menus needed pixel-precise tap areas, and doing that math manually in Photoshop was slow and error-prone.
Practice design and frontend skills, not just algorithm puzzles.
Challenge platforms like LeetCode only tested algorithms, leaving no structured way to practice design or full-stack building skills.
See how 100+ projects' technologies actually connect to each other.
The portfolio used dozens of technologies across 100+ projects, but nothing showed how those technologies related or overlapped.
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.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.