Re:Why software engineering processes and tools don’t work f...
by barumi on Thursday October 15, 2020 @02:56AM
(#24785663)
> (...) as git is possibly one of the worst SCMs for non-programmers because its command set is so bottom-up,
In your personal opinion, what's so "bottom up" about checking out code from a repository and committing changes to a branch?
> (...) while at the same time it exposes an interface that makes it all to easy to screw things up catastrophically.
What? Care to point out a single example of what you perceive as being one of those "catastrophical" failures?
In all my professional life, which includes a bunch of years as a data analysis, I never experienced a single failure with git. Not a single one.
In fact, the only failure I ever experienced with git came from a stupid error I once made by tracking a git repository which found its way into a Dropbox shared folder.
Care to shed some light on what you perceive as being your pain points?
In your personal opinion, what's so "bottom up" about checking out code from a repository and committing changes to a branch?
> (...) while at the same time it exposes an interface that makes it all to easy to screw things up catastrophically.
What? Care to point out a single example of what you perceive as being one of those "catastrophical" failures?
In all my professional life, which includes a bunch of years as a data analysis, I never experienced a single failure with git. Not a single one.
In fact, the only failure I ever experienced with git came from a stupid error I once made by tracking a git repository which found its way into a Dropbox shared folder.
Care to shed some light on what you perceive as being your pain points?