Feed
Feed
Stuff people are actually building today: bugs, wins, half-finished side projects.
build log
Jobs are live: 186 remote dev roles, plus voice notes in the feed
Three things shipped this week.
Jobs. The board was empty.
Now it has 186 remote developer roles, junior to lead, pulled in every six hours from the boards we watch.
Stack and level on every card, salary where the company states it.
If you're in the internship, your dashboard now shows the junior roles that match your track.
→ /jobs
Voice notes. Up to 30 seconds, in posts and in replies. Hit "Record a voice note" under the comment box. It counts as a reply like any other.
GIFs. In every comment. Be nice with them.
One ask: if you find a job on the board that isn't a real dev role, reply here with the title. The filter is new and I'd rather fix it fast.
Trailer below.
showcase
Shipped: Library loans
What I built
A Flask + SQLite API for a small library: books, copies, members, loans. GET /api/<member_id>/loans lists a member's current loans (newest first). POST /api/loans lends a copy.
How to verify each criterion
3+ related tables with FKs: app/models.py — copies -> books, loans -> copies, loans -> members.
10,000+ seeded rows: run python seed.py. Seeds 10,500 loans, 1,200 copies, 600 members, 300 books.
Under 200 ms: run python run.py, call GET /api/261/loans. Measured 7-26 ms warm (see README).
Query plan before/after index: seed.py prints EXPLAIN QUERY PLAN before and after creating ix_loans_member_open; both are in README.md.
Double lending blocked by a constraint: partial unique index uq_one_open_loan_per_copy on loans(copy_id) WHERE returned_date IS NULL. POST /api/loans returns 409 on violation. Tested: same free copy_id posted twice → 201, then 409.
Repository link: https://github.com/hassannnn13/Library-loans.git
Repository: https://github.com/hassannnn13/Library-loans.git
Built for the Verified Backend Internship · a data model and the queries on it
You're browsing as a guest
Sign up free to post, comment, vote and follow developers.
showcase
Shipped: Short link service
What I built:
A Flask + SQLite URL shortener with three endpoints: POST /links (create), GET /<code> (redirect + count visit), GET /links/<code>/stats (check URL + click count). All input is validated before it touches the database — bad requests get 400 with the exact field and rule that failed, never a 500. Short codes are a hash of the URL, so the same URL always maps to the same code, making creation idempotent.
How a reviewer can verify it:
Create/follow/count — POST /links → 200 + code; GET /<code> → 302 redirect; stats endpoint shows clicks going up each follow.
301 vs 302 — README explains why 302 was chosen (not cached, so clicks are counted reliably).
Unknown code → 404 — confirmed by hitting a code that was never created.
Malformed URL → 400, nothing stored — confirmed by posting an invalid URL and checking its stats never resolve.
Duplicate URL → same code — confirmed by posting the same URL twice and comparing the two responses.
All verifiable with the curl/PowerShell commands in the README.
Repository link: https://github.com/hassannnn13/Shortlink-service.git
Repository: https://github.com/hassannnn13/Shortlink-service.git
Built for the Verified Backend Internship · an API that survives bad input
discussion
Backend internship
Hi, I'm a Full-Stack Developer building an AI-Powered Scholarship Finder using Next.js and Django REST Framework. The project integrates NLP for student profile matching and GenAI to automatically assist users in drafting high-converting SOPs.
showcase
Final Touches in Python Practice Repository for Learners
Short Reminder:
Just 2 Modules are left
GitHub Repo:
hasheramin5-cyber/Python-Practice-Repository
github.com
showcase
Shipped: Three decisions, written down
I created a decision record for Nodex documenting the major architectural decisions, alternatives considered, reasoning, and trade-offs. The DECISIONS.md covers the local-first architecture, Web Worker processing, React Flow + Dagre, Zustand state management, IndexedDB persistence, URL-based sharing, and primitive-only graph editing.
The reviewer can open DECISIONS.md in the repository to verify the decisions and their associated costs/trade-offs. The existing README already covers the project architecture, setup instructions, testing, scope, and deliberately unimplemented features.
Repository: https://github.com/riki-k-dev/nodex
Live: https://nodex-jv.vercel.app
Built for the Verified Frontend Internship · Documentation
showcase
Shipped: A tool for a problem you have
I built Nodex, a local-first JSON visualizer and editor that turns deeply nested JSON data into an interactive graph, making complex structures easier to understand, navigate, and edit.
A reviewer can verify the project by:
1. Pasting or editing JSON and seeing it represented as an interactive node graph.
2. Editing primitive values directly from the graph and verifying that the JSON editor updates accordingly.
3. Collapsing and expanding nested objects and arrays to manage complex structures.
4. Using Cmd/Ctrl + K to search for nodes and navigate directly to them.
5. Refreshing the page to verify that the current workspace persists locally.
6. Generating a shareable URL and opening it in a new browser session to restore the same JSON.
7. Exporting the graph as a PNG.
8. Testing empty, invalid, and malformed share-link states to verify that failures are handled without breaking the application.
9. Switching between light and dark themes.
The README includes local setup instructions, project architecture, testing details, limitations, and a section explaining what was deliberately not implemented. The repository also contains the project's development history through Git commits.
Technologies used: Next.js, React, TypeScript, Zustand, React Flow, Monaco Editor, Tailwind CSS, Framer Motion, and Web Workers.
Repository: https://github.com/riki-k-dev/nodex
Live: https://nodex-jv.vercel.app
Built for the Verified Frontend Internship · Final project
Marketplace
Templates, tools, component libraries and MCP servers, built by members. Free or paid, your page, your link.
Visit marketplaceshowcase
Shipped: Conference schedule
I built a single-page schedule for a two-day conference with three parallel tracks (Build, Design and Ship). It works with the keyboard alone and at 320px wide. It is plain HTML, CSS and JavaScript with no libraries.
How parallel tracks work on narrow screens: the page is a list of time slots, not columns. On wide screens the three sessions in a slot sit side by side so you can compare them. On narrow screens they stack under the time heading in the same order. A track filter (All, Build, Design, Ship) and day buttons keep a phone screen short. The reasoning is in the README.
How a reviewer can verify it:
Keyboard order: press Tab from the top. You pass the skip link, the day buttons, the track filter, then the sessions in time order. There is one DOM order for every layout, so tab order always matches what you see.
Visible focus: every button and the skip link shows a 3px orange outline.
No horizontal scroll at 320px: set the viewport to 320px wide and confirm there is no sideways scrollbar.
Session details without a mouse: press Enter on a session to open its dialog. Escape or the Close button dismisses it, and focus returns to the session you opened.
README: explains the narrow-screen decision and includes a short keyboard test checklist.
Repository: https://github.com/ibn-azam/NorthLight
Live: https://github.com/ibn-azam/NorthLight
Built for the Verified Frontend Internship · accessible layout
Repository: https://github.com/ibn-azam/NorthLight
Live: https://ibn-azam.github.io/NorthLight/
Built for the Verified Frontend Internship · accessible layout
showcase
Shipped: Short link service
i tried build as much as the same which you requested
Built for the Verified Backend Internship · an API that survives bad input
sarvarbekbro/URL-shortner
github.com
discussion
RunsOnMac - Discord
Hey guys!
I’m currently building a website called RunsOnMac, a community-driven gaming database made specifically for Mac gamers.
The goal is simple: to create a place where Mac users can find real-world gaming performance data, community benchmarks, compatibility information, and eventually a much clearer picture of what actually runs well on different Macs.
Since I’m much more active on Discord, I’ve also opened a small Discord server dedicated entirely to the project. That’s where I’ll share the latest updates, development progress, previews, and new features first.
If you join now, you’ll be one of the earliest members of a project that I have some pretty big plans for.
If you’re into Mac gaming, benchmarking, testing games, or just want to follow the development of RunsOnMac from the beginning, you’re more than welcome to join.
discord.gg
BCZXyNTmV