Live data from Hacker News

Jira Is Turing-Complete

seriot.ch

151–160 of 160 posts

Re: Jira Is Turing-Complete

#151
post #49

in before every project manager on planet earth makes a "guess we don't need you devs anymore haha" joke during morning standup

...why would we want to do your job?

No you fool, don't you see? Now you're all going to going to be forced to learn how to code...in Project Manager BWA HA HA HA HA!

Re: Jira Is Turing-Complete

#154
I'm going to sound like a lunatic, but the best bug tracking software I've ever used was Apple's Radar internally. I wish they'd open source it. I've also had a bunch of fever dreams about re-implementing it as a product.

Re: Jira Is Turing-Complete

#155

Earlier quoted context omitted.

The non-existence or non-availability of recursive features, like an issue being parent of an issue, or in Slack a thread being started inside a thread and so on, to me usually indicates, that the developers of the tool are afraid of recursion, and have never learned how to implement this easily in a database, used a programming language that easily deals with recursion, and don't know how to deal with it in other la…

Alternatively, it is a conscious decision to help prevent users from causing complicated situations. Given a highly configurable system, users will find ways to (unintentionally) tie it into knots, so adding some guardrails can help reduce complexity demons down the line (both in the technical implementation and the user experience). I guess I prefer to give people making things the benefit of the doubt.

> Alternatively, it is a conscious decision to help prevent users from causing complicated situations.

Based on the rest of Jira, it's definitely not that!

Re: Jira Is Turing-Complete

#156
post #78

Earlier quoted context omitted.

> The engineer is not the target user yes, but: 1. not anymore 2. That's the price you have to pay if you want the tool you like to have corporate buy-in

> That's the price you have to pay if you want the tool you like to have corporate buy-in So to get buy in to the tool you like, first you need to make it into a tool you don’t like? Why would you go after buy in to that tool?

The world does not revolve around you

Re: Jira Is Turing-Complete

#157

Earlier quoted context omitted.

Linear. By far and away, linear. The task tracking features you actually use, it’s fast, you don’t waste a billion years playing “who knows how to do this and has the permissions hell” that you would with Jira. The integrations work properly. The layout and UX makes sense, and all the nontechnical people I’ve used it with liked it and had no issues with it.

What's so special about Linear? I tried it, it's the same crap but bit faster (for now).

One thing was apparent immediately: The UX is thought by Humans, for Humans.

Not whatever abomination Atlassian targets.

Re: Jira Is Turing-Complete

#158
post #157

Earlier quoted context omitted.

What's so special about Linear? I tried it, it's the same crap but bit faster (for now).

One thing was apparent immediately: The UX is thought by Humans, for Humans. Not whatever abomination Atlassian targets.

Where exactly? I see the same fields galore, like in Jira.

Re: Jira Is Turing-Complete

#159
post #29

I think at least 60% companies that use Jira could do better with just Trello. I dont know how it is possible to create such a horrible mess with task manager and some reports. But it probably keeps the managers and POs bussy so :D

I'm sure Atlassian knows this as well. When you setup a basic Kanban board in Jira, it is basically a Trello board. It is offered as one of the default options. I was actually surprised they offered such simple options. Of course the complexity is there, the moment you start wanting an extra column, you're in the rabbit hole.

Yes but it never ends there. Jira mess grows with middle managers trying to suck some kind of reports out of tasks. And trying to manage everything in it. 20 ticket states, 15 bug types and using epics for wrong reasons, every board setup differently. Moving between teams is hell. It is intergalactic spaceship when all you need to is go to have a smooth car ride.

Re: Jira Is Turing-Complete

#160

Earlier quoted context omitted.

I can see very naive points here: * "Corporate hackers" is a... not a very common thing. In the corporate world most programmers do what they are told to do and nothing more. Initiative is punishable. * API wrappers aren't actually good. Not to mention that the API itself is very poor. JIRA has a tradition of arbitrary changing things, especially removing things, or not exposing the useful functionality. It's not a w…

I've worked for a few Fortune 50 companies, and they all had "shadow IT" that would crank out scripts and tools with no official sanction to work around the cumbersomeness of the official tools (or sometimes their complete lack). That's what corporate hackers are.

Well, where I work, "automation" is part of my job title. And if I ever even suggest that I've done some work outside of the tasks assigned to me that has something to do with my job, I'd be sent into disciplinary hearing. Any work I do for the company must be sanctioned by my boss, otherwise it's treated as dereliction of duty (under the pretext, that I should've been using that time to work on my tasks given me by my boss, or, if I had no such tasks, I should've informed my boss about the situation).

And, in my specific case, my boss is not very good at programming, and doesn't like anything I do on that count. So, anything I've done so far was mired in pointless PR reviews and discussions, stalled for many months or simply never made it after more than a year of PRs waiting. Ironically, my boss had to order the cancellation of some CI tests because he didn't accept my PR fixing those tests. And it's been like that for something like three years now.

I wish this situation was exceptional, but it happened more than once, and, by far, I'm not the only one experiencing this. That's what I mean by "initiative is punishable."

Post reply on HN