I don't think it's even a broad strategy from PM or higher ups. I actually think it's engineers inside the company who want to play with the coolest hardware and the build features for the newest stuff. Features can be made to work with older hardware but that requires more time and optimization which they never get, so someone takes a call that x and y features only work on newer gen hardware.

In my new position (on a different product) I don't have enough fingers to count how many times the previous guy bullshitted the PO/PM with "that's not possible" of having some features / workflows enabled. Just because he didn't bother thinking through it or just didn't want to do it. Most of the stuff is a bit boring but just a few days of work and test. So yeah I entirely agree with you.

>I don't have enough fingers to count how many times the previous guy bullshitted the PO/PM with "that's not possible" of having some features / workflows enabled. Just because he didn't bother thinking through it or just didn't want to do it.

Or just because if somebody who knows the code inside out doesn't shoot down most new stupid feature requests, the product would end up a slow overcomplicated mess of random features and technical debt.

I think it's a bit of both and perhaps 10% AI. Companies like Block are bloated for what they offer.

I can't tell if you're being sarcastic or not, but it will happen sooner or later.

It's interesting how this comes up when the west is the one that is trying to catch up :)

Fair enough, but the point still stands: innovation of equal benefit compared to isolationism once more with a hefty share of underhanded copying, which will ultimately result in similar technical capabilities anyways.

While historically this has been difficult to achieve, when innovation cycles shift there is an opportunity to shift ingrained practices too.

I do the same. Directed tasks with smaller context and start a new "chat" when it's done what I want.

Even as a techie, I prefer and use iCloud for exactly this reason, especially for stuff I share with family. I don't want me to be the bottleneck for what is considered basic functionality these days.

I actually I'd be even willing to downgrade my car one level if I'm not driving and just sitting in the back seat. Will likely be cheaper for me to own even with the increased subscription.

I've been meaning to get more components for a diy NAS since atleast the last year and just been pushing it lazily. I'm literally kicking myself now when I actually started looking up deals for this black friday.

Same here, I was waiting for DDR5 to come down in prices to upgrade from 32 -> 128gb. Could have done it for 200-300€ a few weeks ago, now I'm just sad.

Depending on how many disks you need, buying old PCs on eBay is the way to go because there are still some Xeon E3 ECC models available cheap ($100) with plenty of RAM (16GB) and four SATA ports for a NAS.

Check used RAM. I've been reading those are still often fine, pricewise

GraphQL sure, but I'm not sure I'd put kafka in the same bucket. It is a nice technology that has it's use in some cases, where postgresql would not work. It is also something a small team should not start with. Start with postgres and then move on to something else when the need arises.

One of our final projects during university was to design and program a basic database in C. Even after 20 years I think that was one of the most one I've had in a project.