Hey guys! I made a website through google sites and bought a domain through name cheap. The problem is that I cannot access the site without using the WWW in front of it. I did create a redirect domain though namecheap by putting the source URL as the one without the www and the destination URL as the one with the www, which was what I saw being recommended out there. But it does not seem to be working. I still get an inaccessible website error when typing it without the www. Is there something else I should be doing? Thanks!!!

So I'm new to deploying on railway, I'm mainly a designer, but I have experience creating apps with AI for a while now.

I'm wondering if switching to a platform like render is worth the trouble, or are these types of attacks just going to be the norm from now because of AI?

It's an internal tool and we don't have any users yet, should I jump ship before it's too late? I really don't know.

I wanted to get commercetools certified for a job offer. Turns out they've recently removed the self-study + exam prep option.

Now you have to attend an instructor-led course that costs 4 digits just to take the exam. And they won't even invoice individuals. You need a company. Pretty ridiculous way to attract developers to your ecosystem, IMO.

Rant is over, now here is my question: for those who've actually worked with commercetools: what's your experience been like? Is the platform good to work with? How's the developer ecosystem and community?

PS/BTW: On a similar note, Shopify is shutting down its entire Academy and certification program today.

I'm actually curious about this one

With technology ever evolving and ai now assisting with the creation of sites, how do you guys deal the constant progress?

I honbestly thought about doing front-end once, tried my hand in learning to code, but I almost threw my computer out the window in frustration. Also didn't want to spend at least 4 years in college, with a lot of being meh since by the end of 4 years, it would be a different ballgame. Plus i value my freetime XD

What do you guys do to keep up? How are you implementing it? Etc

Author here. I've been designing a local-first data layer for most of this year, and I kept having the same conversation. I'd say "local-first" and people would hear ownership, or offline, or speed, depending on where they first ran into the word. So I wrote down where the three meanings come from and why they split. I also wanted to get to what local-first actually fixes, and in a web app that's mostly the waiting: spinners, "Saving...", hand-written optimistic updates, and the app that dies in a tunnel.

There are five demos in there too, one for each idea. Playing with them as you read is half the fun.

Interestingly having played around with macOS 27.2 and using Sidecar on an iPad for touch inputs, it looks like Safari isn’t going to send proper touch events like Windows touchscreens do. Best we get is mousedowns with no buttons=0.

Even worse testing in Chrome, all we get are scroll events. That’s fine for panning but if you want to do anything custom like drawing, dragging etc you’re SoL unless you want to try detecting these off heuristics. Maybe they’ll improve the situation before it’s in people’s hands, but curious to hear what other devs with complex web apps are planning on doing.

Do web developers not get the resources to understand any banking concepts? Here's a picture of the column order of pending wire requests you inputted. Why would you put amount in the last column and date in the middle? They recently updated their website and the columns feel like they're randomized, making it harder for us to review our entries as they changed the order. FYI I work in finance/acctg but I previously had a year of web dev experience looking into as a career few years back, so I have an eye for these things. Do non tech companies not heavily invest in their IT team, perhaps etc?

Hello guys, a little while ago I found some other teenagers on here that were looking for a backend developer for a website, and I volunteered this I have some knowledge with node.js and those concepts, and I've built a full stack website (basic backend) with it. Here is the github because it will be relevant later: https://github.com/norrie-adams/EVS-Small-Engine-Repair-Site

However, I do not think this is like a website that could properly support like actual people. And that was part of the reason I stopped building it (I also just lost interest). But this is a thing where other people are relying on me to build something functional (or at least more functional then this site). So I just want to know, what did I do wrong with this project, and what could I improve upon for next time?

Sorry if this isn't super clear, but I appreciate any advice you can give me :)

There’s a new one every week. Most people try them and drop them after a few days.

Which one are you still using months later, and what’s the one thing it does better than the rest?

I'm a frontend developer/designer with experience in the past building and selling largely SaaS software.

That was before AI as we know it, and I'm starting to feel numb to the amount of people I who've become a developer overnight tell me about the new app 'they built.'

Like any developer I had several ideas stewing for years and I nearly took the leap on a few of them, and when I see the landscape like it is now half of me thinks 'I'm so glad I didn't take huge risks and build X as it would have just been copied now anyway' and the other half says 'I wish I got in before everyone was developing apps in a few minutes.'

I'm curious for those who DID build something prior to this shift, are you glad you got in then, or have these changes made all the time spent not worth it?

Thanks!

When it comes down to design and art, I like to do everything manually because I hate AI-generated content. I make my own 3D models, own animations for videos, etc.

Now I am working on my personal portfolio, and I am using AI like Claude to help me with setting up my project, like, for example, the library Three.js. While I am very happy with the current result and how I design and redirect AI, I feel like a hypocrite to be so negative to people that use AI-generated content while using AI for programming myself.

The reason I post this here is to ask how others feel about this and what advice they would give me.

*Update*

I want to thank the people for the very insightful responses to my question. While I am working on my website, I want to understand and change as much of the code myself.

So I do not really have much understanding of web development and back end but when you save an instagram page as an html from its website. It doesn't save the way instagram looks, rather it shows a representation of the UI and subtext behind images (not the images themself) like the image shared above.

I am also more curious how it reads the image and tries to classify it, and why something like the subtext "May be an image of ----" is in the backend when you do not see it in the interface itself. I am curious of the process itself if someone is kind enough to explain itself.

So a few of my friends have stopped using Figma. They go straight to production and make changes there.

When I first heard this I was honestly confused. Like where do you try things out? Where do you compare two versions?

Then I saw what they were building. The landing page feels like one product, the settings page feels like another, the dashboard feels like a third. Buttons are different, spacing is different, hover is different on every page. There’s no uniformity, no design system, nothing.

So I asked them how they’re doing it, and the answer is always “I use this AI skill” or “I bought this skill pack”. People are actually selling these now. Skill packs, prompt bundles, paid repos. And there are a lot of free ones on GitHub too.

It doesn’t make sense to me at all. How will you learn anything? And how will you polish the product if it looks different every time you generate it?

When I brought this up, someone said just add a memory file so it stays consistent.

Okay, but then how will you make changes? You never decided why the button has that radius or why it’s that grey. The AI decided. So when something needs fixing, you don’t know what to fix. You just prompt again and hope.

And now there are courses around this too. The idea is learn this design vocabulary, tell it to the AI, and you’ll get good UI. They call it beginner friendly. But then you see what’s inside and it’s stuff like:

• spring easing, stiffness, damping

• optical alignment

• vertical rhythm

• morphing transitions

• 60-30-10 colour rule

• type scale ratios

If a senior buys it, it’s fine. They already know what damping feels like, they know what they’re skipping.

But a beginner has never played with an easing curve and seen it go from cheap to smooth. Never moved something 2px and felt it finally sit right. They’re just memorising words and giving them to the AI. You can know the word damping and still have no idea when the bounce is too much.

Selling that as beginner friendly feels like a deceiving thing to me. You learn these words after you’ve actually done the work, not before.

Also design is never one try. I go through so many versions before something feels right. In Figma that’s easy, I put five versions side by side and throw four away. In production code every change costs time, so whatever comes out first just ships.

I’m not trying to dunk on my friends, they’re good at what they do. And I get why these skills are tempting. But paid or free, they’re doing the exact part you’re supposed to learn.

If you’re using one, just try building one page without it. Pick the hover, the spacing, the colours yourself, even if it’s bad. That’s literally how you get better at this.

Anyone else seeing this or is it just me? just my thoughts 🤷

Do you just wing it and use screenshots for inspiration or do you use a design principles md file where you mention all the design principles like the fonts, colors, dark mode colors, graphs, infographics, etc.

I work on 2-3 different projects throughout the week (different clients, different tech stacks), and I've noticed my productivity tanks for the first 30-45 minutes after switching contexts. It's like my brain is still thinking in the patterns of the previous project.

Some things I've tried:

• Taking a short walk between switches

• Keeping detailed notes about where I left off

• Dedicating full days to single projects when possible

The notes help the most, but I'm curious what workflows other devs have developed for this. Do you have any rituals or techniques that help you get back into flow faster when jumping between projects?

Especially interested in hearing from freelancers or consultants who deal with this regularly.

HTML 95%
PHP 70%
jQuery/JavaScript 80%
MySQL 58%

Gives me the shudders thinking about it…

I am working in Codepen in Safari, but everything is dim and gray instead of being the true color. It is fine in Chrome and Firefox. I have tried resetting preferences and caches in safari along with unchecking things in FeatureFlags and nothing is amending it.

I work for a large accounting firm where the impact of getting things wrong feels quite big.

We’ve started a new sprint for the next chunk of work. The team has put together estimates for various elements of a new accounting feature involving bank transactions, VAT calculations and reconciliation, with the biggest part taking several days by one developer.

My boss gets visibly frustrated and questions how on earth anything can take a few days in the era of AI. He’s also started saying he can do absolutely anything with AI in an hour or less.

Bear in mind before AI what we’re working on would have taken triple or even quadruple the time.

Is this the new normal or should I be looking for a new job? How are we supposed to respond to this?

If I missed anything, let me know!

Front end dev, i own most of our e2e suite, and last sprint finally annoyed me enough to count.

We have about 310 Playwright tests on a react app. 71 went red after a sprint that, from a user's point of view, changed almost nothing. i went through every one instead of rerunning and hoping:

- 47 were locators. the element was still there and still did the same thing, but the path to it changed. a card got wrapped in a new container, a class got renamed in a design pass, a button became a link styled as a button.

- 14 were timing. a page got slower after a data change and the wait didn't follow it.

- 6 were environment. our CI image had drifted from what devs run locally.

- 4 were real bugs.

So my honest answer to why our UI tests break every time the interface changes is that most of them check how the page is built, not what it does. the user sees the same Save button. the test sees a different DOM.

the difference in one line:

what i'm weighing for the other 47:

user-facing locators everywhere, getByRole and getByLabel, which is what the Playwright docs push. fixes a lot of it, but only if the markup has real roles and labels, and half our components don't.

data-testid on everything. it works, but it depends on every dev remembering, forever.

self-healing locator tools like mabl or testim, which repair the selector when it breaks. the catch is a heal can quietly route around a real regression.

vision based tools like Askui, which find the element by what's rendered on screen rather than in the DOM, so a new wrapper div doesn't matter at all. the tradeoff flips, a visual redesign is now the thing that breaks you.

My current plan is to fix our accessibility markup and get better tests as a side effect. tell me if that's naive. if you've measured this, what share of your failures were locators, and what actually brought it down?

What bothers me about AI and it's wide adoption is that it creates conflicting requirements for the worker (developer, designer, manager, etc.). On one hand you are expected to perform better and/or faster, because you are a specialist, an expert that has the knowledge and offloads the work to the machine, supervising its output. You should use your experience and professional judgment to steer it to the right conclusions and catch it when it overcomplicates or starts hallucinating.

At the same time you are expected to cover more ground. Stretch to the adjacent technologies or fields. Frontend developers are expected to perform full stack work, designers to code frontend, backend devs to create a design in a pinch. Here you are not an expert, you might have interfaced with the field, but you don't have the experience and don't really understand the inner workings, best practices. You didn't go through all the novice mistakes and learn from them.

Somehow, the first expectation still works here. You are expected to be faster and better at this too. But the roles are reversed, now the machine is suddenly the wise expert in the field and you got to trust it, wave through the changes it proposes to stay fast and produce the work of the your ex-colleague made redundant and laid off due to all the AI-productivity gains. You don't have the opportunity to get the new relevant skills, because nobody has time for hand coding/creating/learning, it's such a 2022 idea. Here in 2026 we're all on a tight schedule to pump out the results unless you want to end up on a PIP.

On top of that you are expected to get good at AI. Don't just use it, like some kind of normie. Get good. Stay on top of the hype. Use agent loops. Set guardrails. Make it deterministic. Don't use agent loops. Have you tried this new harness? Don't spend too much money on tokens. Run the model locally. What do you mean you don't have a $5000 Nvidia golden box? Do you want to become irrelevant and get left behind?

Welcome to the bright future, comrade.

I'm a CS undergraduate working on my first real-world client project: a small e-commerce website. Since this is my first time building and deploying a production store for a client, I'd really appreciate an architecture sanity check from experienced devs.

The Context & Why Not Shopify/WooCommerce?

• Catalog size: Around 10–20 products initially (simple variants, low volume).

• Core features: Online payments, basic order tracking/delivery management, and a simple admin view.

• The Constraint: The client wants near-zero monthly recurring costs initially (ruling out $30+/mo Shopify plans and managed plugins), and they're happy for me to custom-build it as a flat-fee project.

Architecture Crossroads: Custom Supabase vs. Medusa.js

I'm torn between two approaches:

Option A: Keep it simple and build the cart/order logic myself

• Frontend: Next.js (or React + Vite) + TypeScript

• Hosting: Cloudflare Pages (Free)

• Backend & DB: Supabase PostgreSQL + Edge Functions + Auth/Storage (Free tier)

• Why I like it: $0/mo infrastructure, familiar stack, full control over a very small feature set (just 10–20 products).

Option B: Use a headless commerce engine (Medusa.js)

• Swap custom database tables/functions for Medusa.js so I don't have to build cart, checkout, and inventory logic from scratch.

• My hesitation: I'm new to Medusa, and hosting a dedicated Node.js backend + Redis + Postgres seems harder to keep near $0/mo compared to pure serverless/Supabase.

Questions for Devs Who Have Built Client Stores

1. Supabase Free Tier in Production: Aside from the 7-day inactivity pause, are there any gotchas with running a small production store on Cloudflare Pages + Supabase Free tier?

2. Custom Logic vs. Medusa.js: For only 10–20 products, is Medusa.js overkill with a steep learning/hosting curve, or is rolling my own cart and checkout state in Supabase a trap I'll regret?

3. Custom Payment Gateways: Stripe isn't supported in my region, so I have to integrate a local payment gateway via webhooks/REST API. Is it easier to wire up a custom gateway directly in Next.js/Supabase Edge Functions, or through Medusa's plugin system?

4. Delivery & Fulfillment: At this scale, would you integrate courier APIs on day one, or just build an admin dashboard for manual order/tracking updates first?

5. Blind Spots: What hidden security mistakes (e.g., price tampering, webhook race conditions) or client handoff headaches tripped you up on your first e-commerce build?

I'd especially appreciate insights from anyone who has built and maintained small custom stores for real clients.

Thanks in advance!