12/31/2023 0 Comments Sourcetree git flow slowIt is easy to integrate a CLI into any type of existing terminal workflow you may have with other tools / commands.CLI commands are uniform and consistent, GUIs change around all the time and now suddenly you cannot find the feature you used to have.GUIs will sometimes not have all features available, or be slow to implement new features.Since things are not abstracted away from you, it pushes you to learn and understand what is going on more so than a GUI with a single button that maybe does 3 things under the hood.Knowing the commands makes it a ton easier to create custom workflows, scripts and routines.Especially when you start creating your own aliases and shorthands.Speed, when you know the commands you can typically do things faster.Here is my list of reasons to love the terminal: also changes done on a feature branch can be checked via continious integration (running all tests) and later on you can merge that back into your main line.The reduces the burden in your brain to keep track of which stage/chunk the appropriate change is contained in etc. In git it's easy to do just:Īnd learn to merge things etc. If you like to work by feature I strongly recommend to work with branches instead (or learn it). which are driven by command line.also linux/unix tools and even on Windows (WSL) is going into that direction even more over the years.Ī recommendation based on your git workflow. The first recommendation I give them all is to learn keyboard short cuts.Īlso there are today so many tools out there like kubernetes, docker, terraform, ansible etc. The same thing is true for IDE's many people (in particular juniors) using mouse etc. That also helps if you sometimes get onto systems (servers, docker containers etc.) where you don't have any UI tool.Apart from that you learn over the time to write scripts which can simplify tasks.and make you even faster. At the beginning most of the students where really annoyed of being forced to use the command line but later they realised that they learned the basics/concept of the tools and it way easy to adapt to the UI tools if they like to.but most of them have learned the power of the command line. I have held a lot of trainings/workshops about tools like git,svn,docker, Maven etc. Not that simple answer: You will learn how tools are working (understand the background of the tools for example git or other tools as well) better than via UI tools. The simple answer to this is: In general it's faster. Either one, people should use what they are comfortable with. On my use case, I find using gui more practical and just use command line occasionally on things not covered by the ui.Īnyway, whether command line or gui, i always think of both as means to an end. I also find handling multiple git submodules to be very easy using gui. When reviewing via visual diff, I can easily spot experimental codes that should be removed, tabs instead of spaces, etc. Majority (not all) of the people who worked closely with me who originally uses command line, they switched to gui once they see my workflow and how efficient things are when using a git ui such as visual diff with live edit. They asked for my help and I did it on gui and was able to solve it immediately. Previously, I have two senior engineers trying to solve merge conflicts using command line. I find GUI's approach with 3 or even 4 panels(base, theirs, ours, result) way easier to analyze, than single screen approach in CLI forgot to mention resolving merge conflicts. automation: substitution characters in path git add - '**/*.test.js', using "previous HEAD" in format of or HEAD~10 in all commit-centric operations, and last but not least - ability to chain multiple operations through shell and pipe "|"(cannot give live world example from the top of my head, but I definitely used this for several times). Any GUI tool will miss something that git supports for CLI. Just an random example: Inteliji IDEA has a ticket open for last 3 yest on support per-line commiting(what git commit -p already does - and does much better with ability to edit-on-the-fly). Since UI tools are built on the top of CLI, latter will always be more powerful. For UI client it's always an extra cognitive load - some actions are shown as buttons, some are hidden in menu, some - as a checkboxes in Preferences. You always pass parameters in format - or - with value separated by space. unified user interface - even CLI has this - all parameters, formats expected, command structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |