Found it while doomscrolling like a bish.

I know the most fun times for me in coding were when I was deep in some rabbit hole exploring weird technologies and trying to piece them together.

You'd think AI makes this worse, but actually no. It just makes it even easier to go down these rabbit holes, because it's easier to write code, try out different approaches, explore new things, etc.

But somehow most of the people I see aren't doing that. How are you not bored out of your mind?

Anyway, yeah. GO EXPERIMENT WITH MORE THINGS. SIDE PROJECTS ARE STILL COOL.

I've been using Divi for many years now but I feel it's time for a change, it's a bit clunky for e-commerce sites and shops that have lots of traffic and users. I don't want to be locked into an eco system like Divi or elementor. After a quick Google and chat with ai it looks like kadence or astra have everything I'm looking for.

My main goals is not to be locked in to anything apart from wordpress. I want portability, speed and not too steep a learning curve whilst learning a new theme and plugin.

Hello web developers, I was wondering why my website may have gotten banned by my employer? I just tried to search it up right now (I'm on the clock) and it blocked me from visiting the site.

Fox content, this is the website: hidden sitename (got enough feedback thx)
Edit: ppl saying "Fox content" it was a typo "For context" 😭

It's a social media type website where people can sell digital products basically... Not trying to promote. The focus is why was it blocked?

I'm concerned because if the website is being flagged as malicious, that could hurt my growth...

I've been applying to Remote Junior Frontend Dev positions on LinkedIn for about 3 months now. Any senior devs or recruiters here that could give me some suggestions on my resume? Also are there better ways to find frontend dev roles than LinkedIn? I live in the US if that helps.

As per the title, the image above shows my cloudfare 24 hour traffic, it's a pretty much all junk as the website is still in development with no real users.

They like to hammer a few specific pages, with one page getting 10k hits daily. I've setup cloudflare rules to prevent bots, blocking most crawling user agents, blocking a bunch of url patterns, on top of the usual robots.txt but it's still fairly bad.

I'm not persistently logging then blocking specific ips yet (partially because I dont know how). Is there anything else that I could be doing?

My page website is fairly page heavy, exposing around 1000 pages in the sitemap but still I didnt expect so much malicious traffic so quickly

I started learning web development at the start of this year and one thing led to another and I’m now trying to build near enough an entire business’ online system.

I’m building an AI and automation enhanced business simulation.

There’s two main purposes: teach myself full stack development, and experiment with where AI and automation fits in modern business systems. I’m trying to treat it like a real business so I can see how and where things can be different to a system that doesn’t use AI or workflow automation.

It started off as an attempt to build the frontend a customer would use so I could practice with state. Then I decided it would be cool to have the opposing merchant interface where you can view the orders. So I needed to make the backend.

But, given the times we’re in, I thought it would be interesting to see I can use AI and automation in ways that would save a user time, or just deliver helpful results.

Now, my long term plan is to create an entire product pipeline, with product suggestions from a ‘supplier’, marketing content created, product going to warehouse, then product available for order. But that’s a ways off.

For now I’m focused on developing the customer and merchant ends with these primary features:

·       Shared backend

·       Customer service chatbot on customer side

·       AI assistant on merchant side

·       AI overwatch feature to monitor AI behaviour

Eventually I’d like to experiment with adding analytics and CEO suggestions features from the AI but again that’s a ways off.

I’ve set up self-hosted n8n which I’ll use for workflows where necessary, and I think once the meat of the project is done I’ll get a bit creative with that.

I’m building it in slices; rather than trying to make the whole backend at once, I’m building it by function. Currently, I’m on the first slice, the cart. This is my first time attempting to write backend code.

What I’m enjoying is the logical, layered approach; I have router, application, service and data layers, each with their own jobs. And because the backend is entirely abstract so I cant rely on looking at where my elements are going on screen (like with frontend) I’m learning to properly understand how data is passed with javascript.

I realised early on that if I’m to have an AI logging system I’ll have to think data first, and I think this has helped me massively as now it’s simply (simply) a case of getting from the front to the back and adding/changing data whose properties I’ve already determined.

I’m going to post more detailed stuff so I can learn from people on here and engage in general in the topic more.

If anyone has any questions or suggestions, please comment!

3-year-old codebase, 2 senior devs who are careful about best practices, security, testing. They're also equal partners in the company, so any efficiency gain lands directly in their pockets.

I'm a PM. I asked this same question ~9 months ago and the consensus was: reading/reviewing AI-generated code is harder than writing it, so my PRs would just be a tax on the senior devs. Not worth it.

Models and tooling have moved a lot since then. Honest gut check:

A. Is it reasonable now for a PM to open PRs with code written via Opus 4.8 (or better), on the condition that every contribution goes through heavy QA and testing before merge?

B. Any world where a PM pushes without a PR? Or is that still insane?

Where's the line in July 2026?

Edit:

People are asking why this is even a need. Two reasons: (a) the devs are slammed with other projects, and (b) the info gap between me and them creates a lot of back-and-forth, ping-pong, slow turnaround. On roles: we're all equal partners, so better process and faster results benefit everyone regardless of our traditional titles. And it goes both ways - the devs are free to push AI- or human-driven PM-side upgrades too, and they sometimes do.

Hi guys!

I’m making a web app for school (mobile First) but the white space at the top is ruinijg the aesthetic. I have an ombre background só I tried to make the body color beige but it still looks off is there anyway around this? I tried the whole meta head thing but still nothing

I’m building a small tools/content site and trying to keep the public pages SEO-friendly from the start.

The actual tools can be interactive, but I’m wondering about the surrounding pages: homepage, tool landing pages, category pages, docs/help pages, etc.

My instinct is to make those pages mostly static or server-rendered, with normal HTML content available without waiting for JS. Then only use client-side rendering for the actual interactive parts.

For people who build small sites that need organic traffic, is this still the safest approach?

Or is modern Google rendering good enough that CSR is usually fine as long as the site is fast and internally linked well?

we had a bug where our own bot would go quiet right after sending a message, like it accidentally armed its own away mode on itself.

our dedup for "is this our own message echoing back in" was a single-use token, push on send, pop on receive, keyed by a content hash. worked fine until the third-party platform retried the outbound webhook delivery, which happens more than you'd think. the retry landed as a second event, the token was already gone, so it fell through the normal ingest path and got treated as a brand new inbound message. outbound detection never got a chance to catch it.

the real lesson is about dedup design generally: any scheme with exactly one token per event is one retry away from failing, because the upstream is allowed to deliver twice and your dedup can only survive that once.

do you assume every webhook can be delivered more than once by default, or does that assumption only show up after it bites you?

A few years ago, I developed a browser extension to block LinkedIn's little News feature (I felt it was too much of a distraction).

One day, however, it stopped working, and I realized that it was because LinkedIn had replaced the class I was looking for with a bunch of mangled class names. I ended up using, but it keeps coming back, and a recent "peek" seems to indicate that it's happening because the class names are getting changed seemingly daily - despite no visual changes.

For example, these were the classes yesterday:

.a04ea70e._4ae6872e.ea6ce3e7._854ea209.f543c3ba.dffb4272._0ec569ed._6030e161._62303b7e._6b4eb75a._694c34e7.de4044e3._20e3c592.a2906c41

and then today it was this:

._5c537f20._72fd5906._31504bd6.a62467c2.e800bc3f._7985fa5f.b3f42bc8._9bd701cc._1c257c76.d3944a37._7b065b4c._2c68b8b7._2c8dcc4f._0ac4d058

Is this a common practice, or is Microsoft just being Microsoft?

I'm building a deal alert side project that tracks price, review count and stock for about 300 products. Playwright on a small VPS works until captchas, page changes or bad data start breaking runs with no clear errors. I'm looking for a managed amazon api scraping setup that handles browsers, proxies, and retries without much extra infra. What are web devs using for this now?

I was thinking about how many developer tools I've seen over the last few years that promised to make teams more productive. I do agree that some of them were really useful but most just faded away after the initial excitement.

I'm interested in the ones that people genuinely kept using.

What's one tool that actually earned its place? What did it improve enough that your team kept using it?

It doesn't have to be AI particularly. It could be anything from CI/CD, testing, deployments, monitoring, version control, or just a small utility that removed a surprisingly painful bottleneck.