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.
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.
I don’t know if Gitlab is an industry standard, but I’ve never heard of Forgejo. I worked for a headless CMS company and the only three providers we ever had requests for were GitHub, Bitbucket, and Gitlab. Gitlab is big enough to be generally adopted by governments. I think it’s fair to say it’s at least a lot closer to being an industry standard then Forgejo.
(Aside: I would likely never use Gitlab by choice, and would consider looking into Forgejo)
I’ve recently switched to jj and it is truly amazing. It too about a week for me to “get it”. The tool is amazing but I think there’s way too much emphasis on what it does/allows rather than what benefits it brings to your workflow. If they get that marketing right I could see it growing. If not, I’ll keep using it
Same here. It’s super weird take to me now. Maybe if you’re just writing plain HTML and CSS tailwind would be worse, but assuming there’s a component system you’re going to be just fine. The cascade of CSS is such a foot gun. Localized styles work great and tailwind abstracts away hardcoded values with relative ones
We use tailwind and are capable of building accessible websites without any issue. People could make all the same mistakes with CSS for accessibility. It’s the not knowing how to make accessible content that leads to inaccessible content, not the tool you use to implement the styling.
But I have a workflow I like with git and I can’t see how jj would be better. I’m genuinely curious as to whether it would be or not, but the behaviours people are describing are not things that interest me.
There must be some kind of split in how people work or something. I’ve never had the desire to jump around the git tree. I never squash commits. I basically never stash changes. All the things that people say jj makes easier are things I never even want to do. Not because they’re not easy with git, but because it sounds hard to keep straight in my head.
I’m not a fit expert by any means. The workflows being described do not appeal to me but not because of the way fit works. They sound confusing and I don’t understand what benefit I’m getting out of them. Like, it’s a solution to a problem I’m not sure exists (for me)