Jira is a customizable ticketing platform. I manage a different ticketing platform at my company (ServiceNow), and I see a lot of crossover in system complaints.
People ask for a tightly controlled workflow and then get mad when they can't freely move between states. There will always be exception cases so don't lock down your states in Jira unless it's for some audit reason.
Too many custom mandatory fields to enforce some sort of process compliance. If you have a process you want people to follow, do your job and educate and have recurring trainings on the damn process. The system can't do the educating for you, and if everything is locked down and mandatory all the time it means the ticket can't even be worked on in phases, or the requester responded to quickly, without having to spend five minutes on data entry - for every ticket.
People try to use a particular ticket type for something it's not meant to be used for and get mad when it doesn't work. This seems to be less of a concern on Jira than ServiceNow but use the correct ticket types for what you're doing and you won't have a problem.
People hate the underlying processes put in place, and blame the system. This is what the article is addressing.
I do have to agree with this article as a whole. There are a lot of managers who see what Jira can do and expect employees to do it all without considering whether it will be worthwhile. Especially if you're not running agile and sprints, Jira isn't the tool for everyone. Most companies have a Microsoft 365 license and Planner works well for team task tracking in general (and it's integrated with Teams).
At the same time, some employees just hate the idea of ticketing at all and rage against the idea of being held accountable for their tasks, and sucks to be them I guess.
Someone else in the thread linked this article which has just come out as well and seems to be a summary of an ex-employee's accusations of terrible working conditions on Twitter. (I can't see the Twitter thread because of no account so I can't link to a primary source, sorry.)
I'd say Kirk being here for multiple episodes was necessary to resolve La'an's growth as a person. Whether it needed to be Kirk himself, obviously not, but since they started that thread they had to complete it. I do hope he doesn't just continue hanging around next season, though. He has a post on the Farragut to attend to.
I agree. As a fellow musical lover (I'm posting from the intermission of a touring Broadway show) the writers clearly understand what the music in musicals is meant to represent. La'an's and Uhura's solo numbers definitely gave some emotional insight into both characters that I feel benefited the show beyond just being decent musical numbers.
The autotune was painful in a few moments for certain actors but hey, they're not professional singers, and I would have loved a bigger dance number, but I know that's pushing it.
The company my workplace partners with for our IT Helpbot has given a lot of insight into how their LLM system works, and the big thing about it is the langchain and the checks and balances.
Like, you ask "how fix printer error" and instead of hallucinating a response, it first queries our help articles for the correct information and finds the correct snippet to include, along with a link to the source. It also checks whether the user has access to that source material, and if not then it won't return it but it will proactively tell the user that and ask whether the user wants to open a help request for access to that info. (We haven't implemented a lot of this stuff in our own workplace because it requires so many coordinating integrations - this is a best case scenario.)
Then, before sending, a second AI comes in and double-checks whether the response is going to be truthful and factual and non-toxic, or else the response has to be regenerated.
This stuff is incredibly powerful but it's not as simple as "train an LLM and release it on the world" - you need to really think through it as one tool in your toolbox, and how it will interact with those other tools. The only people it's good at replacing, at least in it's current state, is L1 Help Desk who only read and respond from SOPs. Otherwise, Copilots can be a good way to assist in coding for example (ChatGPT has given me great insight into my PHP errors for example) but it certainly can't do the actual work for you.
I wouldn't say the hype is dangerous or overblown, because this stuff can be absolutely transformative if applied correctly, but executives see dollar signs and think they can replace real thinking humans and then they suffer the consequences, because they didn't understand the very initiative they directed.
ActivityPub has actors and activities. These are very broadly defined - yes, a user is an actor, but so is a magazine in kbin. A like, a thread, and a microblog are all activities. These come from an actor, and they are sent to and cc'd to other actors in the fediverse.
NNTP, however, is not actor to actor, it's server to server, to my understanding.
In practice, the way this is implemented here, it's not that much of a practical difference, but it's interesting to know.
The other difference is that NNTP servers would forward messages to their other known NNTP servers, essentially creating a distributed network of information. Per the ActivityPub protocol however, no instance is obligated to do that on ActivityPub. The only obligation for forwarding is if a) The values of to, cc, and/or audience contain a Collection owned by the server (e.g. followers is a Collection) AND The values of inReplyTo, object, target and/or tag are objects owned by the server. So basically if I receive something from lemmy.world user actor, to lemmy.world community actor... Even if kbin.social hasn't received it and errored out, I have no obligation as the.coolest.zone to send it out to them.
But more seriously... While I'm struggling to come up with concrete examples right now, I learned a lot of trivia, read some really interesting anecdotes, and broaded some of my knowledge via Reddit. For all of Reddit's many (many) faults, the people who were willing to take the time to converse and share knowledge were never the problem. They were the reason I stuck around for so long.
I still use nav buttons. I really liked apps that had that left slide out drawer (something Google pushed for a while and then quietly abandoned) and I kept navigating elsewhere while trying to pull out the menu drawers, so I went to buttons.
My final cool app with a drawer, rif is fun, is no longer on my phone, so I guess I can switch to navigation gestures... But it would take a lot of getting used to and "what gesture goes where?" (Note that I am particularly bad at remembering this sort of stuff - I'm the type of person who keeps a screenshot of a keybinding map on my second monitor while playing games.)
"Promise to shareholders" outweighs "promise to environment" and that's why we were being cooked alive this summer.
There's no actual incentive for a company to do the right thing if the wrong thing gives them more money, and I realize this is such a simple notion that everyone's gonna say "well duh", but I am just going to keep repeating it because we desperately need some sort of regulations around this sort of shit.
Rejection sensitive dysphoria (RSD) is extreme emotional sensitivity and pain triggered by the perception that a person has been rejected or criticized by important people in their life. It may also be triggered by a sense of falling short—failing to meet their own high standards or others’ expectations.
When this emotional response is externalized, it looks like an impressive, instantaneous rage at the person or situation responsible for causing the pain.
The first medication mentioned as a possible treatment, guanfacine, changed my life to such a degree I did not think was possible.
I encourage you to read through the entire article and maybe discuss with your doctor on possible treatments if this sounds like what you experience.
The problem is that there are a million logos from the 90s that have the same stylized "separate head". I'm attempting to attach an image to show off some examples. While I absolutely feel like I recognize the logo you've posted, I think it could be an amalgamation of many of them.
To add to this very good point, it also fosters a sense of community. Nothing brings people together like hating a CEO. And hey, if you feel like part of a community, you're less likely to leave.
At my old job we had a system of first initial + last name, or if that was already taken then the first two characters of first name + last name, etc. A ticket came into us from an Lo[...] Li who had some concerns about being loli@bignamecompany.com. We obviously gave him an alias.
Tablet flip phones are huge and I have tiny hands and tiny pockets. I want a tiny phone which I can check the time and basic notifications on, and unfold to a regular sized phone when I actually need to reply to something.
ryan @ ryan @the.coolest.zone Posts 1Comments 211Joined 2 yr. ago 
Jira is a customizable ticketing platform. I manage a different ticketing platform at my company (ServiceNow), and I see a lot of crossover in system complaints.
I do have to agree with this article as a whole. There are a lot of managers who see what Jira can do and expect employees to do it all without considering whether it will be worthwhile. Especially if you're not running agile and sprints, Jira isn't the tool for everyone. Most companies have a Microsoft 365 license and Planner works well for team task tracking in general (and it's integrated with Teams).
At the same time, some employees just hate the idea of ticketing at all and rage against the idea of being held accountable for their tasks, and sucks to be them I guess.