Telemetry (if it’s truly telemetry) is nowhere close to “tracking”. People conflate the two all the time. One can provide useful, anonymous metrics (e.g. “user enabled feature X”) without doing anything but incrementing the counter for “feature X”.
The “Firefox Problem” is that all the power users disable telemetry, so all the “cool” features that power users like (but never get used by “regular people”) get ignored or removed instead of improved because, according to the metrics, “nobody uses them”.
The user doesn't conflate the two, the developers do, and that's why we turn off telemetry, because its damn close to tracking.
Knowing what (vulnerable) version of software a user is using transmitted in the clear was absolutely a part of the NSA monitoring error information from windows crash logs https://www.schneier.com/blog/archives/2017/08/nsa_collects_... - so forgive me if I do not trust the developer to know what makes me unsafe or not.
If you enable telemetry by default I will do my best to never use your product.
Right, but if all terminals behaved like modern pieces of software, we would take functionality like Warp's as given, instead of suggesting workarounds.
What you describe sorta works, but you lose things like file/dir-based autocomplete, since your editor doesn't know about your shell session.
Jira excels when there is a Jira governance committee comprised of people who actually understand data flow and are the only ones with admin privileges.
Too often some manager asks for (and is given) admin access and starts “improving” things.
Sure, anybody can create custom fields and screens and slap together a janky “workflow”, but well-oiled Jira Ops prevent an explosion of custom fields, they curate the create, browse and edit screens of each issue type to only show the fields that are important at that stage, use custom screens on workflow transitions along with validators and conditions to help ensure an issue is always in a reasonable state, etc. Then users don’t complain about the tooling.
But Jira governance takes time, effort, discussions with stakeholders, etc. And without it Jira gets a bad rap.
Jira excels when there is a Jira governance committee
True but oversimplified. Without a Jira administrative state, along with of course democratically elected Jira executive and legislature and a duly appointed Jira Supreme Court, Jira governance committees over time tend to slide into self-dealing, tyranny and eventually mass executions of anti-Jira resistance factions.
Sustaining Jira regime legitimacy over time is far more involved than simply a governance committee with its stakeholder discussions and five year plans for new custom fields.
Even when that happens, if you democratically elect a socialist governance committee you may suddenly find yourself liberated from your electoral duties by the USA
My current company has company managed boards, 6000 devs and we have about 250 custom fields. I work in a research team and we only need Kanban and I can't change the issue type if something is created. Hell.
I’m currently trialing https://tangrid.app/ and it’s got some nice features.
reply