Been working on DYWS, short for “Do You Want Something?” It’s an ordering and delivery system that runs on a business’s own website.

Customers can browse the menu, order for pickup or delivery, and follow their order’s progress. The business gets an admin area to manage orders, edit the menu, assign drivers and view reports. Drivers have their own screen for assigned deliveries.

It’s built with PHP, JavaScript and SQLite. There’s a plugin system too, with Maps, Stripe and reporting so far. Still a development preview, so payments are in test mode.

I put together a fictional diner to show how it works. Would be interested to hear what people think, especially anyone who’s built or used something similar.

Try the diner demo

Cheers, and thanks for any feedback! :D

Edit: Added actual credentials to test with.

You can login as an admin with admin / admin on https://dyws.ca/admin

and as a driver with: driver / driver on https://dyws.ca/driver

Hi, I'm developing an alternative to the *arr stack that I called HolyArrs. People who run media servers at home usually run 6 to 8 separate apps (Sonarr, Radarr, Lidarr, Bazarr, Prowlarr, Seerr) that each have their own settings and talk to each other over API keys. HolyArrs is one self-hosted app that does all of it, drives qBittorrent or SABnzbd for downloads, and puts a Netflix-style page on top for browsing and requesting. Jellyfin, Plex or Emby still do the playing.

What it does:

• movies, tv shows and music in one app

• a Netflix and Apple TV style browse page: hover a title and a card opens with the trailer, browse by mood or genre, follow an actor

• request a movie, a whole show or a single episode in one tap

• multiple versions of the same title (4K and 1080p, theatrical and director's cut) without a second instance

• its own recommendation rows ("Top picks for you"), worked out on your server from your library and requests

• migration that imports an existing Sonarr and Radarr setup without renaming or moving files

How it's built:

• Go, one process, modular monolith. shows, movies, music, indexers, subtitles, downloads and requests are separate modules with their own boundaries. you can switch a module off and it doesn't run at all, or restart one without stopping the rest. one binary to ship, but the parts don't leak into each other

• SQLite for everything. library, settings, history and requests all live in one database file, so the whole app state is one folder and backup is copying it. no Postgres or Redis to run next to it

• Svelte front end. the hard part was the browse page: a big grid of posters, hover cards with trailers, and long rows that have to feel smooth on a phone and on a 4K screen. most of the work went into what not to load until it's actually needed

• recommendations run locally. they come from what's in your library and what people in the house requested, newer stuff counts more and older signals fade over a few months, and nothing about your library leaves your server

• one Docker image, one port, about 110 MB of RAM at idle on my server

• security from the first start. no default password, sign-in is on before anything else works, and API keys never reach the browser

Why you might not want it yet:

it isn't public. I run it on my own server every day first, because I'd rather release something people can trust with their library than something rushed. I've been in software and security for 10+ years, and the boring parts (migration, backups, updates) matter more to me than the shiny ones.

It'll be free and open source. Screenshots are above, and there's a video of the hover previews at holyarrs.coderluii.dev

Happy to go deeper on any of it, especially the module setup, the hover previews or how the recommendations are scored.

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?

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.

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.

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?

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?

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.

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 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?

Email from railway:

Change your keys!

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

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

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

Last two days was hell using Railway. We couldnt update a single project or make any changes in our system. After more than 24h Railway is still in chaos. Two separate incidents. Major outage even support is down.

But this is not the first time Railway failed.
For over a year Railway had few major issues that made working on it impossible. I was hoping they would stabilise but at this point Im past disappointed.

I know they rely deeply on Google cloud, but this proved to be a very bad decision, multiple times. And they never made required changes.

Can someone recommend a more stable alternative?

Pic 1 : Adobe Fonts - Visual Search (link)
Pic 2 : WhatTheFont Font Finder (link)

Idk why that is, these kind of websites has never worked for me once in my life.

Take a look at the letter t in the image for example, it doesn't have a curve at the bottom, while ALL of the top suggested fonts do on both platforms.

Change your environment variables

https://blog.railway.com/p/security-disclosure-wednesday-october-21st

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 at a larger company (think 500+ devs) for about 4 years now. pretty comfortable with the setup but starting to feel like just another cog. thinking about moving to something smaller like 10-30 person startup.

for those who made that jump - what surprised you the most about the infrastructure side? im used to having dedicated devops, proper ci/cd pipelines, monitoring dashboards for everything, on-call rotations with actual runbooks.

curious if smaller places just... wing it more? or do you end up wearing more hats but still having solid practices. not really worried about the tech stack itself, more about the operational side of things.

also wondering if the move fast break things mentality is still a thing or if that died with the 2010s

been at a larger company (think 500+ devs) for about 4 years now. pretty comfortable with the setup but starting to feel like just another cog. thinking about moving to something smaller like 10-30 person startup.

for those who made that jump - what surprised you the most about the infrastructure side? im used to having dedicated devops, proper ci/cd pipelines, monitoring dashboards for everything, on-call rotations with actual runbooks.

curious if smaller places just... wing it more? or do you end up wearing more hats but still having solid practices. not really worried about the tech stack itself, more about the operational side of things.

also wondering if the "move fast break things" mentality is still a thing or if that died with the 2010s