Laravel with Filament is super productive also. Django used to be my goto for 15 years but the frontend infra, Livewire, and flexibility of Filament compared to django-admin are hard to beat.
I've used Redshift for many years and really like it, especially as a user. I'm following the development of DuckDB and one aspect that's nice about it is how predictable prices are when you run it on dedicated servers: https://fet.dev/posts/costs-of-analytics-on-dedicated-hardwa... .
If you don't have huge amounts of data I would take a look at it. Also, Cloudflare R2 might be a good alternative to S3 because there are no egress costs.
Sounds like a DAG based task orchestrator could be a good fit. Where tasks state their dependencies and are allowed to run only when they have all completed.
I'm really excited by Cloudflare Workers. I hope to get a chance to build something tangible with it soon. The developer experience with Wrangler is superb and paired with Durable Objects and KV you got disk and in-memory storage covered. I'm a fan of and have used AWS for 10+ years but wiring everything together still feels like a chore, and Serverless framework and similar tools just hide these details which will inevitable haunt you at some point.
Cloudflare recently announced database partners. Higher-level options for storage and especially streaming would be welcome improvements to me. Macrometa covers a lot of ground but sadly it seems like you need to be on their enterprise tier to use the interesting parts that don't overlap with KV/DO, such as streams. [0]
I played with recently launched support for ES modules and custom builds in Wrangler/Cloudflare Workers the other day together with ClojureScript and found the experience quite delightful. [1]
Second weightlifting. Not really similar or left of field, but a good complement. I found it more interesting after I started following a routine and tracking progress on each exercise, trying to optimize nutrients before/after workout, daily macros etc. Optimizing these things is kind of satisfying.
For example, the other day I had to work out after work instead of in the morning, and I had also been encouraged to do some spinning because of a knee issue. I found that I didn't perform well but I don't what caused it exactly: the cardio before lifting, it being late, tiredness from work, eating schedule, the knee, etc. Kind of similar to debugging.
I would like to know why dark themed apps have become so popular? I'm 30 and use black on white themes whenever possible, only exception being when there are no other light sources, like reading from bed.
You're throttled if you share a public IP address with many people who are fetching anonymously (or at least you used to be). Authenticating your requests fixes that. I'm guessing this is similar.
I'd argue that there's a significant mental overhead reading code when it doesn't follow the same conventions, and that enforcing a style guide is a matter of having no broken windows. But of course there's no point trying to make shit look good.
I'm doing backend development but interact with frontend developers all the time. Something I've noticed, especially among younger devs, is that they are sometimes unknowledgeable about how HTTP, DNS, certificates, and related tech work, and have a hard time grasping why state persistence and synchronization need to be done a certain way. The problems arise when something goes wrong and they immediately need support from backend, when a little more knowledge about the technologies below React or Angular would suffice.
Brings back memories. 15 or so years ago in rural Sweden, me and some friends were frustrated about only having access to 56 k. There was this local networking guy who set up the networks at local LAN parties that we asked for help. It ended up with the brave one of us climbing a local mast to see how many roofs we could see. Then we called the mast/tower owner to ask what it would cost to put some equipment there. We could see around 20 roofs and it would cost ~2k USD/mo. On top of that we'd have to pay for other equipment of course. We figured it wouldn't be worth it really.
Years later we got ADSL but last year they cut the copper wires and now wireless (up to 4G) is the only option, and it works so so.
There's kind of a battle going on between proper fiber (realistic because of subsidies/EU grants) and WISP proponents currently. Marketers of the latter like to call it "air fiber" but that's not really fair IMHO.