Show HN: I made a tool that made me faster at Git
51–60 of 235 posts
Re: Show HN: I made a tool that made me faster at Git
#52Re: Show HN: I made a tool that made me faster at Git
#53Earlier quoted context omitted.
Jira has some asinine design issues, e.g. the only way you can link a git commit to a ticket is by putting the ticket ID into the commit message, generally has confusing choices for UI, code blocks {code}are annoying to add{code} and don't follow any existing conventions, integration with Confluence sucks, basic functionality is locked away in paid extensions, the list goes on
MVP Jira just needs to present a list of stuff to do. But now it's used like a panopticon of social control where I work. And I'm thinking I'm not the only one with stuff like Scaled Agile being out there.
Most of product teams still don't function with any kind of actual agile process. Many try to fake it by endlessly throwing all of their work into the JIRA agile boards, which constantly have sprints rolling over, and are impossible to track any kind of actual velocity with. On our team we just said screw this and went back to getting things done, and tracking things how we wanted to track them.
Don't even get me started on the nightmare that is JIRA TCM, which my company is currently still stuck with for test case management.
Re: Show HN: I made a tool that made me faster at Git
#54Earlier quoted context omitted.
I want to edit the commit message of a commit that is 5 commits in the past, that I have not pushed yet. What is the command to do it? Okay so it turns out I made a minor typo in that commit and I want to change it without adding any more commits. What is the command to do it? Okay so now I want to take all commits that have "bugfix pickme" in the subject and cherry-pick them to master. What is the command to do it?…
> I want to edit the commit message of a commit that is 5 commits in the past, that I have not pushed yet. What is the command to do it? Probably something like: git --rebase -i --force HEAD~6 ...followed by setting the commit in question to "edit"; then once the rebase pauses on that commit, using `commit --amend` to edit the message; and finally `rebase --continue`. > Okay so it turns out I made a minor typo in tha…
git inbox --full-conversation -next
to read an email, and read it in less.Re: Show HN: I made a tool that made me faster at Git
#55I've been using Fork: https://git-fork.com/ because of its 2 primary advantages over SourceTree: • Dark mode • Tabs
Re: Show HN: I made a tool that made me faster at Git
#56Re: Show HN: I made a tool that made me faster at Git
#57Earlier quoted context omitted.
Jira has some asinine design issues, e.g. the only way you can link a git commit to a ticket is by putting the ticket ID into the commit message, generally has confusing choices for UI, code blocks {code}are annoying to add{code} and don't follow any existing conventions, integration with Confluence sucks, basic functionality is locked away in paid extensions, the list goes on
MVP Jira just needs to present a list of stuff to do. But now it's used like a panopticon of social control where I work. And I'm thinking I'm not the only one with stuff like Scaled Agile being out there.
Thanks for putting this into words for me. This is exactly how I feel about Jira. Incompetent middle management automates their micromanaging and enforces bad ideas about how their subordinates should do their jobs.
Re: Show HN: I made a tool that made me faster at Git
#58Earlier quoted context omitted.
Which interface can do the above trivially with git?
I think the point was that git is missing an interface that makes these easy, and it badly needs one.
Re: Show HN: I made a tool that made me faster at Git
#59Earlier quoted context omitted.
this readme really speaks to me
I'm out of the loop. What's the story here? Why are devs sad about Atlassian and Jira?
Let me repeat that.
Your ticketing system is Turing-complete. I don't remember where I heard this first, but someone at my company (at least supposedly) proved it once.
Jira has managed to grow into such a bloated, complex, incredibly pointless piece of software that I've never met someone who likes it. It's like software design by committee, where every manager involved had some pet project that NEEDED to be included for some asinine reason.
Personal anecdote time: I had my interns start on Jira this summer. Three days in, I realized they weren't "getting" it because of how many damn buttons and knobs there are in the Jira UI. So, I switched all their issues to GitHub issues, and they went from having ~20 tickets in the project to over 100, and began adding, grooming, and closing their own without any input or direction from me. Sure, it's lackluster from an automation perspective, but they developed their own tagging system in the span of a few days and maintained their own board all summer.
I loved Atlassian for BitBucket in college, but when I entered the workforce and was forced to use Jira and Hipchat, I lost all love for them.
Re: Show HN: I made a tool that made me faster at Git
#60Earlier quoted context omitted.
I'm out of the loop. What's the story here? Why are devs sad about Atlassian and Jira?
Jira is Turing-complete. Let me repeat that. Your ticketing system is Turing-complete. I don't remember where I heard this first, but someone at my company (at least supposedly) proved it once. Jira has managed to grow into such a bloated, complex, incredibly pointless piece of software that I've never met someone who likes it. It's like software design by committee, where every manager involved had some pet project…