ncphillips

Yes. We’ve almost doubled revenue and our customers are very happy with the improvements we’ve made

[flagged]

Yeah let’s be real there was a ton of slop around before AI

Nobody believes that

Isn’t that the same without a headset?

Having switched to jj I totally agree. Change IDs are a huge UX win.

Within my own company, yes. We’ve shipped a lot more features this year with the same number of people. They’re also better features. We get from 0 to 90% in an hour and then still put a lot of effort into that last 10%. The projects have better test coverage, docs, logging, etc. then they did 2 years ago. Stretch goals are reached much more frequently. What used to be 3 week projects are closer to 3 days. Our commit history is cleaner, easier to understand, has has better commit messages because we have Claude rewrite the history before opening the PRs. Our product is faster, more stable, and has nicer UX.

But this is anecdotal. It’s a team of senior devs who already knew the codebase well. We have a ton of detailed guidelines that make sure it’s writing code we deem acceptable. We review each others code, and get LLMs to review, a LOT.

It drastically simplifies the process.

Redescribe, reorder, split, squash, abandon commits is trivial.

Auto-rebasing is fantastic, fix a conflict once and not have to keep correcting.

You can rebase individual commits, ranges of commits, etc. You can also rebase trees I.e. forking branches with a common ancestor, with a single command.

The operation log also makes it feel super safe. You can always undo a jj operation or restore to a past state

Yeah, my solution to this problem has been to get Claude to use jj to create a clean commit history. Each commit serves a single purpose and includes what drove the decisions we made. You lose the noise and still have the meaning.

So I'm a little unclear as to benefit of this. It sounds...wasteful?

I think what you’re talking about is real, but it’s only part of the problem. The issue is it’s poor design. There’s a lack of consistency that is really off putting. Spacing is inconsistent and doesn’t create a sense of visual hierarchy. Buttons, inputs, selects, call-outs, table cells are barely distinguishable from each other, but also inconsistent within their own categories. The copy is also confusing. I don’t even know what this does.

History is immutable ONCE it’s merged. Prior to that, it’s malleable. We rewrite our branch history fairly often. I’ll take a big PR that’s ready, and rewrite the history in a way that tells clear story. This lets me stack PRs so it’s easier for coworkers to digest the work. It hides the messy reality of how it was constructed. It lets the development process follow evolutionary design, without review being miserable at the end of the day. This also makes git-blame 6 months later way more useful, as the commits end up much tidier with better messages and clearer story being told.

Neovim has been game changing. Literally nothing I miss from VSCode or Jetbrains now

Same experience. At first I really didn’t get it and now I could never go back. The ease of rebasing, renaming, reordering, splitting, etc. Has drastically changed the way I work. My PRs are undoubtably much better now, and I am never afraid of messing up thanks to jj undo and the op log in general

Canada is being attacked because its leadership are mobsters who attack everyone around them and then do insider trading to make themselves rich

I don’t buy that Canada is isolated and reliant at all

They can be repaired but it is going to require a very significant amount of work on one side of the border in particular.

People I know change their meal plans if the only options are US products.

Nah because none of us will buy it

In Canada It’s made with Canadian milk.

There’s also other brands of cream cheese.

Canadian here…we also just dont want US milk

Genuine question: if a human did this manually would it be considered derived?

Cool yeah. I got a M3 with 32GB ram and it’s a little iffy. I’ve considered getting a MacMini to act as an in-house

What kind of machine do you have running that? My attempts at local have always resulted in a very hot lap

For doing what?

It’s a mix. Partially a systems problem. We used to have that problem, then we changed the way work is selected. Sales is part of the process, so they’re forced to see all the things we could build and help decide which ones were saying no to. They still promise things occasionally but they hedge a lot more now. And our teams delivery rate has increased dramatically because we’re not getting yanked around all the time.

I work at a 6 year old startup. Essentially every feature and bug fix we’ve shipped in the last year has had LLMs involved. Every project plan involved AI, either for writing or for codebase research. For code review we get AI to do the first pass.

That’s an interesting question, in particular because I don’t think I have a single example

I’ve used it for several improvements to our wysiwyg. I was able to refactor to a much more cohesive architecture that is making future work much easier/safer. We got a fzf like search algorithm for an autocomplete that includes marking which characters matched. It fixed some jank performance issues I was struggling to track down.

Fixed small several bugs last week without even open the editor. It wrote tests that confirmed the bugs, then fixed them. Then I manually confirmed as well.

It built a double entry event log. A single application event produces two logs, one for the person doing the action, one for the person being acted upon.

For a nasty problem we have, we had AI prototype 2 different solutions. Then we reveiewed them as a team. We threw those out but it was very helpful input into our decision making.

jj required a very weird mind shift in how I work, but since it’s clicked I’d never go back. Occasionally it makes easy things a bit awkward, but the amount of hard things it makes easy is incredible. Several patterns of work have become common for me that I would never have done before.

That’s not what this is though.