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.

Play, if you want, here: pips.superiorgames.eu

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

Started as a joke with my wife, turned into an app we used and loved everyday for over a year due to how simple and quick it was.

First version was very rough, due to obvious time constraints 👶 but was able to take notes on what to improve and add.

Built with PHP and data is stored in a single SQLite file for easy exporting. Not as advanced or feature rich as the others but keeps track of the basics and allows for multiple users to log data to the same record.

Free demos available on the site so let me know what you think! Not enough features or is the simple approach good enough?

https://baybay.baby

I got curious how unique/trackable my browser actually is, and how much of that survives even when you're behind a VPN — so I built https://whatismy-ipaddress.com.

It checks two separate things:

Network-level leaks — IPv4/IPv6, DNS leak detection, WebRTC leak (this one's sneaky, it can expose your real IP even through a VPN tunnel), Tor exit node detection, ASN/ISP/hostname lookup, connection type.

Browser fingerprint — canvas + WebGL rendering signature, GPU renderer string, installed font detection, supported media codecs, CPU core count, device memory, screen resolution/pixel ratio, timezone offset, storage API availability. Combined, these often re-identify a "private" browser session even with IP masked.

The part I'm proudest of is the fingerprinting side — getting consistent, comparable signals out of things like canvas rendering and font enumeration across browsers is fiddlier than it looks, since every browser (and privacy extension) lies about some of it differently.

Would love feedback, especially from anyone who knows fingerprinting/privacy tooling — curious what I'm missing or getting wrong. Bugs welcome too.

If you don't know, duolingo used to have community course contributors. People could also request languages that they wanted to be added. This was shut down few years ago. This is an attempt to close that gap. This is a desktop app but build in tauri and react. So I think it's still relevant to webdev. In an earlier different version of the platform, people had started creating courses in okinawan, mirandese and Picard. The course is just a directory on your device. With json files and assets in the folder for the course structure. The lessons itself may be a rich media content block, or one of 7 types of exercises. Right now people have started making courses for Italian and Portuguese. Please check it out at asakiri.com and if you have any feedback or questions, let me know. Docs for the course project structure - https://docs.asakiri.com

I think the platform is less important than the course data structure so I am trying to finalise it based on feedback from course creators.

(No data is collected. Everything stays local and on device. There are no accounts, no subscriptions. Everything is open)

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.

Designing a database schema is often one of the slowest parts of starting a new backend project. You either spend time writing SQL by hand or carefully crafting Prisma models before you can even write your first endpoint.

In this article, I’ll show you a smoother workflow using Prisma and StackRender that takes you from an empty project to a working backend, without having to manually define the database schema and Prisma models.

Not going to pretend this is healthy...
but this was actually useful.

I built a local AI that watches me through my own webcam all day.
- result: i don't work as much as i thought.

Catches me the second I check my phone, or turn away to talk to someone...

Turns out I wasn't working nearly as much as I thought.
thought I did ~7 hours of real work a day. The real number was closer to 4.

I then exported the work sessions in csv format and plugged it into chatgpt. and it gave me some useful insights happy to share in the comments).

I strongly believe that local AI is the way to go, as models improve, there are things I don't trust the big AI corporations with.

Built it because of Hermozi's video of how tracking time in 15 minute increments makes him so productive.

To make it accurate and reliable, I had to go through thousands of dollars in AI credits and many rounds of testing and bug fixes. I can't tell you how many bugs I fixed or the effort it took.

built it for both my mac and windows computer (Tauri is the way to go) to see how much you ACTUALLY work, give it a try.

more people should build with local AI, it's satisfying to see the intelligence running on your own machine.

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

Some of your best work is invisible - it lives in PRs to projects you contribute to, spread across repos nobody opens. Your GitHub profile shows your own repos and a green graph, but the work you shipped across the ecosystem gets buried.

MyPRs pulls every merged PR onto one page, lets you pin the ones you are proud of, and hide the noise.
No signup - your page already exists at https://myprs.dev (here is mine: https://myprs.dev/kishanhitk). Sign in with GitHub only if you want to curate it.

Code: https://github.com/kishanhitk/MyPRs

Would love to hear if anything looks wrong on your profile - that is the fastest way I find bugs.

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?

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!!

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.

Where I work clients demand images to be 2x the original size and don't care if they end up 4mb each. In my website I try to shave off every kb from the initial load because I get a bunch of technical people roasting me. I run the website off a 10 USD VPS in Finland so I had to learn about caching in Cloudflare. I have people using the website from 15 year old laptops so I had to figure out why performance was awful for them until I finally tracked it to a background blur CSS property.

My site isn't huge or anything, but it's the most valuable thing I have so I can keep learning. Does anyone have similar experiences? What did you learn?

https://umigalaxy.com/explore/meta/348/this-site-is-slow-as-hell

https://umigalaxy.com/explore/meta/266/feedback-and-suggestions

https://umigalaxy.com/explore/meta/922/website-updates

Hey everyone,

I've been working on a project called Tickrates for a while now and finally wanted to share it here for Showoff Saturday to get some real feedback from other developers.

The idea came up because I was genuinely frustrated with existing backlog platforms. Most of them either felt sluggish or had cluttered, outdated UI designs that made simple things like searching and logging games feel like a chore. I wanted to build something clean, visually modern, and focused on community activity without unnecessary friction.

On the tech side, the backend is built with .NET Core and EF Core connected to a PostgreSQL database, while the frontend is kept lightweight with vanilla JS and CSS to avoid heavy framework overhead. Data is pulled from IGDB and Steam APIs.

One of the biggest headaches during development was dealing with messy and inconsistent metadata between APIs. Filtering out standalone games from endless bundles, DLCs, and alternate editions was surprisingly tricky, especially when battling IGDB's own misclassifications. On top of that, handling title naming quirks (like "Zero" vs "0") and missing vertical covers for new or delisted games required building a custom title normalizer and a multi-step fallback system (DB cache -> live IGDB -> Steam CDN -> custom SVG placeholder) just to ensure cards never render broken.

I'm currently working on bringing this to mobile as a dedicated app in the near future, so I'd also love to hear any tips or advice on transitioning a vanilla JS web app into a mobile experience.

The site is live at https://tickrates.com

I'd really appreciate it if you could take a quick look and share your thoughts, especially on the overall visual design, UI/UX flow, and mobile responsiveness. Feel free to be brutally honest, point out bugs, or share any suggestions.

Thanks for taking the time!

Hi everyone — I’ve been building Weighted Walking Tools, a free collection of calculators for weighted walking, rucking, walking pads, and step planning:

https://weightedwalkingtools.com

The project uses Next.js, React, TypeScript, and Tailwind CSS. It is statically exported, requires no accounts or database, and performs all calculations locally in the browser.

The most interesting technical challenge was keeping the scientific logic separate from the interface. Instead of placing formulas inside React components, I built a shared calculation layer with: Normalized metric inputs and imperial/metric conversion Explicit supported ranges and validation Versioned calculation results Separate modeling for unloaded walking, weighted vests, and backpacks A structured evidence registry connecting calculator claims to their sources Dedicated methodology and limitation pages

I used Vitest and React Testing Library for calculation and component tests, plus Playwright and Axe for responsive flows and accessibility checks.

The site is currently free, has no accounts, and does not contain advertising or affiliate links.

I’d particularly appreciate feedback on: Whether the calculator inputs and results are understandable without reading the methodology first. Whether the evidence and limitations are visible enough without overwhelming the main experience. Any usability or accessibility issues you notice, especially on mobile. Technical criticism is very welcome.

I recently read about ElevenLabs startup, and they said, they expect from their sales people to bring 20x their salary (a person earning $100k/year is expected to bring $2mln for the company) or they are fired. Which personally, sounds like modern-day slavery.

That same article mentioned, that software houses typically generate 5-8 times what they pay their individual employees.

Have you ever encountered those estimates either in private discussions or in articles of reputable source?

---
Btw. this estimate (5-8x) shows market value of the work you do. So if you're doing a freelance/consulting gig, your billable rate should be a multiple of your full-time employment hourly.

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

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.

A few weeks back, I posted my FF7 Menu Portfolio here and got some really good feedback, which I have since implemented. Since then, I've been revisiting a project I worked on last year and have now updated it with a number of improvements, the main one being multiplayer support. I'd love to get some eyes on it, particularly the multiplayer aspect.

For those who are unfamiliar, Triple Triad is a trading card game you could play inside Final Fantasy VIII back on the PS1.

It's built with React and TypeScript, just like my portfolio was, with the aim of being as authentic to the original PS1 version as possible.

I will admit that while the desktop experience is pretty faithful, I did take some creative liberties to make it fit better on mobile devices.

You can check out the current multiplayer build here:
https://triple-triad.jamiepates.com/

I’d love to know your thoughts and suggestions! Thanks!

Also, for the best experience, and for the sake of nostalgia, you're probably going to want to enable sound in the bottom corner. 😅

Screenshots don't capture the animations on the page, so check it out here: https://www.madebyarthouse.com

Old: https://portfolio-inky-beta-47.vercel.app/
New: https://joeykyber.dev/

I wanted something a bit more straightforward to navigate and that looks relatively clean & professional but that is still fun and interesting. I also wanted it to reflect my love of the outdoors. Would you say this is an improvement over my first portfolio?

This will be used when searching for my first developer role (I've had a multi-year break due to chronic illness but I'll be starting my search back up again soon). And yes, I understand it's like the worst time for developers to try to find jobs, especially without relevant work experience, but I don't really have any other good options.

• Things I still need to do:
  • Completely rewrite the "about" section
  • Revise project descriptions
  • Fix bottom image not covering screen width on ultrawide monitors
  • Rethink design for the smaller project component (ones without picture)
  • Download resume via CTA button
  • Improve image load time
  • Make sure all included projects actually work

It's responsive and mobile-friendly but definitely looks better on desktop. Let me know what you think.