I have not had this experience as badly with Laravel. Their libraries seem much more stable to me. We've gone up 5 major versions of Laravel over the last year and a half and it was pretty simple for each major version.

Laravel is extremely stable and consistent.

Minecraft is already nostalgia. It reminds me of starting university 16 years ago.

Minecraft to me is similar to unreal tournament (I forget which version) as well as computer hardware from ~2015 onwards. It happened after some sort of critical point of technological development had passed such that it doesn't feel old to me unless I examine it immediately adjacent to something modern.

I suppose that will change for the games if truly high fidelity head mounted displays ever take off. For the hardware I'm less certain because aside from pointlessly bloated web frontends nothing that I do on a day to day basis actually consumes more resources than it did in 2015. Perhaps local AI on low power devices will be the critical point for me there?

> a new hot shot would show up every month and be gone the next when they got bored or frustrated when nobody thought they were special

I don't know much about film industry, and I have a ton of brainfog from being sick today.

Could you say more? What made them a hotshot? They thought they were like, creative geniuses with digital film or something?

They often WERE creative geniuses with a digital camera! Brilliant people! In fact they were the ones who came and went the fastest, what makes you useful in industry is very frequently nothing to do with genius or creativity or mastery of the tools. It's things like reliability, stability, team spirit, open mindedness etc.

Creative genius is one game, but it's far from the only, or even, main one.

Hope you feel better. <3

Yeah same. The idea that you'd be merging code to `main` that isn't ready to deploy is crazy to me, but that doesn't mean you need a `develop` and `prod` branch. The main + 1-layer of branches has generally been totally sufficient. We either deploy to branch-preview environment or we just test it locally.

> the primary branching model the vast, vast majority of people use on Git.

> it's just a historical fact that's not really debatable.

Over my last 15 years of software dev, I have _never_ heard of anyone actually using Gitflow in their codebase.

I'm not saying you're wrong. My experience is anecdotal. But I don't know why you say it's a "fact". Was there surveys or anything?

I'm not questioning your experience, but how "enterprise" is that experience? Gitflow was no small part of my convincing my company to move off TFVC. I doubt they still use, but it was shallow waters for scared folk.

I strongly doubt that my story, just as much as yours, is unique.

I don't quite see the appeal, because Claude Code already supports something similar. They spin up container to make the changes in and then open a PR. I can just use the Claude iOS app to do this. My computer doesn't need to be running or exposed to the internet.

Omnara’s is useful if you have a complex dev setup that’s hard to replicate in Claude’s remote container, or you want to test things out locally without any friction. Omnara tries to make switching between being on your computer and being on your phone feel seamless, whereas in Claude, local and remote dev feel more disconnected.

I can't sit back down at my computer and cd/ssh/tmux into that same environment.

I've just started using Anki and I'm almost grieving. If I had had this 15 years ago I probably would have done so much better in school. I've always struggled with memorizing, but Anki has made this much easier for me. I started learning Japanese 4 months ago and I'm baffled by how much I've retained in that period. Now I'm playing with using it to learn the rules for the OneRing TTPRG.

> In my experience, if you're working on a green-field project, you're working long hours, making very little visible progress, you have to write a lot of code, make important decisions.

Funny, this is the complete opposite of my experience. Greenfield projects I've been a part of have had a ton of highly visible progress with _frequent_ updates to stakeholders basically from day 1. Same goes for complex additional features.

I've seen both kinds. GF projects where the senior devs feel that they have to get something right from the beginning, spending a year just on that piece (a set of widgets, a data ingestion framework, a state machine that covers the entire underlying algorithm). And other GF projects which have frequent updates and are open to development with very few speed bumps.

Of course you can call out the former examples as incompetent or hubris, and they will probably occur less and less, but nevertheless they exist.

I was going to say the same. In my experience I can say without hesitation green field projects is how you advance your career, become visible and get promoted.

What is progress? Are you sure that was greenfield?

I think the OP meant projects that required long investments without immediate returns. For instance, a platform migration that requires many components to be finished before it can even be tested. Or, real greenfield, like a new product venture with a unproven customer thesis. The kind that requires months of work before you can go to market and validade... How do you report progress? Components built, percentage completed? Without something a user can drive or a seller sell, that's not progress... It's just speculation.

I love my Kindle, but I have never been able to use my iPad for reading.

I got HumbleBundle with a bunch of Pathfinder 2e PDFs cheap but I'm still tempted to buy the physical copies.

All of this is cool...but you can do them all on a laptop and you'll probably have a better time.

And those cheap/free things are only available after dropping $1000 on a new iPad

The person I replied to already has the iPad.

As for having a better time on the laptop, YMMV. My iPad is my most used computer by a mile.