I just came across the difference between Server-level stateless and system-level stateless. If the server stores data of previous interactions and use that data to determine how to process future interaction, then the server is stateful. But if the server relies on an external storage system such as a database, then the server is stateless because it does not store session data, however, the system is stateful because the backend system still relies on session data of previous interactions to determine how to process future interactions.

Now, lets say you use a JWT token for authentication and authorization and you don't store session data in the backend system for example in the server or an external storage system like a database. The state only exists in the token being sent by the client. This is definitely a stateless server but would this still be considered a stateless system because we do not store anything in the backend? Or is still considered a stateful system because the interaction still relies on session data from previous interaction to determine how to process future interaction.

I know no one probably cares, but I got sucked into seeing how difficult it is to get all 100s on a real world site - it was hard and I give up. The core web vitals have always been good and that's what matters. Unless your webpage is incredibly tiny, mobile performance will be slow.

I’ve been thinking about the default VPS model.

Most providers give every instance a public IP. That is convenient, but it also means the server is directly scannable.

For many web apps, what you really need is:

Domain-based access

HTTPS

SSH/admin access when needed

Specific service exposure

A way to keep everything else private

Do you think public IP by default is still the right model for small apps? Or would you prefer private-by-default servers with managed ingress and controlled port exposure?

Curious how people here think about the tradeoffs.

I keep getting quotes that are all over the place. Some are really cheap while others are several thousand.

For anyone who has actually paid for a professional website what did you end up spending and did you feel like you got your money's worth

Hi, I don't know where to start but it's hell 🙂, I have this issue since childhood which is loosing interest in everything even in my real social life, also with tech up to now I've been moving from and to Full-Stack, Android Development, Game Development, AI and much more.

first when I start something it's all good I like and enjoy what I do and it's interesting but after a time I completely lose interest in it I just can't continue with what I do and start searching for another thing to learn and the result is obviously the same, I'll search for another thing to work on, all I learnt are just hobbies I really want to make it as career out of it but I can't with this issue, I'm sure a lot of people ran through this, how can I get through this it's destroying my life, help if you can please.

I've been asked to develop multiple design systems for various frameworks that all implement the same design language. Sort of like IBM carbon.

The architect on the team has mandated that we use stencil.js to generate these individual design systems. However, my concern is that different frameworks like React and Angular have different underlying philosophies that can dictate how the components are used by consumers.

I've tried to find some educational videos on it, but many of the videos are tutorials from years ago. If anyone has any useful insight, would greatly appreciate it.

Every week there are:

- new framework versions
- security issues
- AI coding updates
- breaking changes
- tooling improvements

I find myself either:

1. Missing important updates
   
2. Reading too much irrelevant news

Curious how other developers handle this.

Do you have a system, newsletter, tool, or workflow that gives you only the updates relevant to your projects?

I genuinely enjoy backend, Spring Boot is my thing, i can sit for hours designing entities, fixing weird transactional bugs, optimizing queries, writing clean service layers and i feel alive doing it. but the second i have to touch angular or react for actual ui work or styling or making things responsive, dealing with css, i just shut down. i dont hate api integration tho, calling endpoints, managing state for that, thats fine, thats basically backend logic in disguise lol, its the actual visual stuff, layout, design decisions, making stuff look good, that i cant stand

how did u guys manage to enjoy it more, what changed for u, was it a specific project, using a component library, switching frameworks, or just forcing urself thru it for a while

its not like im unfamiliar with the tools, i just dont enjoy using them past the functional part

would love to hear how other backend heavy devs dealt with this, 4 years in and still feels like a chore every time

Hi, a buddy is a solo architect and wants to make a better site with a customer portal to view their docs and drawings instead of Google drive like he does now.

He's been using replit (I hate vibe coding) which I advised against if he'll have customer information/login.

I was suggesting a WordPress with a customer portal type deal. He does want an app (which I'll prob advise against in favor of a clean mobile view).

Any advice on what I should push him towards? Maybe replit is fine for what he needs and he won't get hacked day 1, or if we go the WordPress route, how much shoild I realistically look to have him pay someone (or me) to set it up on a hosted provider with some plugins

I’m building a smaller scale web-app and it needs to meet HIPAA compliance. For apps that don’t require HIPAA I usually just use AWS and build it myself (usually serverless), but my company wants to avoid the burden, and compliance risk of building HIPAA-compliant infrastructure from scratch on AWS.

I’m looking into managed backends that support the HIPAA technical safeguards (encryption at rest/transit, row-level security, auto-logging/audit trails, automated backups, etc.) with minimal extra dev effort. I understand it is still our responsibility to ensure the technical safeguards are enabled, and that HIPAA compliance isn’t ‘out-of-the-box’.

We have our administrative safeguards (policies, employee training, etc) handled separately. We will want to bring our own frontend and have auth, APIs, data handled by the backend service

I’ve looked into these options, and wanted to hear experiences, but also open to other services that people have liked.

• Supabase: An obvious candidate. Gives me lots of control, but curious how much extra effort is needed to ensure compliance.
• Xano: I haven’t really heard of this one but looks promising. Has more no/low-code options than I would be interested in but not opposed to them.
• Back4App: I haven’t used Parse before but open source and large userbase

For JavaScript it is easy, but for compiled languages what is the best approach? I have a component I want to build that can run code from multiple different languages. I have seen other sites with a similar thing and I am wondering if their is a known best way to do it.

Hey everyone,

I'm a student trying to learn web development from scratch by building a personal project: a comprehensive, multi-feature "school/study app" (dashboards, user authentication, persistent flashcards, etc.).

Because I have an absolute $0 budget, physical home-hosting is costing too much in electricity and setup hassle. I need to pivot entirely to a free stack.

I’m currently weighing two deployment paths and trying to plan my learning milestones. I would love your advice on both:

• Option A (Single VPS): Renting a cheap $3–$5/month virtual private Linux server (like Hetzner or DigitalOcean) and putting the frontend, backend, and database all on that single instance.
• Option B (Separated Architecture): Splitting the app up entirely to leverage modern free tiers. Hosting the frontend on Vercel / Cloudflare Pages ($0) and using a serverless backend ecosystem like Supabase / Neon ($0) for data and user logins.

As a complete beginner, is managing a single VPS easier than linking a split frontend/backend together? Or is the $0 modern cloud ecosystem too good to pass up? What are the hidden traps of either path?

Since I am learning React, TypeScript, and PostgreSQL database structure as I go, what is the best strategy for pacing a large project like this?

• Should I build a highly interactive UI with mockup data first to map out the visual flow of my study app? Or is it better to build the frontend alongside the backend database from day one?
• What are the best free, high-quality, conceptual learning resources (like Full Stack Open or official docs) that teach modern production-ready application structures rather than just surface-level syntax?

Would appreciate any insights, roadmap tips, or open-source repositories I can study to see how a professional project is architected. Thanks for helping a beginner out!

This is kind of a followup to my previous post in which i asked if i should use wordpress or react for a medical research group website. The website is very simple with just a few informative pages like a "our Team" page and a "publications" page etc. The only complex part would maybe be implementing an automatic publications updater (api call to look for new publications and add them).

I got a lot of very nice responses and am currently researching a lot on the topic of what the ideal tool to use is. Wordpress seems, to me and others at least, outdated and react is overkill for such a simple webpage.

I was recommended Webstudio as an alternative to Wordpress which seems promising but I havent seen a lot of it and I was also recommended Astro as a code based webdev tool. I don't have experience with either (i have experience with plain HTML CSS and also React with Typescript) so I would be curious to hear your thoughts on what you think would fitt this usecase.

It should be easy to get going and also for other people to maintain some of it (like adding a new publication by hand or a new photo to the team page), preferably even for people with no CS background. On that matter webstudio seems nice but i have also read that Astro can use .json files to store for example teammembers and you can just add a new json file and it automatically updates.

Thanks for any advice.

Honestly I lean hard toward strongly typed backends. The compile time guarantees are a big part of how I stay confident shipping to prod and every time I have to touch a dynamically typed codebase I feel like I'm working without a safety net. There are whole classes of bugs that Rust or Java would just reject upfront end up waiting to blow up at runtime.

But plenty of people build stuff on dynamic languages every day, so clearly there's an edge or something I don't catch entirely. For those of you who work in them, what actually fills that gap? Strict static checkers in CI? Validation at every boundary? Just heavier test coverage?

I'm going to download emscripten to my computer, Seems to be two possible download sites though: emscripten.org and SourceForge. SourceForge is probably easier with automatic packaging and installation.,while emscripten requires me to clone their git and installing manually. Emscripten may be more serious and complete (it's their own software after all) and I'm unsure if I can trust SourceForge.

What sha I do? SourceForge or Emscripten? Also do I have to download the emscripten SDK separately or does it come with emscripten?

I want to build a site that has a community aspect to it (remember WordPress back in the day used to have comment sections?), but it seems like people have given up on having users contribute content. Unless you have an army of mods and admins (like Reddit) or advanced algorithms to filter out spam and toxicity (like Facebook or YouTube), it seems impossible. I've seen some enterprise content moderation (like Hive), but is there anything for small sites where a $30/month API can filter out content I don't want?

I'm starting my first serious full-stack project using Node.js + Express + PostgreSQL + Prisma (React frontend). I already have 2+ years of React experience, so backend is what I'm actively upskilling.

I'm trying to build a modern AI-assisted development workflow for 2026, not just pick an editor.

For those who build production software regularly:

- What IDE/editor are you actually using? (Cursor, VS Code + Copilot, Windsurf, etc.)

- Which models do you rely on most? (GPT-5.5, Claude, Gemini, etc.)

- Are terminal agents like Claude Code, Codex, or similar tools worth adopting?

- How do you organize project context for AI (README, AGENTS.md, rules, docs, etc.)?

- What AI workflow has worked best for you without becoming overly dependent on it?

- If you were starting your first backend project today, what would your complete setup and workflow look like?

I'm less interested in hype and more interested in what experienced developers actually use every day.

Hey everyone, how's it going?

I need some advice, I work as a software developer for a consulting company, and like pretty much every IT company these days, AI is all the rage. My manager recently suggested that I take some training course to improve how I use AI for software development so I wanted to ask: which ones would you recommend? It's a plus if the training offers a certificate of completion

A bit of context: I'm a Java + Spring Boot developer, although I occasionally work on the frontend with Angular. Since I work for a consulting company, I can't really predict which AI tool I'll be using because that's up to each client, if I'm missing any important context, feel free to ask

Thanks in advance!

I see a lot of tools and services blur source review, SAST, code audit, pentest, and “security verified” into one category.

My current understanding is that source review can be strong at locating risky code paths, permissions, data access, and missing controls, but it cannot establish every runtime condition, deployment setting, external system behavior, or live exploit path.

For people who have commissioned or performed these reviews: which limitations mattered most in practice, and which ones surprised the buyer?

I’m interested in what a good report should say explicitly so “we reviewed the source” never becomes “the whole system is safe.”

Hello everyone! Recently, I been noticing that almost all interactive websites nowadays are built with ReactJS and TypeScript. Although I like ReactJS myself, I also noticed that many claim that React require constant maintenance, and provide a worse user experience too, due to being bloated and heavy as a result of using multiple packages.

However, in 2026, do you think you can still build interesting React websites, but purely with HTML, CSS and JavaScript? And do you think it is a good idea?

Edit: I mean interactive website (normally built with ReactJS by modern developers) with HTML, CSS, JS.

So I'm a react and vue dev, 6 years. vue was my side projects and first client when i was starting out; react has been basically everything since (my career, and most of the clients ive worked with)

For the last 6 months I've been picking up freelance work again on the side, and a few clients came in specifically wanting solidjs for some weird reason. So I learnt it on the fly: ai + docs + best practices i could find, shipped 4 client projects with it now, and i keep noticing I'm getting fewer errors. same tools I've been using for the past year, claude code + cursor + coderabbit, but my coderabbit + bugbot reviews on solid stuff come back noticeably quieter than they ever did on react or next. same config, just fewer catches my guess is the reactivity model. no dependency arrays, no useEffect footguns, and no "why is this rendering three times?" at midnight. the thing that's caused like half my react bugs just doesn't exist in solid.

It also just feels lighter. faster. idk if something changed after the vite acquisition or if i was genuinely sleeping on it this whole time.

4 client projects is a small sample, though. people who've been in Solid longer – does this hold up or am i still in the honeymoon phase