Almad

7 ms·

1.
by Almad 8mo ago
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? Compare with now: revolution may be televised,
2.
by Almad 8mo ago
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...?
3.
by Almad 1y ago
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 seems to be currently less insane than, say, US)
4.
by Almad 6y ago
> Gradle files (worst abomination of a build system ever) Ant? Maven?
5.
On Uneducated Hiring(almad.blog)
1 points by Almad 6y ago|0 comments
6.
by Almad 6y ago
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 wonder whether we haven't exchanged
7.
by Almad 6y ago
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 memory or the hosting. EDIT: This feels wrong, even when done for
8.
Continuous Delivery Is a Risk Management Strategy(almad.blog)
1 points by Almad 6y ago|0 comments
9.
by Almad 6y ago
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 as I believe the "positive/negative mental h
10.
by Almad 6y ago
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 ;)
11.
by Almad 6y ago
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 but, well, I need this next week for Gartner Magic Quadr
12.
by Almad 6y ago
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 and will reply with high priority during w
13.
by Almad 6y ago
True. I think one of the issues is slapping an issue tracking system on a bunch of different problems.
14.
by Almad 6y ago
As mentioned, this is true for versioned software, not for continuously deployed SaaS.
15.
by Almad 6y ago
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 actually important, but rather "who is the contact
16.
by Almad 6y ago
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.
17.
by Almad 6y ago
"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, but the component matters in the routing step bef
18.
by Almad 6y ago
> 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 members. Agreed. My point was more about that there
19.
by Almad 6y ago
As the frontpage says, intentionally deferred :P
20.
by Almad 6y ago
I actually never new about bugs being assigned to people as opposed to products, interesting to know.
21.
by Almad 6y ago
I do agree it can totally suck to be on the receiving side.
22.
by Almad 6y ago
Note: Author is Eastern Europian, so #totes
23.
by Almad 6y ago
Fair, although, depends on scale again. As they say, at scale, every implementation detail is something customers rely on :)
24.
by Almad 6y ago
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 rather a prerequisite for the outlined system to have
25.
by Almad 6y ago
The main problem I had with them is inability to sort them in a list, which is somewhat solvable with GH Projects now.
26.
by Almad 6y ago
In my experience, the final sorting needs to be done by a collaboration between ticket manager and someone-who-understands-technology anyway. If the ticket manager doesn't have a clue, they can't make judgement calls necessary as
27.
by Almad 6y ago
Happy to, glad you like it
28.
by Almad 6y ago
I'd agree with you if I would be only seeing the teams through my management reports and not from the trenches. I am envious of the environment where you never saw somebody trying to bug feature request as a bug. I do think in a lot of
29.
by Almad 6y ago
Thanks! Yeah, this is something worth a separate article (this one felt long already): ticket systems as reporting tools.
30.
by Almad 6y ago
I do agree completely on "failed promise" and this is actually why I think the bug vs feature is flawed. I think "failed promise" is a great ticket type though ;) There are obvious cases where I have nothing against what

More ›