Viewing profile — Almad

That's from the good old days where truth mattered. Like how many action movies are about "getting the truth out" where that act in itself brings consequences, cut, happy ending? C…

From what I know, politologists are analyzing the situation in US from a perspective of "mid intensity civil war". So what you're writing is aligned with tactics you'd expect...?

So what are the sources for people driven insane by it? (I have no opinion, but find it mildly suspicious given that I happen to sometimes drive through Germany, and the country se…

> Gradle files (worst abomination of a build system ever) Ant? Maven?

Not always. You may also end up with having incompatible set of ciphers (happened to me). "Get off my Internet lawn if you can't be up to date" is what we're saying and I just do w…

Internet starts to have 1y memory retention. Unless refreshed by active learning, aka someone doing the refresh job. Or unless delegating the work to large players—either the memor…

I'd say quite the opposite. What you say is one of the myriad of considerations that should go into prioritization by the team, yet is super hard to capture by any hard attribute a…

One of the reasons I am delaying design is getting deeper into accessibility and readability research. And I have decided to write some content first ;)

If you mean how to prevent them, well, no bugs so no way to create them. If you mean how they handle them, there is an incident procedure for that. If it's not really an incident b…

In both companies I've been using that, it was a very simple RT/JIRA-SD-style system: "open a subject/text ticket, clock starts ticking, on call engineer gets a non-wake-up memo an…

True. I think one of the issues is slapping an issue tracking system on a bunch of different problems.

As mentioned, this is true for versioned software, not for continuously deployed SaaS.

Thanks, this made me think. My first knee-jerk reaction was something about things and implicitness, but after some consideration: * I am not sure "who reported the issue" is actua…

I completely agree and I hope I explicitly mentioned it in the article: it's not Jira, it's about how people/organizations often think about the problem.

"Season to taste" I totally agree with, no way to capture the whole world in a signel post ;) > I agree that ultimately (and quickly) the bug needs to land with a single person, bu…

> But that isn't correct. You can have a team pull from a single queue of tasks assigned to the team as a whole. There's no need to proactively assign them to individual team membe…

As the frontpage says, intentionally deferred :P

I actually never new about bugs being assigned to people as opposed to products, interesting to know.

I do agree it can totally suck to be on the receiving side.

Note: Author is Eastern Europian, so #totes

Fair, although, depends on scale again. As they say, at scale, every implementation detail is something customers rely on :)

Hmm, I communicated wrongly then. Because the separate system for issues is for a different team and a different purpose and no, it's definitely not a solution to the problem, but …