Projects
Showcase posts from members, newest first. Filter by the stack they built it with.
Shipped: Short link service
i tried build as much as the same which you requested · Repository: https://github.com/sarvarbekbro/URL shortner
Shipped: A service somebody else could run
Deployed an accounts backed habit tracker (Node.js, built in http and node:sqlite, no external dependencies) at https://habit tracker 1u6z.onrender.com, repo at https://github.com/mohammedoomatia max/habit tracker. Users sign up/log in and get a bearer token; every /habits... route requires Authorization: Bearer <token and returns 401 with a named field if it's missing or invalid. Ownership is enforced by scoping every habit lookup to WHERE id = ? AND user id = ? — a habit that exists but belongs to someone else returns 404, identical to a habit that doesn't exist, so IDs can't be enumerated by watching for 403 vs 404; test/acceptance.test.js proves this with a real two account test. The retry safe write path is check ins: POST /habits/:id/checkins is keyed on (habit id, date) with a UNIQUE constraint as the backstop, so the same check in sent twice returns the existing row (200) instead of creating a duplicate — reasoning is in the README. All 400 errors return {error, field} naming exactly what was wrong. No secret is committed: password hashing reads a pepper from PASSWORD PEPPER, set as an environment variable on Render, with only a placeholder in the committed .env.example. Run node test/acceptance.test.js to verify the first four reviewer checks automatically (18/18 passing) · Repository: https://github.com/mohammedoomatia max/habit tracker
Shipped: Library loans
Built a library loan tracking service on Node's built in node:sqlite module (no external dependencies). Schema has four related tables — books, copies, members, loans — with foreign keys from copies to books and from loans to copies/members. Seeded with 12,000 loans. GET /members/:id/loans returns a member's currently checked out books, most recently borrowed first, and responds in under 1ms on the full dataset (well under the 200ms bar) once the idx loans member active borrowed index is added — the README shows the real EXPLAIN QUERY PLAN output and timings both before (0.283ms, table scan + sort) and after (0.005ms, direct index search, no sort) adding it. Double lending is blocked at the database layer by a partial unique index (UNIQUE INDEX ... WHERE returned at IS NULL), not application code — test/acceptance.test.js proves this by inserting directly against the database, bypassing the server entirely, and confirming SQLite itself rejects the second active loan. Run node test/acceptance.test.js to verify all five reviewer checks automatically, or node scripts/measure query plan.js to regenerate the before/after evidence. · Repository: https://github.com/mohammedoomatia max/library loans
Shipped: Bookmark service
Built a zero dependency Node.js HTTP service for saving bookmarks, with create, list, get by id, and delete endpoints. A reviewer can verify the criteria by running node test/acceptance.test.js, which starts the server and automatically checks all five requirements: three plus endpoints with documented status codes; malformed input (missing url, empty string, a number instead of a string, a 2KB url) returning 400 with a message naming the field; no request producing a 500; and sending the same create request twice leaving exactly one row, since the service keys on the url itself and returns the existing bookmark with a 200 instead of creating a duplicate. The README explains the reasoning behind that dedupe approach and has curl examples for manual verification too. · Repository: https://github.com/mohammedoomatia max/bookmark service
Shipped: Conference schedule
Built a conference schedule page for a fictional two day event (Converge 2026) with Next.js 16 and Tailwind v4. · What it does:
Shipped: Conference schedule
I built a responsive two day conference schedule with three parallel tracks: Frontend, Backend, and Developer Experience. · Each session is keyboard accessible and opens a detailed session dialog with proper focus management. Reviewers can use Tab to navigate through the interface, Enter/Space to interact with controls, and Escape to close the dialog and return focus to the triggering session. Visible focus indicators are provided across interactive elements. On desktop, all three tracks are displayed side by side for easy comparison, while on narrow screens, a keyboard accessible track selector displays one track at a time alongside the time column, preventing horizontal page scrolling at 320px. The README documents the responsive design decision, accessibility approach, and keyboard testing checklist.
Shipped: Short link service
I built an HTTP short link service (Node.js + Express) that creates a short code for a URL, redirects on lookup, and tracks how many times each code has been followed. · To verify the acceptance criteria:
Shipped: Conference schedule
What I built: · A single page for a two day conference with 3 tracks (Build, Design, Workshop). Sessions are buttons that open a dialog with their details. It's all HTML, CSS and a tiny script, no libraries. On wide screens the 3 tracks are laid out side by side in their time slots. On narrower screens they flow into a single list, sorted by time, with each session noting the track and room. The reasoning is in the README.
Shipped: Recipe with adjustable servings
I built a responsive Pâté Chaud recipe page using React, TypeScript, and Vite. The page includes an ingredient list, an ordered cooking method, and a keyboard accessible slider that adjusts the recipe for 12, 24, or 36 pastries. Changing the slider recalculates the ingredient quantities and triggers an aria live announcement for screen reader users. · A reviewer can verify the acceptance criteria by:
Shipped: A README for a stranger
What I built and how the acceptance criteria are met: I built a React + Vite GitHub Repository Search application that allows users to search GitHub repositories through the public GitHub REST API and view repository details such as name, description, language, stars, and last updated date. The README is written for a first time user and provides concrete prerequisites, installation and run commands, environment variable requirements, architecture, project structure, design decisions, available commands, and known limitations. A reviewer can verify the acceptance criteria directly by following the README from a fresh clone, running the documented commands, and checking the documented idle, loading, results, empty, and error states. The implementation also includes responsive behavior, visible keyboard focus states, semantic HTML, and accessible status/error messaging. The project was additionally verified with npm run lint (0 warnings/errors) and npm run build (successful production build). · Repository: https://github.com/kiths bit/github repository search
Shipped: Bookmark service
I built a Node/Express/Mongoose bookmark API with CRUD endpoints, strict URL validation, and duplicate detection by normalized lowercase trimmed URL. A reviewer can see the criteria in the README and tests: malformed input returns 400 with a message naming the url field, duplicate create requests keep only one row, and the API exposes create/list/get/delete flows with documented status codes. · Repository: https://github.com/Tushar Sharma hub/Bookmark Service
Shipped: A rebuild of one feature you use
What I built & how to review it: I rebuilt GitHub’s repository search as a focused React/Vite application using the public GitHub REST API. The reviewer can verify the acceptance criteria by opening the deployed application, searching for repositories, and testing the initial empty state, loading state, successful results, no results state, and API error/retry flow. The complete search experience is keyboard accessible with visible focus states, and the layout can be tested at a 320px viewport without horizontal scrolling. The GitHub repository contains the development history and README with setup instructions, scope, accessibility considerations, omitted features, and the comparison with the original GitHub feature. · Repository: https://github.com/kiths bit/github repository search
Shipped: Personal reading list
I built a Personal Reading List web application using React and Vite, backed by the Open Library Search API. Reviewers can search for books, view book details, add books to their personal reading list, remove them, and refresh the page to verify that the list persists through browser localStorage . The application includes clearly separated loading, error, and empty states. To make the acceptance criteria easy to verify without changing the code, the Reviewer Demo section at the top provides buttons for Show loading state, Show error state, and Show empty state, plus Reset demo. The empty reading list state also explains the purpose of the list and how to add the first book, while the error state explains what failed and what the reviewer should do. Reviewers can therefore test all required states directly from the live application, while the README documents the implementation, setup, API, persistence, and state demonstrations. · Repository: https://github.com/kiths bit/personal reading list
Shipped: Short link service
GitHub repo URL · ↓
Shipped: E-Commerce Price Tracker watches Amazon & Daraz, emails you when the price drops
Ever kept refreshing a product page waiting for a sale? I automated that. · Paste any Amazon / Daraz product URL + your target price, and it scrapes the live price, stores the history, re checks every few hours, and emails you the moment it hits your target.
Shipped: Personal reading list
A single web page for saving the books, articles, and links you want to get back to. Entries persist in the browser's local storage, accessed through a small async api layer (list, add, remove) that mimics a real REST backend including latency and failures so the loading and error states are genuine, not just mocked up visuals. · Repository: https://github.com/rocklegend14/personal reading list
Shipped: Recipe with adjustable servings
A pancake recipe with a servings stepper. Every ingredient quantity and every quantity mentioned in the method text is driven from one data source and recalculated when servings change nothing is hand duplicated, so the two never drift out of sync. · Repository: https://github.com/rocklegend14/Fluffy buttermilk pancakes
Shipped: A README a reviewer can follow
I built Task Desk, a deployable task management application with a responsive web interface and JSON API. A reviewer can visit https://task desk api.vercel.app to see the working UI, add tasks, search and filter them, mark them complete, delete them, and confirm the service status. The API can be verified at /api/health and /api/tasks, while the README documents the data model, environment variables, local setup, Vercel deployment, endpoint inputs and outputs, success and failure status codes, Mermaid request flow, known limitations, and scaling decisions. The repository also includes an MIT license, concrete Node.js prerequisites, and the DevConnect badge, allowing the reviewer to clone, run, inspect, and test the project without additional guidance. · Repository: https://github.com/azizulabedinazmi/Task Desk API
Shipped: A service with a job running behind it
I built and deployed relay/digest, a Vercel hosted service that accepts authenticated CSV imports through a responsive dashboard and returns immediately with 202 Accepted , while Vercel Cron processes the import in the background. A reviewer can visit https://relay digest api.vercel.app and enter the configured AUTH TOKEN , submit the sample CSV, and observe the import move from queued to completed . The service uses account scoped database queries so users cannot read another account’s rows, idempotency keys and unique database constraints make retries safe, and worker leases recover jobs that die mid processing while storing visible errors. The protected API returns 401 Unauthorized without credentials, CRON SECRET protects the scheduled worker, the README documents failure recovery and deployment, the repository contains the requested DevConnect badge and MIT license, and secrets are supplied through environment variables rather than committed to source. · Repository: https://github.com/azizulabedinazmi/Relay Digest API
Shipped: The data model, explained
I built the documentation for mern auth api, an Express/MongoDB auth API with one users collection. README.md covers every endpoint with its real status codes (including the handlers that hang), local setup with env vars and a seed script, and eight decisions I'd revisit at ten times the traffic. DATA MODEL.md describes the collection field by field and the implicit links between documents, and has a constraints table with what each rule prevents. It lists the queries that carry the load with the index each uses, names the unindexed reset token lookup as the one that breaks first at 10x, and includes the commands and seed script to capture the explain() plans. · Repository: https://github.com/abbasg dev/mern auth api