Tootfinder

Titan submarine: Also in the same ntsb set of documents are a) The interview with the Softee who worked on some of the software, (describing Jira and Git to marine investigators..), and replugging the Logitech joystick dongle, and who had also got into screwing the end cap of the sub on and torquing the bolts up (!).
and b) The details of the recovery of the images off the camera - which turn out to be useless - but involved some fun with Luks, and a Qualcomm SoM.

Designers are always inventing new titles. Web designer, UI designer, UX designer, UX/UI designer, Product designer, UX/AI designer (???)
These are all the same!
As long as your work is mediated entirely by Figma and Jira, you are just a production artist.
Fighting with PMs over who "gets" to do strategy (usually: neither of you) won't help you. Lean into the core #design

Without UX governance, your app turns to "sludge"
Break out of the feature delivery mindset and attend to the architecture and maintenance of the product.

RAG4Tickets: AI-Powered Ticket Resolution via Retrieval-Augmented Generation on JIRA and GitHub Data
Mohammad Baqar
https://arxiv.org/abs/2510.08667 https://

RAG4Tickets: AI-Powered Ticket Resolution via Retrieval-Augmented Generation on JIRA and GitHub Data
Modern software teams frequently encounter delays in resolving recurring or related issues due to fragmented knowledge scattered across JIRA tickets, developer discussions, and GitHub pull requests (PRs). To address this challenge, we propose a Retrieval-Augmented Generation (RAG) framework that integrates Sentence-Transformers for semantic embeddings with FAISS-based vector search to deliver context-aware ticket resolution recommendations. The approach embeds historical JIRA tickets, user comm…

A recurring issue:
Source of Truth vs Point of Truth with many-system setups.
Imagine having separate
- issue tracking (e.g. JIRA)
- time tracking (e.g. Toggl)
- development tracking (e.g. GitLab)
- daily team sync (e.g. Confluence)
- weekly sync with stakeholders (...)
Without diligent manual labor or a lot of handcrafted automation, those keep getting out of sync.

Yes, of course we’re Agile. We have Jira!
Oh no sorry, sprints are enforced at 2 week length per corporate policy.
What’s that? No sorry, teams can’t modify task fields, you’d need to ask a Jira admin, but they don’t like to change things.
Swimlanes? Oh dear no, that’s the Jira admin as well. You see it’s important we have a strictly uniform implementation of our Agile workflow across the org.
(And they don’t even hear the irony themselves…)

En Australia han implementado el control de edad para acceder a servicios on-line. Desde hoy los menores de edad no pueden acceder a Jira ni a los servicios on-line del gobierno australiano.
JAJAJAJAJAJA

"Tree! Document <title> is wrong! Specifically this <valueX>! Who is the ignoramus who specified that value? ITS COMPLETELY WRONG WHO DO I GET TO LIGHT ON FIRE AND BLAME FOR EVERYTHING BEING WRONG?"
<checks Jira tickets that produced the latest document revision; goes back 3 document revisions over as many years>
You did. See here (2 yr old ticket): "pls change valueX from <blah> to <blah> because <rationale>. "
"…

Und, wie schnell seid Ihr bei der Umsetzung von als kritisch deklarierten Features? 😅🤦

"If George Boole is the 19th century’s AI scientist, then his contemporary machine learning engineers were Charles Babbage and Ada Lovelace. The Difference Engine, which would be frequently cited as the first example of a (mechanical) programmable digital computer if it had been built at the time, was explicitly designed to _replace_ rather than _augment_ human thought. Just as modern software engineering managers use Jira to avoid thinking about process engineering."

Douglas Hofstadter
You may be worried that I am going to talk about an author of books that are not about programming, and you are correct and incorrect. Correct, in that Hofstadter's books are not about programming (the intellectually hollow like to claim that they are not about anything at all, or that if you think you know what they are about then you did not understand them; this is untrue). Incorrect, in that Hofstadter's books and computer programs themselves are about the same thing.

Using GPT to build a Project Management assistant for Jira environments
Joel Garcia-Escribano, Arkaitz Carbajo, Mikel Ega\~na Aranguren, Unai Lopez-Novoa
https://arxiv.org/abs/2509.26014

Using GPT to build a Project Management assistant for Jira environments
In the domain of Project Management, the sheer volume of data is a challenge that project managers continually have to deal with. Effectively steering projects from inception to completion requires handling of diverse information streams, including timelines, budgetary considerations, and task dependencies. To navigate this data-driven landscape with precision and agility, project managers must rely on efficient and sophisticated tools. These tools have become essential, as they enable project …

“in an effort to streamline productivity we moved the button that is the raison d’être of Jira into a new location where it's really easy to _not_ see it”
Someone at Atlassian, probably.

Them: We need to add jira stories for the integration
Me, quietly to myself: "integration" is an anagram of "taint region"