5 ms·
I'd short it technically because Confluence is Satan's wiki, but corps eat it up because WYSIWYG and because it costs money. (FOSS is bad, doncha know).
by unethical_ban 11y ago
I'd short it technically because Confluence is Satan's wiki, but corps eat it up because WYSIWYG and because it costs money. (FOSS is bad, doncha know).
- deleted 11y ago[deleted]
- icedchai 11y agoWhat do you think about Jira?
- Laaw 11y agoNot a huge fan of Confluence (just give me Markup, dammit), but Jira is simply the best at what it does.
- icedchai 11y agoPretty much all developers I know can't stand Jira. Management loves it though.
- Dirlewanger 11y agoYup, JIRA is a power-manager's wet dream. Whatever way one can think of for adding "things" to a task (and how to classify them, and how to keep track of them...), Atlassian has probably thought of it. For a developer who just wants to keep the tool at a distance and only log into it to move their shit across the scrum board and promptly log back out, they better hope their scrum overlords have looked upon them kindly.
- cowmix 11y agoAlmost every time my company gets called in to do JIRA consulting the situation is this: Devs bring JIRA in.. JIRA gets popular.. things get out of control. It is almost NEVER brought in by management.
- alkonaut 11y agoIn my opinion it's a range of management requests that give rise to the workflow, and devs hate managing workflows with email, notes ("When you are done implementing move the issue to the X column and send a message to the testers group that..."). So then devs bring in JIRA to do some automation. Now the tester person gets an email when the issue is moved to the testing phase. But once everything is in place, management will see the benefits, and the workflow will "evolve", especially if the teams grow. It's pretty natural.
- icehawk219 11y agoI used to be a dev who brought in JIRA because I like it out-of-the-box and it can grow with a team. But I always tell my manager to NOT TOUCH THE WORKFLOWS and to just let things grow organically as the needs of the team grow (or don't). And every time the moment they click around and see the workflow editor we ended up with some big, bloated, convoluted mess. I've been burned too many times, I no longer recommend JIRA to anyone.
- daigoba66 11y agoThe trick is that Jira should be "owned" by the dev teams, not by management. Management shouldn't even have a login, except perhaps to submit bugs. The only exception is if Jira is used for project management type stuff - those projects can and should be isolated from dev projects.
- Laaw 11y agoJira is a super flexible tool. Sounds like all the developers you know hate how their bosses use tools. I happen to love how my team uses Jira.
- LukeB_UK 11y agoI love Jira. You just have to have it set up for the people using it every day (developers)
- serge2k 11y agoAs a dev, Jira is the best of a bad lot.
- colinyoung 11y agoI'm one of these. PivotalTracker is the only thing I don't hate.
- mlindner 11y agoI hate Jira completely. It is terrible. Best system I've seen is Pivotal Tracker.
- mdolon 11y agoI used to be a Pivotal guy before looking into JIRA again recently. They've made a lot of changes to their platform that really make it a pleasure to use, at least for my needs (development work with small teams). There is a bit of setup work but once you do that, it's smooth sailing.
- jacques_chester 11y agoPivotal Tracker is deliberately minimalist. I didn't really get it until I started working at Pivotal Labs.
- caoilte 11y agoJira 3 was an okay issue tracker. Jira 4 is a SLOOOW issue and a terrible agile planning tool. Much happier with Trello and a zero bug policy.
- Laaw 11y ago> zero bug policy. Oh, why hadn't I thought of that...
- acidburnNSA 11y agoI started using FOSS Phabricator on a medium-sized team (~20) for private central git hosting, code review, issue tracking, project management, etc. We absolutely love it and I wonder how it compares to Confluence/JIRA.
- rdtsc 11y agoNot OP. Unlike Github's mostly developer centric issue mechanism, Jira is more suited for organizations the would have a QA department, a security review, a more complicated release process (multiple phases of validation and testing) or that that just need a custom issue state machine. It just so happens that those companies also have money to buy Jira licenses and Atlassian is brilliant for letting OSS project use it as well. So they get a foot in the door at multiple places in the industry. If startup developers don't like it, oh well, there is enough money for them to be made in the Enterprise market. (Also, I noticed that there is an interesting plugin market for it as well, once you have audience that paid so much to use it, they'll be willing to shell out a a few hundred more for say Slack integration or other such plugins).
- Zigurd 11y agoJira can do anything. Up to you if that's a bug or a feature. The interesting thing is that it is very often used for Agile project management. It's massive overkill for that. It has the feel of something that evolved from an issue-tracking system, because it existed before Agile and morphed into an Agile tool.
- cowmix 11y agoThat's not why corps eat up Confluence. My day job is Atlassian crap and I move people off of other OSS wikis into Confluence all the time. Corps just run into roadblocks with OSS wikis.
- evgen 11y agoLike what? As someone maintaining a Confluence wiki among other tasks I can say the only thing I has provided is reasonably fine-grained access control and a huge ton of headaches, pure WTF moments of XML hell, and java crash stack traces to debug. Confluence is the Wordpress of wikis, but without Wordpress's code quality</s>
- Karunamon 11y agoOnly time I've ever run into XML hell on Confluence is when dealing with imported pages. Their automated import tool is neat, but it leaves you with some cleanup to do since not all of the markup from $wikiPackage transfers cleanly to Confluence macros. Combine this with the fact that there's no error handler for broken pages - if the XML that makes a page work is invalid on the back end, the page just straight up won't render and has to be fixed another way. (Which sucks, but as I said, this is not a thing most people will ever encounter). It's not possible to generate invalid XML using the WYSIWYG editor, but plenty possible if you're using either the code editor, or plugins that do strange things. The logs are chatty as hell and you'll generally get stack traces for even completely benign problems/notices. That's one thing I wish they'd deal with, but it's pretty minor. If you're getting error-level stack traces and XML nonsense on a daily basis, something is terribly wrong in your instance. That is simply not standard behavior, and I'm kind of curious what their support people are telling you. (Shoot me an email if you're comfortable doing so - I may be able to help you out)
- devonkim 11y agoYou want this alphabetically for why most corps won't deploy OSS wikis that are stamped for approval by the HN crowd? 1. LDAP support 2. SAML / SSO support 3. RBACLs 4. Auditability that integrates with some Big Corp compliance system (I'm thinking SOX primarily here and why some companies can't use Git for systems that require full auditability just because Git rebase and wipe of the reflog can happen) 5. The fact it's Java-based rather than oh... Erlang or Python is a pro to most enterprises that have hordes of people that have known only Java tooling and languages. Training a bunch of people that are not motivated to learn anything new is insanely hard. PHP could substitute in here as well I suppose. 6. Other software suites that integrate tightly with it. JIRA sucks for a lot of people, too, but it sure beats all the other crap I've had to use at work. I think less than 20% of the people on HN have actually had to use HP Quality Center or Rational ClearQuest on a daily basis for a long time. 7. Vendor is software maintainer. Big Corps would rather work with a single vendor if possible rather than some small consulting companies that install and integrate the software tailored for their environment and then leave pretty much. So unless one of the primary maintainers of I dunno, Redmine, started offering support contracts with a team of professional services folks, there's hardly any actual competitors to the Atlassian suite in the enterprise "more money and not much technical know-how to spend it effectively" software market. 8. A sales team that you can choke to bend to your will with money. Most OSS projects will not take terrible, horrible, ugly feature requests for large sums of money from a single user that are technically bad and tough to support without massive costs - this is how a lot of enterprise software vendors do business and part of how they decline over time (too many one-off feature requests for big ticket customers that create conflicting design requirements to engineer around combined with a shift to sales culture over engineering / innovation culture leading to massive loss of technical talent). Edit for newlines
- gregmac 11y agoI actually really like Confluence specifically because it's WYSIWYG -- not for myself, but because by being accessible, other (non-developer/technical) people actually use it. I hate having to deal with the mess that is every shared network drive at every company ever, or even worse, email attachments. Personally, I'd be happy with just Markdown if it was just a group of devs, but that is a rarity. At my company now, we have tech support, IT, (non-technical) account reps and even to some extent HR and finance using it, and to get that to happen, it was essential to be very easy. There's still a handful of users that attach Word or PDF documents to a page, but at least it's accepted that the wiki is still the canonical location to get any type of documentation, company policy/forms, etc. Baby steps. So well Confluence does have its warts, getting buy-in into non-technical departments trumps those. Conversely, I've never seen a non-WYSIWYG wiki actually successfully deployed and used by non-technical users (as contributors) -- anyone else?
- unethical_ban 11y agoWell, the wiki my team needs is one that is used by tech-people only. IT security team. We had Dokuwiki, which worked alright (except inline images were a bit tedious). Confluence is just tacky, too much whitespace, whizzywig editor is slow and buggy (less so than 2yr ago). And the old fogeys on the team that hate documentation still write their notes in a notes.txt file on our team share. Having a "beginner friendly" wiki didn't help anything. Oh, and our dokuwiki was HA on day one, with backup scripts zipping and SCPing a backup to an offsite server. Confluence took MONTHS to get HA as an enterprise solution.
- s_henry_paulson 11y agoHaving inline images be easy was the first thing that sold me on Confluence. I mean you're already doing documentation, adding tedious tasks to it just makes it worse. Ctrl+C, Ctrl+V, done. Your "old fogeys" thing is a managerial/personnel problem, it has nothing to do with the software. And this is the first time that I've heard "too much whitespace" be a complaint. You want to be distracted from the content?
- jobu 11y agoIn my experience, Confluence sucks a lot less than SharePoint. The unfortunate thing with any Wiki or document sharing tool is they tend to become cesspools of outdated or contradictory information. It has to be someone's job responsibility to keep it updated and curated.
- unethical_ban 11y ago1) Something isn't a wiki because it's called such. Sharepoint is not a Wiki. It's a server of some kind that can sometimes hold data that users put on it. I didn't even classify it as a wiki in my "what's crappy" list. 2) Agreed on the maintenance part. There needs to be a yearly audit/testing of procedures to make sure the docs hold up to new versions of software, new releases, etc.
- frik 11y agoSharepoint is many things, it has a basic Wiki system included.
- IshKebab 11y agoIncorrect. Sharepoint is Satan's wiki. Confluence is amazing in comparison (and it's not too bad in absolute terms to be honest).
- rickette 11y agoThis a 100 times. I'd wish more companies would dump Sharepoint and just use Confluence.
- Sophistifunk 11y agoWent through the exact opposite of this while at ${CAR_COMPANY.jp} last year (CF->SP). Even a poorly-run Confluence is Shangri-La compared to the abomination that is Sharepoint.
- mschuster91 11y agoBe happy you never had to work with Lotus Notes. Only if you have mastered it you may complain about anything else ;)
- krupan 11y agoSharepoint cannot even be referred to as a wiki (at least what I've seen, it's an MSOffice document store with some clumsy shared-edting kludged on). Confluence used to have regular wiki syntax plus WYSIWYG for non-geeks, but the non-WYSIWYG appears to have been killed off completly. It's till a wiki, but barely.
- jason_s 11y agoYou can use either Atlassian markup or Markdown to edit Confluence pages, it just takes a few extra keystrokes and I can't remember how to do it right at the moment. Not a piece of cake like Github/Stackoverflow, but at least it's possible.
- provemewrong 11y agoSharepoint does have "wiki pages" feature among other things, but I agree that its usual use case is shared document storage.
- andygcook 11y agoThought I'd hop in here for everyone who isn't satisfied with Confluence (or think it's the preferred publishing method of the devil). My startup's building wiki software that's targeted at small groups to start who want a team wiki (instead of having to post everything to the entire corporation). The idea is to really focus on making the publishing and discussion experiences delightful. I'd love to chat with anyone who is thinking about setting up a wiki for their startup or team My email is andy@tettra.co and the site is http://tettra.co http://tettra.co.
- Karunamon 11y agoThe thing with Atlassian's whole stack, I've found after nearly 5 years administering them, is that how the users perceive it depends entirely on how it's run. That applies to nearly everything they make, Jira, Confluence, the whole lot. It's possible, and very very easy, to set up a shitty Confluence wiki, and some of the details of its performance are not exactly obvious. It takes a bit more work to set up one that's both well liked and easy to use. If I had it to do over again, I'd still pick Confluence over MediaWiki every day of the week and twice on Sunday. Life's too short to deal with wiki markup by hand.
- mlindner 11y agoYeah I'm also considering shorting this as well. Having worked at a company that ate Atlassian software day and night, every single piece of software they have in their portfolio is a complete ugly mess. For every piece of software they have there's a better alternative that is cheap or free.
- dbattaglia 11y agoI think it's pretty subjective. JIRA can turn into a nightmare once overzealous project managers get their hands on the workflow designer. But I really miss Bamboo, having since moved to a company using Jenkins now. And Stash's web UI is pretty nice for doing pull requests/code reviews.
- jarek 11y agoHave you ever seen an enterprise software company do badly because its software was an ugly mess and alternatives were cheap or free?
- katbyte 11y agoCould you list the cheap and or free alternatives?
- mschuster91 11y agoWell, for wikis it's obviously MediaWiki, and Bugzilla for JIRA. Only thing that I don't know of free software replacement is the Agile Development tooling that JIRA provides. But tbh, "agile development" is a hellhole of buzzwords, expensive consultants and ridiculous bullshit rules anyway.
- rubidium 11y agoOr, you know, something a fortune 200 company uses to set its release dates for its flagship software. And is able to communicate how scope creep would affect sales to their internal team. And hits that release date.