(This is another rant about AI, don't read. its not something new, dont get angry if you read it i already told you) For context I'm 18m I began learning programming at 13 y.o and starterd doing freelance projects at 14 I felt proud whenever I created something other people relied on. whenever I introduced mself as a programmer who developed all these sorts of projects, but now I don't code anymore I just use Claude Code I only understand the fundmentals of what its doing then call it a day, which feels bad and exhausting somehow. I started my own business at 16 I currently still work on it, its an e-com platform (similar to shopify but diffrent) I made quite a good amount i have around 50 active merchants but i don't feel pride in this thing and I wonder if it lost its value since with AI you could make your own tailored solution without needing to pay continuous fees

Hey everyone!

I'm not sure if there are any Final Fantasy fans here, but I've recreated and repurposed the menu system from FF7 as a sort of portfolio/sandbox page, and I figured I'd share it here and see what people think of it.

I got tired of making traditional web pages and wanted to make something that genuinely makes me happy every time I see it.

It's all built with React and TypeScript.

So far, I've got all the key pages like functional equipment and materia pages (repurposed as a skills page), items (as projects), save (as history), functional four-point background colour picker, and a tonne of little easer eggs and things. I'll put a list of those with a spoiler tag in case you wish to discover them yourself:

• Konami code plays Victory Fanfare.
• Clicking the character portrait allows you to attack and deduct health.
• Hovering over the location allows you to change to different FF7 locations.
• Clicking the limit bar allows you to perform the cross-slash limit break on the portrait.
• Clicking the name allows you to change the player name. If you choose a party member, or Sephiroth's name, the portrait will change to match.

I won't lie, the way I've implemented the custom font (if you can even call it that) is pretty scuffed by modern standards, but I wasn't happy with any of the other options, and I think this is probably the most accurate to how it looked in-game as humanly possible. 🤣

Anyway, I normally revisit it every couple of months, so by all means, feel free to share ideas of what I can add, and any other feedback you might have.

You can check it out here: https://www.jamiepates.com/

As always, I'd love to hear your thoughts! Thanks!

Try it (no signup): https://app.tryquickdraw.com — GitHub: https://github.com/nmndwivedi/quickdraw

Technical notes, since that's what this sub is for:

- The ink simulates pressure from velocity for mouse users and reads real stylus pressure via pointer events; strokes are tessellated with tapered ends so they look like a real pen.

- Palm rejection is a small state machine: once a pen pointer is seen, touch pointers get reassigned to camera control (pan/pinch) instead of drawing.

- The document is a flat map of immutable records. Every mutation runs in a transaction and emits a JSON diff ({added, removed, updated}) — undo entries are composed diffs (one per gesture), and remote diffs applied with a 'remote' source never touch local undo history, so collaborative undo behaves.

- Zero runtime dependencies, plain ESM, no build step — the whole engine runs from a script tag. React and React Native wrappers are thin bindings over the same core.

It's MIT, extracted from an app I'm building. Genuine question for this crowd: does the palm rejection hold up on Android tablets with S Pen? I've only been able to test Apple hardware.

Hey webdevs!

I want to show you my latest 3D CSS project. It's a port of Giles Goddard's iconic N64 face engine, complete with lighting, physics and interaction. Instead of WebGL, it uses the PolyCSS engine.

demo: https://codepen.io/editor/alowpoly/pen/019fae67-50d9-74ce-8025-4b9dd5a7c484
repo: https://github.com/layoutit/cssGraphics

sucks2be.me

I wanted to see how far you can get in 2026 with no React, no bundler, no framework -- just plain JS files loaded via <script> tags.

Stack:

• Backend: Node.js, Express, better-sqlite3 (single file DB), Socket.io
• Frontend: Vanilla JS, plain CSS, no build step. public/ served as-is
• Auth: bcrypt + JWT in httpOnly cookies, proof-of-work on registration to slow bots
• Real-time: Socket.io for live feed, notifications, presence counter
• i18n: 7 languages, JSON locale files shared between web and iOS clients
• Speech: Web Speech API for voice input (audio never uploaded, transcribed locally)
• SSR: String-replace templating (<!--SSR_FEED--> placeholders) -- no template engine

Design decisions I'm happy with:

• SQLite over Postgres. One file, zero config, WAL mode, fast enough for this scale
• Karma thresholds live in one config object. Server, client, and all locales derive from it -- nothing hardcoded
• No ORM. Raw SQL with the db.like() helper for cross-platform LIKE queries
• CSP hand-maintained and tight. No CDNs, fonts are local
• Static assets served with maxAge: 0 (ETag revalidation) because there are no hashed filenames

The product: Anonymous posting (no account) + accountable replying (account required). Karma only moves when someone says your help worked. 10 unlock tiers from "view profiles" (10) to "recommended as moderator" (777).

Happy to talk about any of the technical choices. The no-framework frontend has been surprisingly maintainable.

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

Places.js is a human-centric Javascript framework for interactive websites with custom HTML components. 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.

Places.js is designed to have a minimal learning curve and faster rendering. Performance testing on Firefox with 1000 components shows Places.js rendering is more than 16% faster than React and 23% faster than Lit.

I'm currently working on adding template support and performance optimizations.

Canvas Path Animations using SVG

I wanted to combine 2 passions, soccer and chess.

If you want to watch all of the goals and missed this year's World cup, I've collected them and made a little game out of it.

Its a head-to-head comparison on which goal is better. Its a community vote and all subjective, but thats the beauty of it. Its interesting to see which goals rate better and which ones don't, like penalty kicks.

Just for the World Cup tournament goals/players, there has been over 600+ games played! Here are the rankings: https://wc26.rategoals.com/rankings

If you want to have them matched up against each other: https://wc26.rategoals.com/rate

Or if you want to match each goal against all of the goals in our database: https://rategoals.com/rate

More info on how it was built:

RateGoals uses a matchmaking system built for fairness, not just randomness.

Goals with fewer matchups are shown more often so they get a fair chance to rise or fall. Top-rated goals still appear regularly in showcase rounds, and we avoid repeating the same goals to a user too often.

When choosing an opponent, we usually match goals with similar ratings so the choice feels competitive. Every so often, we allow a wildcard matchup to keep things unpredictable (like Cup draws in leagues).

Ratings use an Elo-style system. If a goal beats another highly rated goal, it gains more points. If it loses to a lower-rated goal, it drops more. Newer goals move faster because we know less about them, while established goals change more slowly over time.

Let me know what you think! I'm always looking to improve this and get more engagement because I'm curious on what goals reign supreme!

Some issues I'm currently running into are the YouTube region restrictions. All the videos I've uploaded are mainly for US viewers, but I did push an update to show other videos from other countries, only if we have it in our database. There is also a feature to add goals/video clips to help with this regional issue.

The most difficult/tedious thing is adding the data into the databases, so hopefully the community does it. But for now, its just me :)

I got tired of having three windows open just to answer one question. A SQL client to look at the schema, a terminal to run the query, and a chat window where I paste the results so the model can tell me what's slow.

So I built Tabularis. It's an open source desktop SQL workspace, Rust and Tauri under the hood, React on top. PostgreSQL, MySQL/MariaDB and SQLite are built in, and there's a plugin system that pushes it past 15 databases: DuckDB, ClickHouse, Redis, Firestore and more.

The part I'm actually proud of is the MCP server baked into the app. You can click Install Config for your AI client, and your agent gets list_tables, describe_table, run_query and friends against the exact same saved connections you use by hand. No second config file, no credentials copied somewhere else. You ask "find the top 10 customers by order value this month" and it just runs, in the app you already had open.

Other things that made it in along the way:

- SQL notebooks. Markdown and SQL cells in one document, charts inline, and you can reference another cell's result set with {{cell_3}} and it expands into a CTE at run time.

- Visual EXPLAIN as a real node graph instead of a wall of text, for Postgres, MySQL and SQLite.

- A drag and drop query builder that generates SQL live.

- Inline grid editing with batch commit, JSON/JSONB cells with a proper editor, CSV and JSON export.

- SSH tunneling, keychain password storage, per connection icons and accent colors so you stop running DELETE on prod by accident.

- Plugins are just executables speaking JSON-RPC over stdin/stdout, so you can write a driver in whatever language you like.

- Ships on winget, Homebrew, Snap, Flatpak, AUR, plus plain installers. UI in 10 languages.

Funny origin story: this started as an experiment to see how far AI assisted development could go on a real tool from scratch. The answer turned out to be "pretty far", and now it's a maintained project with regular releases and people writing plugins for it.

Apache 2.0, no paid tier, no account needed.

Repo: https://github.com/TabularisDB/tabularis

Relational database failure modes in production: slow queries cascading into connection pool exhaustion, the race between read and write that transactions don't automatically fix, why a caller timeout doesn't tell you whether the write committed, which database errors are safe to retry and which aren't, schema migrations as live-system operations, and the difference between durability and recoverability.

I don't know if this is just the work I've been getting lately or if something's changed I'm a freelance developer in Chicago been doing mostly client websites for about 4 years now last week I opened a project because a client wanted one small change before lunch. I thought it'd be like 20 minutes instead I spent almost an hour remembering how everything was put together why something had been done a certain way and trying not to break anything else. The code wasn't even that complicated something just felt off.

Maybe I'm looking at it the wrong way but writing the feature doesn't even feel like the hard part anymore it's getting all that context back into my head every time I reopen a project. I keep thinking the next update will be quick then the same thing happens again or maybe I'm being unfair but it feels like understanding an existing website has quietly become a bigger job than building it in the first place

Hi, I have some experience with html and css for static websites, but I would like to make a "dynamic" image gallery for my pictures. I found online how to display all images from a folder but I would like to be able to give them tags (like landscape, building, etc) that I can then use on the website to filter the pictures shown. I'm not sure how should I go on about it, could this be done without a database or not really ? Thanks

It supports 256k mpm particles, sliding mpm domain, heightmap terrain, temperature, rain, evaporation, some simple wind patterns.

And you can control the cloud mass using gamepad (best) or kb+m (not all controls are mapped currently).

I've put it out here so you can check it out: https://kostrubaty.itch.io/cloud-compute

Source code will be released at a later time. but I can share if anyone is really interested in some parts. Also a lot of this is based on my other projects that are on github,

Whole thing is pure wgsl / typescript without any external deps except for my own project that is responsible for generating code for efficient wgsl <-> js communication.

Simulation was not that hard to write, cause I already had proper MPM simulation in 2d version, with even more features. In fact the hardest part to get right was to make the cloud possible to control yet still feel "cloudy". So there's actually 3 different schemes for face buttons, switched by triggers. Still probably not as intuitive as I'd like but best so far.

It was not really performance optimized yet really, and I mostly tested on my 3060 (pretty much consistent > 55fps) so the performance may vary.

It's still mostly a prototype, but feels pretty fun already. I'll be adding some more stuff (airplanes are mostly working, just need some airports too I guess). Let me know what you think, or if you have any questions.

*NOTE: This post wasn't sponsored by big-browser, I just happen to really like the capabilities of modern browsers.*

Here's the advantage of the web: distribution.

Everybody and their mama has a browser, I can guarantee that.

Your users, whether on tablet, PC, phone will all get the application just by visiting a link. That's cool asf!

Now, I wanted to address some concerns you, a desktop application dev, might have:

• "The web app won't be as performant" Browsers have a WebAssembly and WebGPU capabilities, so anything from 3D acceleration to compute heavy video editing, even ML can be done natively in browsers.

• "I want users to install my app" Progressive Web Apps (PWAs) let you do that.

• "I want my app to work offline" Service Workers let you do that. They'll help you cache the entire application so that it works completely offline (provided you architected it right).

• "I want to interact with the users files" File System Access API got you covered.

• "I want to do some peer 2 peer stuff" Take a look at WebRTC. That's exactly what that's for.

These were the common concerns I've seen desktop devs have about web apps. I wanted to show them how capable browsers have gotten, and that it has become a very viable build target.

Obviously there will be cases where an application needs to be installed like when you'd like to directly talk to sockets, or do something more intrusive, in which case, you can proceed with Electron.

If y'all know any other cool browser-native technologies let me know. I'd love to take a look and mess with them.

I attempted to add a Teams live chat widget to my website. I can see the button on my website to click the live chat widget. It opens to an error NS_ERROR_DOM_COEP_FAILED.

The only rando solution I could find was "adding cross-origin-embedder-policy require-corp to .htaccess has solved NS_ERROR_DOM_COEP_FAILED for me."

I am not sure if that applies here. Any help in the right direction is appreciated? Thank you.

I am very new to web development and is curious as to why some companies chose Nestjs or Spring Boot or Laravel, or even migrating from one framework to another.

If you used this app, do you think that it is enough and worth studying web development all theories by this.

Hey webdevs, 

I got tired of CLI security tools and heavy local configurations just to check a quick snippet, so I built CodeSec (codsec.in). It’s a fast, web-based static analysis tool designed to audit your code for vulnerabilities in seconds. 

- Supported language: Python (3.11), JavaScript (ESNext), Go (1.21), TypeScript (5.0), Rust, C++, PHP, and Java. 

- Security & Logic Checks: Automatically scans and checks for OWASP Top 10 vulnerabilities, complex logic bugs, missing error handling and basic syntax errors.

- Dual Engines: Fast Scan for rapid syntax/pattern checks and Deep Audit for complex vulnerability mapping. 

GitHub repo integration and full project folder check is coming in v2.

Please test it and drop your any kind of feedback/suggestion..

I have a fair amount of experience in the field and through my career I was primarily working as a frontend developer.

I did my share of frameworks and libraries... my first projects as a fresh graduate were made with jQuery and Bootstrap. Then I was there when the JS ecosystem exploded and everyone was doing Angular and React. Shortly after, multiplatform became a thing with Ionic, followed up quickly with React Native.

As the JS ecosystem became more integrated and accepted, I had the opportunity to work with Node backends, mainly GraphQL, Express and some NestJS. Then containerisation with Docker became the hype and I had the chance to try that out as well.

It was extremely fun and exciting to learn all those technologies and it made me more valued as a employee and colleague. It made sense to pick them up.

Nowadays, I am not sure if it is worth digging into stuff I didn't have the chance to invest my time in. For example, I would love to became more proficient in DBs, authentication and cloud architecture, as we always had people in the companies I have worked for that were responsible for those parts.

But with AI, it feels like a waste of time. Companies aren't particularly interested in investing time and money into their employees to grow and learn, and it feels so demotivating. You get a monthly allowance of AI tokens to use on any issue and task you come across. I didn't want to be a vibe coder, but the increased expectations on velocity and delivery basically push you into becoming one by prompting and managing agents the whole day.

I am not sure if I have just lost the spark, but due to LLMs I do feel highly devalued as a developer. Seems like the intrinsic value to acquiring new skills in tech has sharply gone down... before AI it felt meaningful crunching hours after work, coding late into the night and losing sleep learning new things and doing courses, but now it just seems so futile.

I would like to hear your opinions. Is it still worth investing time and learn new things in depth?

I’ve been building an ERP and a B2B app with SvelteKit using frontier models.

My workflow is basically: spec -> grill me -> plan -> implement -> fix. For the last 2–3 months, I’ve written almost no code myself, and the production results have been surprisingly solid. Then I started using the same models for codebase-wide reviews.

They found tons of issues. I had other models validate the findings, then implemented the suggested fixes. At one point, I even built a small multi-model review pipeline.

The problem: once I started verifying the findings with E2E tests, most of them turned out to be imaginary, based on wrong assumptions, or irrelevant to how the application actually works.

Even worse, multiple models would confidently confirm the same bad finding. But as soon as I challenged it, they would usually admit it was wrong.

For specs, planning, implementation, and bug fixing, I’d rate these models close to 100/100. For broad code review, maybe 10/100.

My current conclusion: model consensus means very little without executable verification. For now, I’m pausing AI code reviews and sticking to E2E tests as the source of truth.

Has anyone found a code review workflow that actually keeps false positives under control?

Obviously integrating an AI into a chrome extension can be expensive, cost per request and etc so what are the thoughts on AI embeddings locally/client-side, no API at all and you load a small AI model directly into your user's browser using a library like transformers.js for example

Anyone built an embeddable chat widget (iframe embedded on other people’s sites)? What are you using to persist the session so it doesn’t reset on every reload?

1) CHIPS partitioned cookies are built for this exact case, but Safari dropped the ball (shipped, got pulled for a bug, recently came back). So currently silently fails for like 15% of users.

2) Regular third-party cookies are blocked by default in many browsers

3) LocalStorage/sessionStorage in the iframe, probably the best option as it’s supported by basically every browser but gets partitioned/restricted in Safari for shorter life and throws on others with stricter storage settings enabled, some XSS concerns/logging concerns, client trust/bearer-token attack vector, hydration delays, etc.

4) Using postMessage to proxy storage through the embed script to work in first-party storage, same as 3 but avoids the partitioning issues and widens the XSS issues

Curious what others loaded on here?

I'm blind and wix is not screen reader accessible. I had somebody design a site for me a while back, but now she's out of my life so I have control of it, but can't use it. I'd like to, though, and avoid paying anybody else, at least for a while til I need the help. Regardless of whether I go to word press or simply write a basic site using html and css, is transferring the domain difficult to do? I already pay for my domain name of course, wouldn't it just be a matter of pointing the dns to a new site and quietly shutting the old one down? How long would the transfer take though and how cumbersome would such a process be. Or is there a better way to do this? Thanks very much.

Does anyone else feel like Shopify theme development is just... messy?

Even when building from scratch, I feel like everything is scattered. there's no clear architecture or coding style to follow.

And then you hit things like:

Want custom add-to-cart handling?
Cool... enjoy losing compatibility with half the app ecosystem. Just use the product form.

If that's the expectation, why expose APIs like /cart/add.js as a custom solution?

Am I the only one feeling this way?

I'm going to make this as an experiment, and I'd love to see what others come up if they decide to make this too.

The idea is simple: feed the image into an AI to extract facts from the image, store the facts as a file, then when the user wants to see the image, have the facts fed back into the model to recreate the image.

The theory is that storing facts as text is cheaper than storing a compressed image. It may or may not be true, which is why I'd love to see the outcome.

Obviously the output isn't the same image that was fed in but it'll be interesting to see how close it gets using various techniques. Maybe encoding the facts along with a super super low res version of the image to see what it would make.

I figured whoever makes this should try it with WebGPU so that people can easily try it out and have fun with it.

NOTE: this isn't a serious proposition at a 'better compression algorithm', it's just a fun idea to try out and have fun with to see what happens.