When I have discrete, separate units of work, but some may not merge soon (or ever), being able to use mega merges is so amazing.

For example, I have some branch that has an experimental mock-data-pipeline thingy. I have yet to devote the time to convince my colleagues to merge it. But I use it.

Meanwhile, I could be working on two distinct things that can merge separately, but I would like to use Thing A while also testing Thing B, but ALSO have my experimental things merged in.

Simply run `jj new A B C`. Now I have it all.

Because jj's conflict resolution is fundamentally better, and rebases are painless, this workflow is natural and simple to use as a tool

And I hope you do. It is so much better than git in every way. It enables working with stacks and the aforementioned megamerges so easily, allowing me to continue working forward while smaller units of work are reviewed/merged.

When I first tried to use jj, I wasn't entirely committed and switched between jj and git. Finally I hit a breaking point being fed up with stacks/merges and tried jj _for real_.

I recommend to give it a serious try for a few solid days and use it exclusively to really understand it. You won't go back.

The jj Discord is a very helpful place. Thanks to everyone there. Great article Isaac!

Same price, fewer applications.

Give any of us a tired morning without coffee and a mis-click, and many of us could be in the same predicament.

But I hope Matthias gets his channel back. I'm a long-time subscriber to both of his channels. Hopefully my comment adds into the pile and brings more notice to him :)

Then I began to exhibit packet loss. For gaming/discord, it's a death knell. I isolated the source of packet loss to be within the CenturyLink network, basically between me and the first traceroute hop. (Also retroactively verified by switching ISPs)

CenturyLink as an _offering_ is great, but their company operations and customer support is... kafkaesque and absurd. They are beyond incompetent and seem to have neither the capacity nor desire to fix any real problems.

When talking with some of the technicians and support people, the insight into their world was sad and disappointing. What a ramshackle company.

I really hope nothing ever goes wrong in your network segment :)

I'm sure there are many more people like me. Please keep making more videos and information. We'll happily pay more to support the effort.

My userbase was in the dozens at most, so pushing out a version OTA usually was effective to get things moving along.

Worst case, I had some code to check if the client version was too old and would shut it down until they updated.

As per models, what kind of details are you asking?

Stack:

- React Native + Expo - Typescript - Supabase - Vercel - Some Vercel/nextJS-ish lamda functions so I could avoid AWS (Supabase didn't have that kind of offering yet)

For me, it was _very_ pleasant to work in. I was able to ship features via OTA updates from idea to live in literally minutes.. sometimes even under a minute.

Loved working with Supabase.

Hope it helps someone!

Comments URL: https://news.ycombinator.com/item?id=32515571

Points: 3

# Comments: 2

Glad it's back up now.. :)

Comments URL: https://news.ycombinator.com/item?id=32026639

Points: 254

# Comments: 248