591–600 of 750 posts
Earlier quoted context omitted.
> I have never interacted with a piece of software that, for every single problem I found, there was an open issue always at least 4-7 years old You have never interacted with Jira?
I'm going to be honest with you, I never even considered that the pinnacle of enterprise software would have a public issue tracker (do they?). If something doesn't work the way I expect I just accept it and move on.
Earlier quoted context omitted.
I'm going to be honest with you, I never even considered that the pinnacle of enterprise software would have a public issue tracker (do they?). If something doesn't work the way I expect I just accept it and move on.
Jira bugs celebrate being old enough to drink.
"The Machine Stops" by Forster [0], anyone?
Honestly, I can't believe how repeatedly people ignore or don't know the warning signs put up by previous people.
Yes, it's science fiction, but so is 1984, Brave New World and Pump Six.
When will we go through something between 2001[1] and Tacoma[2]? Will we ever learn?
[0]: https://en.wikipedia.org/wiki/The_Machine_Stops
Gogs https://gogs.io/ (this IS gitea btw)
Forgejo https://forgejo.org/
Self hosted or cloud hosted. Also excluding Github because, please just fracking don't.
Earlier quoted context omitted.
You are imagining that the opposite of DEI is discrimination, whereas most see the opposite of DEI as merit.
The irony is that DEI promotes merit by forcing companies to justify hiring beyond basic “cultural fit” vibes. I’ve been in the business and seen a ton of hires on vibes. DEI actually asked people to expand the talent search, not hire anyone unqualified (which is what the anti-DEI folks are desperate to have us believe it did). I predict some major EEO lawsuits will eventually bring the pendulum back in the other dir…
Ive seen many cases where HR stalls hiring until the most qualified candidates move on, prefilter insufficiency "diverse" candidates from the pool presented to teams, or implement internal quotas to meet external funding or contract requirements.
Not to mention the actual external requirements for "diversity" from public tender process, government backed funding bodies, and politically protected mega wealthy.
GitLab could be the perfect case study on AI-powered efficiency improvements. I have never interacted with a piece of software that, for every single problem I found, there was an open issue always at least 4-7 years old that was just being shuffled around by managers adding and removing random labels. Surely with all of these ridiculous developer productivity gains enabled by AI, they should finally be able to fix a…
I once found a looooong bug report thread on their issue tracker 7ish years old that had all the usual waves of promises that a fix might make the next release, then silence, then repeat, and the usual challenges to the bug’s status every time a release happened, plus it saw community members correctly diagnose the problem in the first couple years, then by like year 5 there’s was a (small!) patch posted by a community member with multiple posters confirming it was good and fixed the issue, that the author and others had been begging Google to apply and get in a release for a couple years. There’d been no responses from Google folks for a while.
That might be the worst one I saw, but encountering something like that was a few-times-per-year thing in my android app dev years.
GitLab could be the perfect case study on AI-powered efficiency improvements. I have never interacted with a piece of software that, for every single problem I found, there was an open issue always at least 4-7 years old that was just being shuffled around by managers adding and removing random labels. Surely with all of these ridiculous developer productivity gains enabled by AI, they should finally be able to fix a…
The reason for this is: the only way to show productivity gains enabled by AI is to lay off people and pretend you are doing the same amount of work (while in reality you are severely dropping quality and accumulating technical debt).
Earlier quoted context omitted.
Self-host your git, take this as a sign. Forgejo is great.
There are a lot of downsides to self-hosting your git as well. Especially if you need to deal with high availability, scalability beyond a single server, and/or being open to the public Internet. I'm not saying you should never self-host your git server, but it's not for everyone.
GitLab could be the perfect case study on AI-powered efficiency improvements. I have never interacted with a piece of software that, for every single problem I found, there was an open issue always at least 4-7 years old that was just being shuffled around by managers adding and removing random labels. Surely with all of these ridiculous developer productivity gains enabled by AI, they should finally be able to fix a…
The reason for this is: the only way to show productivity gains enabled by AI is to lay off people and pretend you are doing the same amount of work (while in reality you are severely dropping quality and accumulating technical debt).
Productivity gains can also be achieved by reducing scope. The coming issues will be that because of increased productivity (idea -> working code) that software is too bloated, does too much, that product managers will and can say "yes" to everything. Until it becomes unmanageable.
And that's not a new problem, it's what basically every programming adage / wisdom going back 70 years is about.
Earlier quoted context omitted.
I'm going to be honest with you, I never even considered that the pinnacle of enterprise software would have a public issue tracker (do they?). If something doesn't work the way I expect I just accept it and move on.
Jira bugs celebrate being old enough to drink.