1,087 karma · joined June 21, 2010
There are some samples. If you have GPU you might want to fork and improve this, but otherwise slow, but usable on CPU as well.
About usage: it looks like web development gets benefits here, but other areas are not that successful somehow. While I use it successfully for Neovim Lua plugins development, CLI apps (in JS) and shell development (WezTerm Lua + fish shell). So I don't know if:
a) it simply has clicked for me and it will click for everyone who invests into it;
b) it is not for everybody because of tech;
c) is it not for everybody because of mindset;
What's the difference?
In some member states, like Germany, the EDIFACT format, when compliant with the EN 16931 data model, is accepted as a valid e-invoice format.
EN 16931 defines what information needs to be in an invoice (the data model), while EDIFACT INVOIC defines how that information is structured and formatted for electronic transmission (the syntax).
* My 5 years old project: monorepo with backend, 2 front-ends and 2 libraries
* 10+ years old company project: about 20 various packages in monorepo
In both cases I successfully give Claude Code or OpenCode instructions either at package level or monorepo level. Usually I prefer package level.
E.g. just now I gave instructions in my personal project: "Invoice styles in /app/settings/invoice should be localized". It figured out that unlocalized strings comes from library package, added strings to the code and messages files (added missing translations), however has not cleaned up hardcoded strings from library. As I know code I have written extra prompt "Maybe INVOICE_STYLE_CONFIGS can be cleaned-up in such case" and it cleaned-up what I have expected, ran tests and linting.
So why this matter if code works? If you will not look at it anymore then no problem at all, but that's definition of dead code that does not need support and will not be used anymore. I have projects that I do not support for years, but I can return to them anytime and work on them, because they age well like wine.
So in summary I think it was just part of automated process (maybe) or it will become one in the future.