r/webdev

Can anyone get to railway.com

Been about 30 minutes.

So railway is down, and all my production .env keys are on there without me able to access them to export the project to another hosting service. They apparently got suspended from their google cloud account, leading to everyone's sites going down.

Go to their site, you'll see.

🙃🙃🙃🙃🙃🙃🙃

Junior devs aren't struggling because the market is bad, they're struggling because the work that used to justify hiring a junior dev is just gone. It is quietly camouflaged into what a senior dev can do in an afternoon with Copilot.

The junior role always did the boring stuff, the small bugs, the simple features, the stuff nobody wants to touch, and in return you get proximity to a real codebase and people who've seen things go wrong, that proximity was the actual education.

that boring stuff is what AI does now.

So nobody cancelled the junior role, the economics just shifted and the role kind of dissolved on its own.

Bootcamps are still running, cs programs are still graduating people, everyone's still saying build projects, do leetcode, contribute to open source as if the path is the same as it was five years ago

Senior devs still have jobs because you need actual judgment to work with AI output, you need to have seen enough things break badly to know when the generated code is confidently wrong, but that judgment comes from years of doing the work that doesn't exist for juniors anymore

so how do you get the experience if the entry point is gone

Hey everyone, i'm looking to build a pretty straightforward mobile app for my small business but have literally zero coding background. I've been researching different mobile app builders and there's just so many options out there - some drag and drop, some that claim to use AI, some that are more template based.

I need something that can handle basic stuff like user accounts, push notifications, maybe some simple e-commerce functionality. Budget isn't huge but i'm willing to invest in something that actually works well.

The overwhelming part is that every platform claims to be "the easiest" or "no coding required" but then you read reviews and half the people say you still need technical knowledge to do anything decent.

For those who've actually built apps without a coding background, what platform worked best for you? And realistically, how much time should i expect to invest in learning whatever tool i choose?

I just got a few requests, but my job is keeping me busy enough. Now I'm wondering if it makes sense to start your own agency still in 2026. After all, most people can vibe code what they need. It is only the leads I've got now that make me think...

I'm a product engineer with 10 YOE, so my skills are good. I know some juniors, too.

Most requests I get are way easy, too.

What do you guys think?

This is a really intriguing idea, because I actually often use LLMs in this fashion, forcing them to not provide any code or direct answers, and instead walk through the process iteratively, while manually implementing and taking the time to write the code myself. Slower work, but better work.

started with a CS call back in January, then 2 Zendesk tickets in February, then a Slack thread someone in support kicked off in March that died with zero replies, and first time the issue showed up in our Jira backlog was last week, already P0 and tied to a churn risk on one of our biggest accounts.

sat in the post-mortem yesterday and everyone wanted to know why engineering didn’t catch it sooner, and i’m sitting there thinking, where on that timeline was i supposed to discover this…

Was i supposed to be reading every Zendesk ticket personally or dialing into every cs call from January onward just in case one of them was the one that mattered.

Once the issue reached us it was already an outage in everything but name, and somehow the post-mortem is shaped like we’re the people who missed it.

4 months across 4 systems, and the only team that opens a ticket about it is the team getting asked why it took so long.

dont even know what the right answer is supposed to be.

What it is:

Guess the S&P 500 stock ticker in 6 tries. Works like Wordle — green/yellow/gray feedback after each guess. New ticker every day.

Tickerdle.org

What I built:

- Daily, Endless, and Higher or Lower game modes

- Real-time player counter

- Live stock chart as the background (shows the actual price history of the ticker you're guessing)

- Leaderboard

- Mobile responsive

- Full backend with ticker validation, chart data proxying and daily puzzle logic

Stack:

- Frontend: React 18 + Vite + Tailwind CSS

- Backend: Node.js + Express + WebSockets (ws)

- Stock data: yahoo-finance2 (server-side, so the answer ticker is never exposed to the client)

- Hosting: Hetzner VPS + nginx + PM2 + Let's Encrypt

- No database — game state lives in localStorage

It's been a fun project, combining two things I love, markets and puzzle games. Would love to hear any feedback or feature ideas from this community!

Hello everyone,

Wanted to share a super cool project (IMO) we have been working on. It’s a zero-dependency React data grid, called LyteNyte Grid. Check it out, and hopefully, you will find it useful and save yourself a ton of time.

Some of the reasons to use LyteNyte Grid.

• Crazy Performance: LyteNyte Grid is super light at only 40kb (gzipped) and is extremely fast. It can handle millions of rows and 10,000+ updates/sec. Based on our internal benchmarks, it is one of the fastest grids available on the market.

• Feature-rich: Brings 150+ features, most of which are free and open source. Features such as cell range selection, row master-detail, and row grouping are included for free with LyteNyte Grid. This is something we are quite proud of. There are paid libraries (I won't name them) that offer less.

• No Styling Tradeoffs: With LyteNyte Grid, you can choose whether to go headless or styled. There is basically no tradeoff when considering styling choices.

• Full Prop Driven: You can configure it declaratively from your state, whether it’s URL params, server state, Redux, or whatever else you can imagine, meaning zero sync headaches.

• Unique DX Experience: Our grid is built in React for React and has a clean declarative API, which eliminates awkward configuration workarounds.

We also recently dropped LyteNyte Grid AI Skills. This is a really nice feature if you’re using AI coding agents. It lets you describe an advanced data grid solution, and your AI agent codes it for you. We have been testing this with increasingly complex grid instances, and the results have been awesome.

All our code is publicly available on GitHub. Happy to answer any questions you may have.

If you find this helpful and like what we’re building, GitHub stars help. Feature suggestions and code contributions are always welcome.

• GitHub
• Live Demo

Every website has it, being reddit, youtube, etc

For example on a reddit comment, you might see "2y" to indicate the comment was posted 2 years ago

Initially, the way it worked is that it would show "2 years ago" until we cross the 3rd anniversary, then it becomes "3 years ago"

But recently this behaviour has changed on all major websites I can think of. Now, it might show "3 years ago" if it was 2.6 years ago for example, and I find this rounding to be very confusing

Has it always worked like that or am I not crazy and the behaviour actually changed?

My theory is that they all rely on the same javascript library and that it recently changed its behaviour, but I couldn't verify this

Was surprised to keep seeing the same project appear again and again on my feed. I saw a comment calling out the OP for the same thing, which led to searching their (hidden) post history, which reveals a long tail of the same project getting posted again and again, and somehow always receiving upvotes and positives comments.

https://www.reddit.com/r/coolgithubprojects/comments/1thobk4/comment/omp3p6n/

I am not even against authors sharing their projects. But manipulating votes, adding fake comments, hiding post history, deleting posts that didn't land well (get called out for AI slop), etc. and then doubling down when called out, all of this is just disingenuous behavior that erodes the community's trust.

title

Moved from VS Code to Windsurf two months ago and it changed how fast I build. The AI flow is better than anything I used before.

But VS Code had an ecosystem of security plugins, Windsurf has nothing at that layer. Last week a dependency it suggested came from an account with three packages and zero publish history. In VS Code a plugin would have caught that before I accepted it.

What are Windsurf users doing for security coverage right now?

ran puppeteer in prod for 18 months generating invoices. around 15 concurrent requests it starts leaking, 200-500mb per chromium instance

tried pooling pages, killing zombies on a cron, relaunching the browser every N pages. each fix lasted maybe a week then memory climbing again at 3am

ended up spending more time on chromium babysitting than building features. added a grafana dashboard just to watch puppeteer's RAM

my coworker asked why i dont just use an api and at this point i couldnt argue. 18 months of telling myself id fix it next sprint

anyone actually running headless chrome at scale without it becoming a second job

I've been hosting a domain and webspace for a while now and would like to create a simple website myself. What tools (website builders or AI) are available for this? I only want to create the website and run it at my existing webspace.

I’m trying to work out a better way to get useful feedback on web apps before they’re properly launched.

The problem I keep seeing is that a lot of feedback is either too vague or too polite. People say things like “looks good” or “nice idea”, but that doesn’t really tell you if the landing page is clear, if the first screen explains the product, if the onboarding has friction, if the pricing feels believable, or if users would actually know what to do next.

What I’m trying to improve is the feedback process itself, especially for early web apps, SaaS tools, dashboards, browser tools and small products.

The kind of things I think need checking before launch are:

- does the headline explain the value quickly?

- does the first screen make sense without extra context?

- is the main call-to-action obvious?

- does the UI feel trustworthy?

- is there anything confusing in onboarding?

- does the pricing or offer feel believable?

- would a new user know what to do next?

- does the product look like it solves a real problem?

I’ve found that asking “what do you think?” usually gets weak answers. More specific questions seem to work better, like “where would you click next?” or “what part made you hesitate?”

For people here who build or review web apps, how do you normally get useful pre-launch feedback without it turning into vague praise or random opinions?

I needed a website for my game so I decided to make it myself.
I figured it would be more interesting to do it in vanilla HTML/CSS with a little JavaScript rather than reaching for a framework.

I'm a fairly competent C++ game dev but a complete noob when it comes to webdev.
It took me about 10 hours, was a lot of fun and I'm pretty happy with the result.
What do you think?

Hey Reddit,
I am the creator of agent-qa.

AI has accelerated development which allows devs to build products at lightning speed. But the confidence whether it works isn't there. Though coding agents can write tests on their own but they greedily writes tests to make them pass.

The intention of building agent-qa is to provide an AI native solution to E2E testing.
I have used playwright as a kernel for executing planned actions in the QA harness.

Looking forward to feedback.

GitHub - https://github.com/vostride/agent-qa
Consider giving it a ⭐
Thanks!

Demo - vostride.com/

Im seeing more PRs where the code looks finished on the first pass: types line up, tests pass, demo clicks thru, lint is quiet. Then review gets weird because nobody can say why that cache key exists, why auth runs after the expensive call, what happens when the provider times out, or who owns the fallback when retries hit twice.

Small thing. Pushing back feels oddly impolite because the branch works in the demo, and web dev has always been mostly the boring cases around auth, retries, deploy order, and bad data. AI seems good at filling the happy path, less good at leaving a trail a human can explain later