111–120 of 287 posts
Earlier quoted context omitted.
I've wondered the same thing about Microsoft Teams. Is Teams as horrible as people say, or do they just hate it because it's what they happen to use for video meetings at work? Conversely, I don't hear much hate for zoom.
Having used Teams previously, I strongly suspect the latter. I didn't find anything about it to be particularly obnoxious.
I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.
I work in a mid-to-large org. The more agile part use tools like jira and slack. The older part (established in the 1920s) use Remedy and Teams. Jira is brilliant. It is team-led. Different teams have different approaches, some love all the features like components, versions, issue types, assignee, kanban boards, scrumms, reports etc etc. Others like my team use it with subject/description/comments. You make the tool…
I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.
> disdain for the specific tool vs. disdain for what working in a mid-to-large org You're kind of missing the problem here - it's both and neither. It's not the tool (it's awful) or the mid-to-large org itself, it's the concept that a tool as blunt as a ticketing system can meaningfully capture software development management in a useful way. If people just treated it as a "necessary evil" time-tracking type system t…
You’re conflating ticketing systems with work estimation.
That said, when it’s bad it’s because the company is trying to be too clever with it. If it’s used how Atlassian recommends, it works fine. If not, you have a lot of pain. I can’t blame Atlassian too much for their customers, either. The customer is always right.
I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.
When I clicked on the site the very first opinion called Jira shit because they had 20 different boards for the same thing, 2000 tickets in the backlog and 20 different mandatory fields for each ticket. Which is absolutely not the fault of Jira. Jira does not make you create 20 boards and per default a Title is all you need to create a Ticket. By the complaints own wording they had 2000 tickets because management ref…
Management didn't insist on that.
Earlier quoted context omitted.
It's the worst documentation tool, except all the others. Seriously though, what is better?
I’ve been pretty happy with Slab. Straightforward shared wiki with a good editor, governance, and integrations. https://slab.com/ I tried using README files in the repo but there’s far too much friction to get most folks to bother. Google Docs tend to disappear content due to a lack of structure.
I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.
Earlier quoted context omitted.
Having used Teams previously, I strongly suspect the latter. I didn't find anything about it to be particularly obnoxious.
It's slow, it's got a really poorly designed UI. It tries to do too much. It's not configurable enough, very low density