this post was submitted on 16 May 2026
300 points (98.1% liked)
Programming
26943 readers
950 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Aw shit we use JIRA at work. Will it get worse now?
It... It can get worse?
Bruh, have you used Jira recently? We tried GitHub recently and that was so much bloat, especially hated by our devs.
Oh you sweet summer child. Have you seen Rational Team Concert?
Is that a boy punk group?
You're the other person that used RTC?! I had heard there was another but I was starting to think it was just a legend.
I migrated an entire codebase from a combo of RCS, CVS, and Subversion. This was about 10 minutes before git started to hit in a big way.
I'd call it a dumpster fire but that really disrespects dumpster fires.
You mean it was worse than Microsoft Source Safe? The VCS that used to lose data?
Source Safe just attempted to be a useless source control system. RTC tried to add issue tracking, automation, and other crap. It wanted to be truly terrible at everything.
But Source Safe was fantastically bad. I especially liked that its database file was limited to like 2GB. It was so bad that Microslop didn't use it.
It's the best I've ever used, so take that for what you will Action Remedy System was...something.
Although ive found that Jira and Confluence Cloud madr dozens and dozens of bad decisions and regressions over the oon-prem version.
we (team of 15) use salesforce and a promise to include issue numbers in our (svn) commit msgs all on one dev branch so when we cherry pick merge later to qa we can “safely” assume we got it all. 30% of the time it works 10% of the time.
i can’t convince these guys code is not “self documenting” let alone use git or a tool for proper bug reporting.
I had a boss who wrote a script to automatically remove all comments from code for pull requests. Since nobody ever added meaningful comments to their commits (or made any contributions at all to the alleged documentation), the code base was a complete mystery to the people who were actually working on it. God knows what it seemed like to new developers added to the project. But hey, comments are a "code smell" (his exact words) so it was all good.
His primary justification of his "comments bad" philosophy was that if comments aren't kept up-to-date with the code, they can mislead and confuse future developers. This gets said a lot but it is something that I have literally never seen in 25 years of programming (I've witnessed -- and participated in -- a large number of project failures, and misleading comments have never been the cause of the failure). I pointed out that the same exact thing could be said about method and variable names but nobody ever advocates not using descriptive method and variable names; he had no response to this.
kinda depends how you set it up and run it, no?
i have some simple new projects that are clean and easy, and some 10+ year old monstrosities that are the spawn of satan.
need to use ublock to stop the insane 'pls bro buy our ai' pop-up though.
I inject an entire set of CSS rules into Jira and into Confluence 🫠