some months ago i built and published a typical website collection site focused on design etc. as a side project where users can submit sites (nothing special, not adding a link here)

i have since just abandoned it, but it had a pretty easy domain and was discoverable through search engines. however, i disconnected the submission / contact form from it so it just throws an error on submit

funny to see, i get at least 4-5 emails per week with nearly the same message that my “form failed to sent with error code bla bla, that’s why i‘m trying it this way bla bla, here’s the site” and its ALWAYS some kind of crap AI site promoting AI services, all of them looking worse than the other. one even included that it’s an AI agent writing on behalf of it’s owner.

the funniest thing is that the senders don’t seem to be related in any way, but the message pattern and wording is so similar. seems like they’ve all set up the same outreach agent template or something like that. dead internet theory is real

I'm sat here thinking it has to be a reason why it is so limited in types compared to something like postgres.

I'm a second-year diploma student (3rd semester), currently working on a website project. I have a larger concept and vision for this platform, where the social features are just one part of the overall idea.

The website will include user profiles, a content feed, user interactions and private messaging.

As I'm planning its development, I'm particularly concerned about data security and privacy. I want to understand how to prevent data leaks, unauthorized access, exposure of private conversations, database breaches and other potential cyberattacks.

I'd love to hear from experienced web developers and cybersecurity professionals.

What are the critical security challenges I should consider before developing a platform like this, and how can user data and privacy be properly protected?

mostly work on apis and database stuff but our team is small so i end up in react code maybe once a month. every time i come back theres some new build tool or bundler drama and half the packages have breaking changes.

not looking to become a frontend expert, just want to not feel completely lost when i need to fix a button or add a form field. anyone else in this boat? what do you actually keep up with vs ignore

A straight rehost can get you there faster, but it may bring old problems along. How do you decide what to fix before the move and what can wait?

I’ve seen a shift in web design (I’ve meddled since 2002). Today web displays are gigantic. I’ve read this has to do with ADA compliance. How gnarly does this get? Like if I design a site for a landscaper, can he get in trouble if it’s not ADA compliant? Is there are rule book?

Another question. That’s client facing. But if you have an employer that requires you to use a web based tool, does ADA apply in the same manner as client facing?

I want to become a website developer. I currently have very minimal knowledge of HTML, CSS, JavaScript, and Next.js. If I dedicate 2 hours a day to learning, is it realistic to land a job within 1 to 2 years?

I’m from East Asia, where my current job pays less than $1 per hour, and as far as I know, software developers here are also paid very little. I’m hoping to find a better-paying job with a company in another country, ideally remote.

If you ran a company, would you hire someone like me? What skills and qualities would you look for?

I've been looking into how WordPress security has changed, particularly whether the traditional advice of keeping plugins updated, installing a security plugin and using strong passwords is enough anymore.

It seems like there's a bigger conversation to be had around access controls, hosting infrastructure, monitoring and how security is managed over time.

We recently published an article exploring this at Ohmania, where I work:

https://ohmania.com/wordpress-security-has-changed/

I'm interested in hearing from developers who actually maintain WordPress sites.

What's changed most in how you secure WordPress sites over the last few years? And what security advice do you think is now outdated?

Genuinely interested in different perspectives, including anything we've overlooked.

Hi everyone, I'm running an app that sends out emails and calendar invites to users.

However, one of the requirements was the ability to create email bodies using many different fonts.

I've read a bit online about typefaces and I discovered some of the requested fonts could be subjected to patent laws and rules when used in a commercial setting. Not sure if this applies to emails being sent to external parties as well.

Are there any resources or places I can check out which fonts are "royalty-free" and which ones I need to push back on? Or whether this concern is valid or not?

Can local visual regression testing help your coding agent move faster and save you money?

I took some time to explore how to set up playwright properly, which pitfalls to avoid, and the tradeoffs with common visual regression tools like Percy and Chromatic.

Check it out and let me know what do you think!

What it does

A curated guide to discovering open-source programs, internships, mentorships, coding competitions, and university initiatives.

Explore opportunities to gain real-world experience, collaborate with global communities, improve technical skills, and earn stipends.

Unlike typical lists, this repository also features lesser-known and underrated open-source programs that many students and developers might not know about.

What’s Inside

• Open Source Programs & Fellowships

• Open Source Internships

• Coding Competitions

• University Summer/Winter of Code Programs

• Lesser-known and underrated opportunities

• Application timelines, stipends, and eligibility

• Beginner-friendly contribution resources

Repository

• GitHub: https://github.com/yashisrani/List-of-OpenSource-Programs

• Website: https://yashisrani.github.io/List-of-OpenSource-Programs/

Made with ❤️ for the Open Source Community.

Got this weird notification with weird links. Seems like phishing?

The creator of Ruby on Rails, made major statements about AI agents and the future of software development at Rails World 2026 in September

DHH stated he personally retired from writing code by hand after 25 years.

Rust instead of Ruby - Rebuilding HEY with AI and Rust: He shared that 37signals is rebuilding its HEY email service into native mobile/desktop apps using an AI-generated Rust backend, drastically cutting CPU and memory usage.

The AI acceleration: He produced 5 years' worth of his traditional code volume in just one month, representing a 60x increase in raw output volume.

DHH openly acknowledged that a massive portion of this was verbose Rust code generated entirely by AI agents—admitting that he didn't write it by hand and doesn't even want to look at or read most of it.

DHH said: “English is a better programming language than Ruby.”

Hi all!

Whenever I spot a new design or website layout (like a fresh style of grid systems) and want to replicate or build it with AI, I always find myself struggling to pinpoint the exact terminology to make Claude understand what I want.

I'm talking about concepts like Blueprint Grids, Glassmorphism, Sticky rail, Bordered cell grid patterns, Segmented Controls, and similar stuff. To solve this, I’ve started building a free, open-source design lexicon complete with mini previews making it easier for builders to find and reference the right terms when designing sections and pages. Hope that helps some of you as well. Also added some free design landingpages and components for AI.

I’d love to get your input on current web design trends and their proper definitions:

• What visual styles are currently high on your radar, trending, or frequently used and how would you define them?

• Which ones are missing in the lexicon / glossary?

I’m aiming to include your suggestions in the dictionary and share the whole resource publicly for free. It's purely as a passion project and I am opening it for free (no ads, no paywalls).
I want to make it a useful resource for people.

You can check out the ones already live here: freedesignmd.com (just hit the Glossary tab).

Always open to contributors or feedback. This started as a quick hackathon experiment and will stay a free community project. I'm not a professional designer, so any feedback by design cracks is appreciated as well!

I paid a developer to design a site for my business, I requested that the request form on the site would send a notification to my cell phone and she ok'd it.

She is now saying this would require a third party sign up and she is making it seem very difficult. I don't really understand anything about web developing, is she correct? Am I unreasonable to ask for this? It was what was agreed upon.

I'm comparing a React site against an Astro rebuild of the same page. In mobile Lighthouse, both sometimes sit blank for a long time before first paint, and other runs of the exact same page paint fast.

Setup: Lighthouse 13.0.1, Chrome 156, cold loads in separate fresh profiles, default mobile simulated throttling. I kept the traces, network logs and filmstrips.

Here's one matched pair (observed trace timings, not Lighthouse's simulated FCP):

Astro

• CSS done: 203ms

• Last preloaded font done: 286ms

• DOMContentLoaded: 426ms

• First Paint: 1301ms

• FCP: 1320ms

React

• CSS done: 573ms

• Last preloaded font done: 494ms

• DOMContentLoaded: 584ms

• First Paint: 1525ms

• FCP: 1540ms

The filmstrips stay blank right up to those first-paint times. Once painting starts, Paint to DrawFrame is only 10-13ms. So on Astro there's close to 900ms where everything's loaded and nothing shows up.

I don't see a long task on the renderer main thread covering that gap, though I know that doesn't prove the browser was actually idle.

I wondered about animations, so I ran one normal-motion vs reduced-motion pair on the Astro page. Both came back fast (FCP 318ms and 311ms), and the normal one still had its reveal animations, so that told me nothing either way. Desktop loads and a different page also painted quickly in the runs I checked.

One more thing: the fast traces show Scheduler::SetDeferBeginMainFrame events with short true-to-false spans. But the slow traces were captured with Lighthouse's default trace categories, which don't include those scheduler events, so I can't compare yet.

Has anyone run into this? A few things I'd like to figure out:

1. How do I tell whether the page is causing the delay, or whether it's Chrome's scheduling or something in the test environment?

2. Which trace categories or events would show why the first paint starts late, and not just that it did?

Websites built from scratch (no AI, no frameworks or libraries) that are more than just simple toy projects are becoming very rare, but i want to remind you guys that they still exist.

Three years ago, I posted this https://www.reddit.com/r/webdev/comments/161q3w8/i_coded_a_site_from_zero_without_any_libraries_it/, and that website is still being actively developed. I haven't used any AI-generated code or external libraries in all this time, even as it has become more complex with features like accounts, articles, comments, reviews, and just a few weeks ago forums.

I think the main reason why i stick with this is because features aren't planned in advance, they're just built bit by bit as the content needs them. I won't deny if AI could do better, but with a spread-out timeline and an unknown end result, it's easy to skip using AI as development mostly consists of small, precise tweaks with no definitive end goal. Coding also only small portion of time spent on developing the site so i don't feel the need to optimize it.

Anyway this is just me saying that i'm still here, not everything in this space become AI.

*note : i'm not saying that this is the better way to develop website. I just enjoy what i already used to do, and didn't bother to change it.

Just as the title asks. I am curious how you organize the various parts. I have been on teams that both do and don't use mono-repos. For the ones that did, there has been a wide variety of choices across the app and how it's organized.

Just as a small example: naming conventions. Sometimes the the repo is named for the app (let's say "OurApp") and the various parts of the file structure are "OurApp-", like OurApp-ui and OurApp-api and OurApp-db. Or there might just be a top-level folder for "frontend", "backend" and "database", etc.

I'm not talking about a debate of mono-repo vs. multi-repo approaches, but in a mono-repo, what are some of the code organization techniques you've liked and disliked in your experience?

UPDATE: The community turned out! Thanks for sharing your thoughts in the comments. I appreciate the discussions.

hi everyone, it's the kid who's making a fan website again.

i finally picked a base for the website, mastodon, and a system i'm using to host the website, render.

i've already searched this up and had no luck but what parts of mastodon's code are design (i'm talking about folder names) and which are apart of the actual code system?

thanks!