domain-driven-hexagon VS GitExtensions

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/

Domain-Driven Hexagon - architecture (NodeJS code examples)

Can't use any frameworks or libraries? Seems like a terrible idea tbh. I can suggest this repo https://github.com/Sairyss/domain-driven-hexagon - read "modules" and "folder and file structure" sections for some suggestions on how to structure files using patterns like Modular Architecture, Vertical Slicing, etc. Make sure to read the attached links and check code examples.

This is a reasonable intro, furthermore it points out more resources if you would he interested: https://github.com/Sairyss/domain-driven-hexagon

I’ve recently refactored one of my key domains using nestjs/cqrs and was heavily inspired by this repository.

Not a big one, but explains how to combine architectures like clean architecture, domain-driven design, hexagonal, etc. https://github.com/Sairyss/domain-driven-hexagon

I strongly recommand this: https://github.com/Sairyss/domain-driven-hexagon

Here is an example codebase with architectural patterns described more in details: https://github.com/Sairyss/domain-driven-hexagon

I agree that git is almost asking you to juggle commits.

My preference is to use temporary branches and cherry-picking instead of stashing; I mostly use a gui* to work with git so it is easy to select the two or three commits to cherry-picking or see visually if an interactive rebase would work.

* https://gitextensions.github.io/

I use Git Extensions myself as I find the git interface very straight forward, however they still have this fucking insane and frustrating issue: In the mergetool "Theirs" and "Mine" are swapped

Git Extensions is a more-intuitive way to manage your Git repositories in Windows. Its standalone interface serves as an effective, CLI-free means to control Git. Preferred by namtab00, because "SourceTree hides and shortcuts too much git functionality."

I presume this is where one goes to make a feature request? https://github.com/gitextensions/gitextensions/issues

If you're on Windows, I'd start with installing official Git. It comes with a Git Bash CLI and what not. There are also third party apps like GitExtensions and TortoiseGit if you want more UI/shell integration.

Everyone's going to downvote this, but I prefer the GUI over the command-line. I use http://gitextensions.github.io/

https://github.com/gitextensions/gitextensions/releases/tag/v2.51.05 - nice little ui for working with git. unfortunately, v2.51.05 is the last version that I can confirm works under mono (it was the last 2.x version and they completely rewrote the code from scratch in the 3.x series. My understanding was that it lost Linux compatibility at that point).