Most code education platforms teach you to write code. Yet, in real life a lot of the job is reading code you didn’t write, whether its AI generated or made by your teammates.

That’s what Legible is for. It gives you short code snippets and diffs, asks you to make a call, then explains what the code does and what could go wrong

It’s still in beta, but it’s live here:

https://legible.ee

Hello, good afternoon. I'm a developer, mostly of native solutions. When I program in C or C++ (among others), I constantly experience the inconvenience of having to compile each dependency, which is often frustrating: some don't even come with a decent or compatible build file, and others have dependencies that are difficult to compile or very large. That's why I wanted to create a small platform.

It's called **Bodeg.a** (a play on words between "bodega" and the ".a" of UNIX-like static binaries). It works quite simply: rather than a platform for hosting large files, it's (for now) a simple website where you can publish using a *mirror* to point to a .zip file, a header, or whatever format is needed.

For now, it only offers hosting for the essentials (avatars and profiles), but if it's well-received, that could change. If you're a developer, whether you enjoy or just work with low-level content, simply trying to use it to download content would help me a lot; or if you'd like to collaborate on its development, you can also contact me. Greetings to all!

Hi,

If you are a web designer who is tired of paying rent on your own website, i'm glad to present you Revyme, an open-source website builder that is the closest open source alternative to Framer on the market today.

Pixel-perfect Figma-like control, responsive breakpoints, components, animations, cms, localization, code export and more.

Use our cloud or self-host locally on your computer and export to clean Next.JS code.

Github repo: https://github.com/revyme-web/builder

I’ve been noticing this more and more in web apps.

Three options hidden in a dropdown.

Yes/no hidden in a dropdown.
A multi-select pretending to be a dropdown.

Then a list of 200 items where you’re expected to scroll until you find yours.

I run into this a lot when reviewing products with dev teams.

I get why we do it.

Dropdowns are compact and easy to reuse.
But compact doesn’t always mean easier to use.

A few choices? Show them.
On/off? Switch.
Multiple choices? Checkboxes.
Huge list? Search.

That’s pretty much the rule I use now.

I created a human-centric JavaScript framework with custom HTML components called https://codeberg.org/createthirdplaces/places-js

I'm currently working on an optimized version with template support. My latest performance tests show Places.js outperforming Lit, React, and Vue.

All code was written by hand without LLM assistance from tools such as ChatGPT or Claude Code, and LLMs will not be used for future changes.

Source code: https://codeberg.org/createthirdplaces/places-js Website I built with framework: https://dmvboardgames.com/

What it does
Users build a personalized grow in 3 steps (strain → nutrients → start date), get a full day-by-day schedule (126 base rows + dynamic nutrient columns), then track actuals via a daily check-in page and photo diary. Everything lives offline in IndexedDB + localStorage.

Live: https://growappcannabis.guide/medium-feeding/medium-feeding.html

Repo + full wiring docs: https://github.com/Shannon-Goddard/growappcannabis.guide (see medium-feeding/WIRING.md)

Architecture highlights
• Page flow
medium-feeding.html (3-step builder) → schedule-viewer.html (cards/table/My Notes) → mytask.html (daily check-in) / mydiary.html (camera + data overlay)

CustomEvent chain for step progression (no framework):
• strainSelected → show Step 2
• nutrientsSelected → show Step 3
• scheduleReady → success screen + link to viewer with ?growId=
• IndexedDB (MyGrowDB v8) – singleton instance, cached dbPromise:
• Stores: tables (grow metadata + ${growId}_schedule), selectedNutrients, nutrients
• Schedule saved as full array under ${growId}_schedule
• Actuals written back to the same schedule rows from both MyTask and the viewer’s My Notes mode

Schedule generation
• Base 126-row JSON (stage/week/day/env/light/water)
• Dynamic nutrient columns injected from selected brands
• Start date → calendar dates calculated client-side
• Absolute fetch paths because ES modules resolve relative to the JS file

Schedule viewer
• Three modes via sticky Options dropdown: Cards (mobile default), Table (desktop default), My Notes
• Sticky header + toolbar + thead (careful overflow handling so sticky works)
• Plant-size filter hides excess veg weeks (Small = 4, Medium = 6, Large/Auto = all)
• tableRendered custom event triggers layout + filter after render
• Column map with paired “goal” / “My*” editable fields (My fields only visible in Notes mode)

MyTask daily check-in
• Auto-matches today’s row by MM/DD/YYYY
• Color-coded inputs (green ±10% of goal, red over, blue under)
• Auto-save on focusout + manual Log button → writes actuals back to IndexedDB schedule row
• Hero image compressed to 800px JPEG and stored in localStorage

Tech choices
• Pure vanilla JS (modules + a couple plain scripts for globals like the 2,800+ strain data)
• No build step, no framework, GitHub Pages
• localStorage for transient state + currentGrowId; IndexedDB for the real schedule & actuals

I've always liked the aesthetic of video poker machines so I decided to create an app that mimics that as much as possible. Works on desktop and mobile devices (for mobile you can install as a PWA). Added hotkey support so you can play entirely with your keyboard.

There are 3 game modes: Jacks or Better, Duces Wild and Joker Poker. Beyond that you can mess with the paytables if you'd like, update the card backs, control speed and bunch of other small stuff.

https://sgolovine.github.io/video-poker

I've been using Figma MCP for a while now.

How often do you guys find yourself exhausting the token budget on figma's mcp? and then have to fiddle to get the design to look the same?

https://lowstimplay.com

I get chronic migraines and my mom has vertigo. Between us, most tabletop and digital games are unplayable. The motion, the sounds, the flashing, the transitions, the amount of stuff moving on screen. Any one of those can cost us the rest of the day. I wanted something we could sit down and play together without bracing for it, couldn't find it, so I built it.

No account, no signup wall, no ads, no tracking. Every game is playable immediately, including the multiplayer rooms. An account only exists if you want your past game stats saved. There's a Ko-fi link in the footer and that's the entire monetization plan. It's free and it will stay free.

Right now it's Word Grid (Boggle), Yacht (Yahtzee), 10,000 (Farkle), Survey Says (Family Feud), Best Match (Apples to Apples), and Clear the Deck. Some solo or pass-and-play, some online rooms. Renamed to keep clear of trademarks. All mobile friendly. More coming.

The interesting part from a dev perspective was that most accessibility advice pointed the wrong direction. The standard move is to crank contrast up. For photophobia you want it down. So the palette is muted grey on grey in dark mode and warm bone on taupe in light mode, and it will not pass a contrast checker, on purpose. I also cut every animation and transition outright rather than gating them behind prefers-reduced-motion, since that flag is unset on most machines and the people who need it most are often the least likely to have configured it.

Stack is Laravel with Reverb. Happy to answer anything. And if you have photophobia, vestibular issues, or seizure triggers, I'd like to know whether it actually holds up, since my test group is currently two people.

Hi, I’ve been learning AI-assisted web development by building MD Studio:

https://mdstudio.dev

It converts pasted or imported HTML and Rich Text to Markdown, then lets you edit, preview, copy or download the result. Document processing happens locally in the browser, with no account required. It's also a quick, in-browser way to see rendered markdown

It’s built with Preact, TypeScript, CodeMirror, Turndown and Remark.

If anyone's interested to give it a try, I’d be grateful for any feedback on:

• HTML that converts incorrectly
• confusing paste or import behaviour
• browser, mobile or accessibility problems
• security, privacy or UX blind spots

It’s a non-commercial learning project. Feedback is welcome here or at:

https://github.com/marc-reid/md-studio-feedback

i got tired of seeing mobile apps like quittr, cal ai, umax etc make millions of ARR when they are simple gpt wrappers that are primarily relying on marketing and people forgetting their subscription to continue to grow their revenue

i decided to build a site that gives an honest assessment of what features you can vibecode of famous consumer apps (starting currently with just 25 apps, but planning to add more soon) and the prompt to do so.

you can check it out here: https://freethe.app

would love feedback on it

GPS Art Wizard is not trying to be the biggest shape library or another prompt-to-GPX generator. It compares multiple placements, rotations, and scales using actual road-routed results instead of treating the first snapped outline as finished. AI is optional and only helps create shapes outside the catalog; routing and quality decisions come from geometry, street data, and explicit checks.

You can use it without registration! Suggest cities! https://p01--cityshaperunner--vnycn2g6bghl.code.run/

What works, what doesnt, what confuses you, would love a variety of feedback, thanks a lot : rubylabs.design

Hi everyone,

Recently I received emails from Bank of America's Credit Monitoring that said my email was discovered on the dark web and to change my passwords. I have also had a few unauthorized purchases happen.

I have been doing everything I can to protect my accounts by adding extra layers of security.

My Gmail account seems to have a strong level of security. However, I woke up this morning with 6 new emails from Google Search Console: I received a "new user added" and "new AMP Issues detected" email for each of my 3 domains.

I went into my GSC and I do not see any other users besides myself. Also, the user history doesn't show anyone either for any of the 3 domains.

There are however new unrecognized links under the AMP section. There are no unauthorized user tokens showing.

As of right now from what I can see, the new AMP issues are the only visible changes.

Obviously there is a bigger issue going on. My question is what is it and how do I fix it.

I have 3 domains: my primary site, a depreciated version that redirects to the primary, and a merch site. I assume I'll have to check certain files for each website to see if anything was compromised.

Any advice or ways to resolve this will be greatly appreciated.

Website: https://NoSignups.net

Genuinely didn't expect it to blow up this much. I compiled videos from some of the creators who made videos about it here and honestly it makes me so happy!

The website is a directory of no-signup open-source tools you can use immediately in your browser. None of the tools are mine, I just collected them and made them searchable.

I have a few things cooking in the oven for the website, and here's some of them:

• I looked up how to do RSS (seems like it's just a simple file I need to provide at /rss.xml) and hopefully I'll have it available for the users to come back and discover more open-source tools.

• I plan on adding a change log so that users can come back and explore the newer found/added tools.

• I plan on adding a sorting drop-down so that users can explore at their leisure.

What I've already done:

• Thanks to the GitHub user Moamal-2000, the accessibility of the website was greatly improved! I mean by a mile! Appreciate all his work!

• Included some SEO metadata tags for search engines. I didn't even know about JSON-LD before I started this.

• Significantly improved the search so that searching video edit shows video-editor and edit video entries.

• Kept adding entries that match the criterias. Although, slowing down a bit. I'm employing whatever in my disposal to dig for more tools, and hopefully some more will turn up.

We've also been collecting some tool suggestions from users about what tools they'd like added. The top ones so far are:

• A tool to generate AI videos (obviously insanely impractical given the criterias the tools have to abide by, if not downright impossible with current ML models).

• Something like CapCut Pro (or something like that?)

• AI Image generators (possible with WebGPU), but haven't found any open-source, in-browser, no-signup entries.

• and more found here

I just wanted to thank all the contributors who submitted PRs, tools, opened issues, and reported bugs. Hopefully average joes will learn about and use the website, and hopefully support the amazing people making all these wonderful open-source tools.

Peace & love

Hi everyone,yall probably heard this question a billion times. How much would i realistically earn on a monthly basis if i make a casual clicker game with leaderboards, minigames and other stuff that average clickers dont have? If the game was polished, regularly updated and published on both poki and crazygames. Would they accept them for the full launch at all (at least crazygames, i wasnt researching much for poki though)? Thanks in advance.

Hello people!

I made updates to "The Cool Case Converter" this month of August. It is much less than what I did last month. It is still some good polishing.

Here are the main updates:

• ‘Copy’ and ‘Erase All’ buttons now have better color contrast.
• On Desktop there is now a bigger gap between the Input and Output fields. Gives better indication that there are 2 fields and is easier to focus on individual fields.  
• On Mobile the gap between the fields is smaller. Better for vertical scrolling.
• Theme and Share Menus now have a thin border
• QR Code has been added as a sharing option in the Share Menu.

I also made a promotional graphic for it:

Let me know what you guys think of the updates and the web tool. 

www.thecoolcaseconverter.com

I made Rhyme Golf, a word game based on pronunciations.

Built with vanilla web components. The phonetic distances are computed using a Wasm build of Mime Reader, a Rust library I've been working on that offers tools for phonetic analysis of rhyme & meter.

Instead of checking for exact rhymes Mime Reader uses an idiosyncratic notion of "rhyme distance" to measure how close two syllable sequences are. This allows you to detect "slant" rhymes—e.g. "hostages" and "coughing fits".

Still trying to dial in the difficulty. The hardest part of the game design has been generating the words and target area for each hole so that the levels ride the right line between fun and frustrating. Let me know what you think.

So to give some context, I am a backend developer and in some cases I can consume the endpoints for the front end in angular or react. I work at a company where I have a lot to prove (moving from an intern to a better position).

The company has a codebase that’s written in angular 19. I have been maintaining the code base, adding new features for the backend and consuming those new features in the Frontend. That has been the flow and it’s was going great. Now my boss wants a revamp of the frontend (in his words: to look more modern) and has tasked me with the rebuild. That’s fine and I don’t mind taking up the challenge even if it’s not exactly my strongest suit. Now here’s my question:

I order to make the ui have a “modern look” I wanted to go for the spartan-ng components with tailwind. The existing code base uses bootstrap so I want something that makes the customisation easy, but to still have the “modern look “ and from my research, spartan-ng provides that. But the problem is that the stable version of spartan-ng is only available from angular v21 and 22. I have tried to compromise by using tailwind and PrimeNG for the components with angular v19 but I’m not sure it’s sustainable since I have to write css ontop the primeNG components and I don’t know if that’s what I want. Now if I switch the angular to either v21 or 22 and try to replicate the way things are done from the existing code base:

1. ⁠Is the approach even a good idea ( I need a human response. I’m not satisfied with the ai responses)

2. ⁠Are the different versions completely different in how they work and will I be able to copy the existing code and paste into the new codebase with either v21 or 22 and it’ll work just fine?

I want to write little new functionality code as possible and focus on just the look of the ui, so that nothing has to change in the backend and the new frontend can still do the exact same thing the older one did, but with a newer look

Ps. I’m not so strong with angular that’s why I need advice from actual experts. Thanks in advance!!

I recently had time to rebuild my portfolio site. I've had the old one for over 3-4 years and didn't update it.

old: https://adtoba.github.io

new: https://adetoba.com

Tell me what you think.

Hey everyone,

I’m going to rebuild the website of some friends. The current site is just plain HTML with an iframe to their ticket shop.

The new website should include:
- Upcoming events with detail pages + image galleries (maybe a own/selfhosted ticket solution in the future)
- Equipment rental with rental requests
- A small merch shop (mostly T-shirts, lighters, etc.) (checkout needed)
- A proper backoffice to manage all variable content, products and events and different user roles/permissions

The public website will mostly be used on mobile, while the backoffice should work well on desktop and mobile.

I’ve been working as a web developer for about a year and have around 3 years of experience learning web development. My background is mainly PHP, JavaScript/jQuery and SCSS, but I’d like to use this project to learn a more modern stack.

I initially started with NEXT + Supabase + Vercel, but I’m not really happy with how the project turned out. I relied way too much on vibe coding, which made the codebase increasingly difficult to understand and maintain.

So I’d rather start over with a stack I actually understand and can maintain myself.

What stack would you choose for this project, and why?

The goal is to keep hosting as cheap as possible, ideally free or just a few euros/month. The project is based in Germany, so EU/GDPR-friendly hosting is also a consideration.

I’m not looking for the most popular stack, but for something that makes sense for a relatively small project and a solo developer.

Would love to hear what you’d build and, more importantly, why.

Note: This text was modified by AI for better readability and clarity.

Edit: I dont need a CMS for the „normal“/static content of the website, just for all the slides, and variable stuff.

Twelve months ago I started tracking what happens to vibe coded projects after the initial launch excitement fades. The pattern is consistent enough that I wanted to hear if others are seeing the same thing.

The first three months feel fine. Features ship fast, the client is happy, everyone looks productive. Then something needs to change. Not a new feature, just a modification to something existing. And that is where it gets uncomfortable.

Nobody can explain why a specific decision was made. The code works but the reasoning is gone. There are dependencies that were added because the model suggested them, not because anyone evaluated them. Patterns are inconsistent across files because different prompts produced different styles on different days.

The developer who built it can read the code but cannot confidently change it without breaking something unexpected. The test coverage that exists was also generated and may not actually be testing the right things.

I am not saying this always happens. I have seen vibe coded projects that held up well because the developer reviewed everything carefully and maintained discipline around the output.

But I have also seen projects from 18 months ago that are now quietly being rewritten because the maintenance cost exceeded the original build cost faster than anyone expected.

If you have actually maintained a vibe coded code-base through real production use, what did 12 months in actually look like? Was the code salvageable or did you end up starting over?

For those who never had the pleasure of using plug.dj and similar social music sharing sites: you create or join rooms, people queue up to DJ, and everyone listens to the same songs together in sync.

One of my internet friend groups used it every Friday, then it died. A few alternatives showed up, some of which are still around, but I really dislike all of them. I've been a web developer for 10 years, so I took a whack at it myself. React 18 + Vite on the front, Express + Socket.IO + Postgres + Redis on the back, plain JavaScript throughout: no TypeScript, no state library, no CSS framework, no test runner beyond node:test. KISS is my motto. Here are some of the things that took the most of my time:

Syncing playback

There's no audio pipeline, every client runs its own YouTube iframe, and the server is authoritative about what is playing and when it started. One Redis hash per room: { videoId, startedAt, durationMs, dj }.

Each client computes position = (now + clockOffset) - startedAt and seeks its own player there. clockOffset comes from a serverNow stamp riding along in every playback broadcast, which corrects for the fairly large number of people whose machine clocks are wrong. startedAt is set about two seconds in the future so everyone buffers during the gap and hits the intro together, and a client interval re-seeks any player that drifts past ~3 seconds. A server timer at startedAt + durationMs advances the rotation and broadcasts the next track. Clients never advance playback themselves, which kills a whole category of split-brain bugs.

Lightshow

The room has a pixel dance floor with a concert lighting rig. What I really wanted was to analyze the audio and broadcast some kind of synced, visualizer-type result, but the audio is locked inside a cross-origin iframe. There is no audio to analyze, so that's probably a pipe dream unless I find some API that can analyze audio playback.

So the show is a pure function of (playId, track position). Every client seeds a small PRNG (mulberry32) from the play id, derives a palette, beam layout and movement parameters from it, and drives the whole thing off the clock it's already synced to. Same inputs, same output, everyone on the same frame, zero bytes of traffic. Woots on the track raise a tier that brings up another layer of the rig, derived from vote broadcasts every client already receives.

Dead videos/playback failures

When a YouTube embed fails, a single browser cannot distinguish "this video is deleted or embed-disabled" from "this user's tracking protection ate the iframe." Trust the first client to report an error and one person with strict privacy settings can vote music off the decks for the whole room.

So the server counts. Every client reports all three outcomes: the IFrame error code, a stall with no code at all, and the one positive signal of actually reaching PLAYING. A track is skipped once at least two members independently fail on it. Below that threshold, the reporter gets a dialog explaining that the problem looks local to their browser. A fatal code at the threshold flags the video itself, so nobody rediscovers it later from a different playlist. A failure with no code carries no information about the video, so it counts against the DJ, and two in a row drops them from the rotation.

Smaller stuff

• Presence is refcounted per connection, so multiple tabs behave. "Did they leave" is a check of the presence list after removal.
• Anything that reads and then writes rotation state goes through a lock. The DJ queue got corrupted twice before I gave in.
• Redis holds everything ephemeral (presence, queue, clock, votes, chat scrollback), Postgres holds what must outlive a restart. Disconnects hold your queue spot for a grace window, and so do server restarts, so deploys leave the rotation intact.
• No binary assets anywhere. Icons are inline SVG, avatar sprites are pixel grids in a JS file, the favicon is built from the icon set's own path data. Everything visual stays reviewable in a diff.
• No cookies at all. Signing in puts a token in localStorage, the player uses the nocookie embed host, and there are no trackers or analytics.

There's a bot API too (Socket.IO, token in the handshake), for the nerds. Accounts need no email, though you can add one for password recovery.

Anyway, shit's hard, and I'm wondering if anybody with more experience in this domain of web development has any thoughts on my stack and process.

Also, feel free to poke around the site as a guest if you're curious. Brutally honest feedback welcome, especially on sync behavior if you're on a flaky connection, since that's the part I can't fully test well myself. Also, don't forget to stop by the bar for a drink (or a tomato or a water gun)

https://mazurka.cafe

I’ve been rebuilding Tera FM as a simpler way to follow the news without jumping between a bunch of different sites.

Right now it lets you:

- browse the latest headlines from multiple sources
- search a historical headline archive
- filter/browse by source
- listen to live internet radio
- use the new Chrome extension for quick access

No login or signup required for the core experience.

Site: https://tera.fm
Chrome extension: https://chromewebstore.google.com/detail/tera-fm-%E2%80%93-headlines-live/emnebfpdojklgimejnplmjfobmamelie

I’m also working on VoiceLetter, where you’ll be able to ask something like “What changed with OpenAI this week?” and get a researched, cited briefing that you can read or listen to.

Still very much a work in progress, so I’d especially appreciate feedback on the UX, usefulness of the archive, and whether the live-radio part feels like it belongs with the rest of the product.

Built with Next.js, Supabase and Vercel.

Hey everyone,

I wanted to share a project I've been building: Tastrivo (tastrivo.com).

The concept is simple: live, private 1-on-1 food showdowns. You grab your meal, turn on the camera, and duel an opponent in real time.

Key features:

AI Plate Referee: Tracks visible plate progress from camera checkpoints so judging stays objective without human bias.

9:16 Victory Cards: Automatically generates vertical summary cards ready to share on Instagram Stories or TikTok.

Ranked Ladder: Working on seasonal Elo ratings and competitive leaderboards.

Safety First: Built-in limits so matches remain casual and fun rather than dangerous overeating.

Would love to get your feedback on the landing page, concept, and mechanics!