Does anyone here get to use Basecamp? It looks awesome and I’ve read up on their Shape Up process but have yet to find any organizational support for it in my professional experiences.
Why Jira Sucks
101–110 of 530 posts
Re: Why Jira Sucks
#102Can someone - anyone - recommend a better product (non-cloud)?
Phabricator.
Re: Why Jira Sucks
#103I am reading this comment thread and honestly I don't know that I agree. I think JIRA, like most tools, is as good or bad as you make it. I've been at numerous companies using JIRA that don't seem to have most of the issues referenced here. The only thing I've ever felt like JIRA really lacked in was in a good UX for embedding code snippets or other technical details into issue comments. Native support for Markdown i…
Jira Cloud has a new editor that is Markdownesque. Type as if you're using Markdown, and it will do the formatting you'd expect.
From your description, it sounds like this would have Slack's problem (which resulted in one of the most upvoted HN threads of all time, https://news.ycombinator.com/item?id=21589647). I've tried Googling around a bit to find an example of Jira Cloud's Markdown environment, but couldn't find one. (I am certainly biased, though, by my strong loathing of Jira.)
Re: Why Jira Sucks
#104I am reading this comment thread and honestly I don't know that I agree. I think JIRA, like most tools, is as good or bad as you make it. I've been at numerous companies using JIRA that don't seem to have most of the issues referenced here. The only thing I've ever felt like JIRA really lacked in was in a good UX for embedding code snippets or other technical details into issue comments. Native support for Markdown i…
> competing offerings.
Any suggestions for that similar synergy? Doc/Issue Tracker/Code base integration?
Re: Why Jira Sucks
#105I also have a low opinion of jira, but I don't agree with this list at all. I refuse to use jira because it is over-engineered and is generally used as a crowbar to foist non-technical influence upon technical teams, at least in the sites I've seen. Jira is in my opinion a fatal source of friction to the production of reasonable software. That's not what I'm getting from this list. Worse, almost all of the points (al…
Yup. Jira seems to be a tool around creating process. Management loves that shit because they believe if they put enough checkboxes and fields into a ticket eventually things will be good (or something). It drives me nuts to no end how stupidly complex people want to make the development process.
What should, IMO, have almost no interaction with the ticketing system, ends up being a chore for development which adds 0 value to the final product.
Re: Why Jira Sucks
#106What would you have us use instead? Trello?
If you have minimal needs, you could use a simple ticket system like the Erlang ticket system Joe Armstrong described in 2014:
https://joearms.github.io/published/2014-06-25-minimal-viabl...
In use from 1985 to 2014 and maybe longer.
Re: Why Jira Sucks
#107Earlier quoted context omitted.
I haven’t used any of those IDEs, but really, is Minecraft your example? A game with graphics so simple it should work on a Pentium 4 but requires a very beefy computer instead because it’s written in Java. They rewrote it (not sure if in C++ or C#) for the windows store and it works perfectly on computers that can barely run the Java version.
You might not be familiar with how modern computer graphics work. Objects and textures are loaded into the GPU and managed with an API like OpenGL and shader programs written in languages such as GLSL. Java, in this case, serves as the engine that ties everything together and runs the core game logic. Microsoft rewrote it because they're not a Java shop. Microsoft Games Studio not only uses C#, but their mission is t…
Java minecraft did have issues. Professional game streamers were having issues due to the pause-the-world garbage collection.
I don't mean to over hype the issue, minecraft became on of the most successful games in history riding on Java. But the re-write to C++ was not just because Microsoft is a C++ shop. The C++ rewrite delivered measurable performance gains, making it much better on low end devices especially.
Re: Why Jira Sucks
#108As others have said here, the main problem is just that it’s really slow. Apart from that, I think the only item on this list that really puts its finger on a key problem is #1, inability to manage dependencies between projects. You try to work around Jira’s problems by splitting the work into separate projects, but then they’re almost completely siloed, and Jira doesn’t help you connect them up. The other problem I…
Looks like the complexity is a consequence of its generality. Much like Word it serves so many different cases that many people end up using only subsets of features. Yet the code must support all possible cases.
Competitors too will likely drift into the same quagmire unless they're unashamedly opinionated.
Re: Why Jira Sucks
#109I am reading this comment thread and honestly I don't know that I agree. I think JIRA, like most tools, is as good or bad as you make it. I've been at numerous companies using JIRA that don't seem to have most of the issues referenced here. The only thing I've ever felt like JIRA really lacked in was in a good UX for embedding code snippets or other technical details into issue comments. Native support for Markdown i…
> competing offerings. Any suggestions for that similar synergy? Doc/Issue Tracker/Code base integration?
I use pivotal tracker. Not all the features of Atlassian, but I've completed several projects with it, and it doesn't get in the way.