I have a old gaming laptop that is not supported.
Intel i7-7820HK, 4cores 8 threads 2.9Ghz.
Released in 2017.
That’s not old-arse as far as I’m concerned, and I don’t see the need for an upgrade. I’m going to install Linux on this PC because I have the know-how and desire to check out how electron fares. But I can see how that is not an option for everyone.
but it started splitting my commits in chunks
Wait, it can split commits ? I thought you “just” used a LLM to write the messages, but it can also act on the commits ?
How did you achieve this?
I’m really curious to see examples of commit messages.
And more details on how you achieved it, I’d like to give it a go myself, as some of my coworkers commit messages are less than stellar.
Does it write in the conventional commit formalism ?
I bought a moonlander by ZSA about a year ago.
I found the split allows for a much more relaxed position while writing, and being able to adjust the halves individually when I reposition myself is very comfortable.
They also have the benefit of having thumb clusters, giving more work to the strongest finger of the hand.
Another benefit I find is that most split keyboards are fully programmable, which makes customizing it to your needs very nice.
The only drawback I find to this keyboard (apart from the price, which is not cheap) is that it is hefty, and not easy to transport. The fact that it is wired clutters a bit the desktop, if this is something that concerns you.
I recently built a corne low profile yo have something more transportable and wireless, but this is much more involved, as the configuration goes through writing code and not a nice UI.
However the comfort of this new board is very nice.
There was a whole subreddit dedicated to ergonomcal keyboards, ErgoMechKeyboards, which is very interesting to browse, as what I have done is seen as extreme by my coworkers, but tame compared to what some people are do.
You should group your source files by domain, then by feature, e.g. ‘src/foo/model’ and ‘src/foo/exports’.
Is serialization/deserialization the only aim of these structures ? If not, that code should definitely be separated, so as to evolve separately from the structure itself.
If it is the only aim, the code should also be separated, so you can change your serialization type (e.g. from JSON to XML) without impacting the model.
Also you might need another export for compatibility with another software, and you don’t want your model file to grow with the 10 formats you support.