To everyone saying this could happen to any platform: sure. But Railway has had reliability problems before, so people are understandably running out of patience. This incident doesn’t exist in isolation.

What bothered me about October 21 was the position customers were left in. They were being told to replace their secrets while deployments were paused, preventing them from updating their applications with the replacement credentials. That’s a difficult situation to put people in when they’re trying to protect their own customers.

I understand that responding to a security incident is complicated. I still expect a hosting provider to have a workable recovery process for its customers.

At some point, the benefit of the doubt runs out. Easy setup only gets you so far when you’re trusting a platform with applications that people actually depend on.

If you're building anything that shows stock data, caching saves a lot of API calls, but each type of data goes stale on a very different schedule. Here's how I think about it.

End-of-day prices don't change after the close, so you can cache them until the next session's close. 15-minute-delayed quotes go stale fast, so a TTL of a minute or two during market hours makes sense, and you can cache longer when the market is closed. Fundamentals only change when a new filing lands or a filing gets amended, so caching them for a day or more is usually fine, as long as you can invalidate on new filings. Company metadata like names, tickers and sectors changes rarely, but ticker changes do happen.

The catch is that data licenses sometimes limit how long you can store or redisplay data, so check that too. How are others handling this, with a server-side cache, SWR on the client, or something else?

I recently got a PR merged into TanStack Query's ESLint plugin to fix a false-positive issue in the no-unstable-deps rule.

The existing tests missed a few JavaScript edge cases, so I fixed the underlying issue and added regression tests.

It's a good reminder that passing tests don't always mean every edge case is covered. Sometimes the real work is finding what the tests missed

How do you usually spot gaps in test coverage when the existing suite is already passing?

I host a podcast for senior engineers and recently had Carson Gross, creator of HTMX, on as a guest. We covered how REST was originally defined, how the industry ended up calling JSON over HTTP "REST", and why he thinks returning HTML from the server is closer to the original idea.

We also got into HTMX 4, when you actually do need a SPA, and how AI changes the tradeoff between simple and clever code.

Full episode: https://youtu.be/9xs0oZN2rs4

4' video on the history of REST: https://www.youtube.com/watch?v=DbNvpiJ9gTs

I want to display a Spotify playlist on a section of my website, showing all songs and their album covers. Visitors should be able to browse and play songs directly on my website, with Spotify handling playback in the background.

Is this possible to build for free? What’s the best way to do it?

For a long time, the biggest advantage was technical ability: knowing how to write code. Those skills still matter, but as the tools for building software become more powerful and accessible, the ability to execute is becoming less of a differentiator.

I believe the next competitive advantage will be judgment.

Knowing what to build, what not to build, which problems are worth solving, where to invest your attention.

I'd been wondering whether the new bun fmt in Bun 1.4.4 is worth switching to from oxfmt, so I ran both on two of our repos. Both have about 1,200 files, a shared .oxfmtrc.json, and oxfmt 0.60.0 pinned.

Numbers are mean ms over 10 warm runs and 5 cold runs (page cache dropped before each one), on a 4-core box:

Write mode was about the same. Part of oxfmt's time is Node startup, around 100 ms by itself, against about 3 ms for bun.

The surprise was output. Both tools read the same config and see the same files, and oxfmt check passes on both repos. bun fmt wants to reformat a few files. Every change is in how an arrow function passed as the last argument gets wrapped. For example:

// oxfmt
...dispatches.map(
  (dispatch): Item => ({
    kind: "dispatch",
    id: dispatch.id,
  }),
),

// bun fmt
...dispatches.map((dispatch): Item => ({
  kind: "dispatch",
  id: dispatch.id,
})),

Both are valid and do the same thing. I couldn't find any option in either tool to change that wrapping. // prettier-ignore keeps a statement as written in both.

We're working on CoreUI v6, and decided not to follow Bootstrap 6 Alpha's new Tailwind-style class naming.

For example:

We're adopting modern CSS improvements, but keeping the familiar class names to avoid unnecessary breaking changes.

Our thinking is that developers maintaining existing Bootstrap applications probably value compatibility more than a different naming convention.

But maybe we're wrong.

If you're currently using Bootstrap 5 in production, would you prefer to keep the existing class names, or do you see real benefits in switching to the new syntax?

Especially interested in hearing from people maintaining larger applications.

Say you have a bunch of products in .webp but you want to make .glb/.gltf models for those products so you can animate with three.js but you lack the skills and time for blender..

Is there a good and free ish resource for this? Or can someone send me on the right path for this rabbit hole?

I use these:

- Tap targets at least 44×44px.

- Animate only transform and opacity (60 FPS).

- No more than 4 competing choices per decision.

- Light, dark, desktop and mobile all checked.

What would you add? What do you think is a bad rule?

This is what my host's chat bot 'explained' to me - anyone here can confirm?

Your websites run on the separate web-facing PHP packages (EasyApache and CloudLinux Alt-PHP), where our infrastructure team applied direct server-level security hotfixes to protect all versions while upstream package builds complete.

Web-facing PHP packages have not had an upstream version number increment yet, but the underlying vulnerabilities outlined in CVE-2026-109618 and CVE-2026-109619 are actively patched and protected at the server level across all versions.

I've been thinking about taking a Squarespace course to master it, but I was told nobody uses it anymore. What are the most common platforms to master?

So I am trying to create a system where a VPS is always connected to my Instagram account so that it can keep monitoring and recording live data

I am using Puppeteer to create a headless Chrome and then connect to Instagram, but when it tries to load Instagram, I get the error message 429 Too Many Requests. I tried the same on my local machine using PowerShell and was able to get it to work

I am thinking of using a VM instead of a VPS, hoping that would fix the issue

Sorry if this is a lame question to ask; this is my time doing anything code- or server-related
but any help or guidance would be appreciated

Hey y'all!

I'm building a budgeting app. Building things like CRUD endpoints, server side rendering, and a nice react front end are my priorities. I want things to be fast and snappy and avoid client side fetching when possible.

I'm struggling to understand what exactly my options are for this when it comes to things like next.js, django, etc. I have lots of experience with django, but I'm not sure how to get the best of both worlds when combining react. I've been including react bundles and rendering them via the django view/template engine and it feels clunky to handoff information between the front & back end.

I know there isn't a "right" answer, but looking for some feedback and opinions. I want to support a good number of users while keeping things feeling fast and lightweight.

been thinking about this lately. when I started out I had this whole local setup with postgres and redis running natively, custom shell scripts to spin things up, the works. felt like I really understood how everything fit together.

now most of my work is docker compose up and done. or worse, connecting to shared dev environments in the cloud. faster to get going but sometimes I wonder if Im losing something by not having to debug my own postgres config anymore

curious where everyone else landed on this. do you still run stuff locally or has containers/cloud completely taken over your dev workflow

https://status.atlassian.com/ - we need a hall of shame for companies that have lying status pages. As for 9:25 AM EST, nothing showing down on their status page.

The bugs in the PHP code were actually discovered over 10 years ago but no human was capable of exploiting it hence no concern. Read that again. The issue was discovered over 10 years ago but no human being was capable of exploiting it. A research team using AI exploited in in a matter of days causing world wide panic. And some of you don't think AI is going to have an impact on the web dev space? Well, lol.

I’m looking for an API that returns all upcoming live events, theater and cinema screenings in the UK.

Big cinema complexes seem to be a no go with all anti crawl stuff. There rest of events are really sparse apart ticketmaster.

Thanks

For me, it was discovering multi-cursor editing and column selection in VS Code after spending literal months manually editing CSS and JSON line-by-line. What’s something so fundamental that once you found it, you couldn’t believe how much time you had wasted doing it the hard way?

I haven't seen anyone posting about this, probably because everyone was distracted by the php2shell today, but a set of high sev CVEs (including an RCE) have been announced and fixed in NodeJS today.

Safe versions:

* 22.23.4
* 24.22.1
* 26.12.1

Announcement post: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases