![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/c47230a8-134c-4dc9-89e8-75c6ea875d36.png)
It’s just as much a sport as figure skating or synchronised swimming.
It’s just as much a sport as figure skating or synchronised swimming.
Historically, the name came from Dave Nichol, who was president of the company for decades. He actually had a very strong hand in the selection of products that were included in the product line.
Apparently all kinds of people would pitch product ideas at him, and would taste test them and pick only ones he liked. The idea of “President’s Choice” wasn’t to be cheapo no name products, but unique and distinctive stuff personally picked by the company’s president.
And Dave wasn’t just some guy in the corner office. In his prime he was a Canadian personality, and you saw him in TV commercials. Once he left Loblaws in the '90s the President’s Choice stuff lost its panache and meaning.
Maybe that’s the design most compatible with the available hardware.
Often things like this are intended to be support for something else. Maybe there’s something nearby that’s hinged and can fold down on to it?
That’s nothing. I throw up a little in my mouth every time I see “cheque” misspelled, “check”.
Les Nessman comes to mind.
I’m not sure if traffic is “convenience” at this point. At least where I live, it’s a nearly essential piece of functionality.
In fact, for local driving it’s often the only reason to use a map app. I already know how to get to most of the places I want to go, I just need to know the best route to avoid traffic now.
You mean “flavour”, right? Another small but important difference.
Thank God somebody got it.
I think it’s a bit more than that. I think that the idea is that you simplify the problem so that the rubber duck could understand it. Or at least reformulate it in order to communicate it clearly.
It’s the simplification, reformulation or reorganisation that helps to get the breakthrough.
Just thinking out loud isn’t quite the same thing.
“Intercourse!”
In all honesty, I think that happiness comes from finding a bean you love and sticking with it. Experimentation has its place, but…
I’ve always heard of your “post-architecture” referred to as “evolutionary design”.
something manufactured of whole cloth and meant to divide us
I’m not so sure about that.
My parents grew up in London during WWII. My father told me that, on any given day, at least one or two of the kids in his school had recently received a letter from the government telling them that their father, uncle or brother had died in the war. Not to mention other deaths from bombings that happen on and off for years. For the most part, the rest of the kids in school never knew who had just had someone killed in the war, although I suppose it eventually came out to become public knowledge. The point being that you could be playing ball with some kid who had just lost a family member, and you wouldn’t necessarily know it. He said that this shaped his attitude that death is just a part of life, and something that (in true British fashion) you accepted and moved on with.
This came up when my sister-in-law lost her adult daughter some years back and she was (and is) still struggling with it. My father has a hard time understanding her feelings. The two of them are just 22 years apart in age.
WWII is something that casts a pretty big shadow. But when I was born, it was less than 20 years later and its influence on my attitudes is several orders of magnitude smaller than on my parents.
At the other end. It’s hard for anyone much less than 25 years old today to remember life before modern smart phones (if you assume the start of that as the iPhone in 2008). It’s hard to deny that the smart phone has radically changed the way that we interact with each other and the world. Yes, old farts like me have adapted to it, but young people today have these things hard-wired in from the beginning.
So far, in this century, it’s changing technology that casts the big shadow.
The point being that, while society changes in a continuum, big things that cast big shadows tend to define “eras” that shape the way that young people develop. And those big shadows are what cause “generations” to tend to clump together in attitudes and behaviours. And, no, I don’t think this is made up just to divide us.
What would be the point? They hadn’t even invented the electric kettle yet.
In a way, this question itself is very “un-agile”. Agile should be always forward-looking, “What can we do next?”, “What can we get done in this short period of time?”, “What should we do next?”.
OK, so you found a possible “defect” in your system. Is it a defect, or did someone slide in a requirements change 3 months ago?
This reminds me of playing chess. Sometimes a player will make their move when their opponent is distracted. The opponent hears, “Your turn”, and they look at the board. “Which piece did you move?”. The first player just shrugs.
The point is that you shouldn’t need to know which piece just moved. Every chess position is a “state” of its own, and your best move should depend on going forward from that state, not knowing how the board changed recently.
It’s the same thing here. You have a situation. Does it really matter how, when, who or why it happened? It shouldn’t, and here’s why:
Just because it’s a defect (if it is) doesn’t automatically mean that correcting it moves to the top of your “to do” list.
It’s going to take some non-zero amount of time to change it back to blue. And when you’re doing that, you’re not doing something else. There is always an opportunity cost to doing bug fixes and you shouldn’t treat them in an ad-hoc way. Should you be spending that time, and who gets to decide if you do? It’s not your decision. It’s the PO’s decision to make.
Maybe the PO doesn’t care about the colour. Maybe they do care, but not if it means some other feature gets delayed. Maybe it’s the most important aspect of the whole system, and there’s no way you can launch with it green. So you cancel the current Sprint and start a new one dedicated to fixing this defect! Maybe they regret asking for it to be blue, and now they’re happy that it’s now green.
If it was me, I’d get a quick T-shirt size estimate on the work required to change it back to blue, then put it in the Product Backlog to be reviewed with the PO. Maybe have a quick chat with the PO, or send a memo about it. Maybe the PO will need to check with their SME to see if anyone remembers asking for it to be changed to green. Maybe not. In any event, it either makes its way into a Sprint Backlog or it doesn’t.
Also, if you’re doing Agile right, then your clients are getting constant, hands-on, experience with your system as it is being developed. To go 100 days without some kind of “release” that they can play with and give you feedback is an anti-pattern. If you are giving them the latest version every week or two and after almost three months they haven’t noticed that the footer is green, then it’s probably not important.
On to the actual question. Jira is a potential sand trap of administrative complexity. The answer is usually to keep everything smaller. Smaller features, and smaller Sprints. Smaller teams. A team of 5 or 6, working in one week Sprints, can only do so much per Sprint. If your fundamental unit of work - a story, or a feature, or a ticket - is set to take something like 1/2 day and forms the basis of your Sprint Backlog, then each programmer on the team can do at most 10 SB items (in a perfect world). Depending on the composition of your teams, you’re probably going to have only about 3-4 programmers - which means 30-40 tickets per Sprint Backlog. And that’s a blue-sky number that’s practically impossible in a world with meetings. A team of 5 or 6 is going to complete closer to 20 Sprint Backlog items in 1 week Sprint in the real world.
The point being that 14 Sprints is your 100 days and each Sprint has about 20 easy-to-understand items in it. Whatever your management tools, it’s a failure if you can’t locate those 280 features in a matter of seconds. And it should be easy to eliminate 270 of them as not possible places where the change happened just from the description.
And when those SB items are small, as they should be, it’s not an onerous task to document inside them the requirements that they are supposed to meet.
When you have 1 month Sprints with tickets that take 2 weeks to complete, then everything becomes a nightmare. It becomes a nightmare because it’s virtually impossible to impose some kind of consistent organizational structure internally on free-form stuff that big. But it’s almost trivial to do it with tiny tickets.
And the other thing that happens with big tickets is that there’s tons of stuff that programmers do without thinking about it too much. If you’ve got two weeks to finish something, then there’s a ton of latitude to over-reach and the time estimate was just a wild guess anyways. If you have 3 hours to do something, then you’re going to make sure that what you need to do is clearly laid out - and then you have to stick to it or you won’t get done in time.
Did somebody “fix” the inconsistent footer colour while doing some huge, 2 week, ticket? Good luck finding out. But that’s not going to happen with tiny, well documented tickets.
Many, many years ago I used to have two Wyse50 terminals, running split screens each with two parts. I did a lot of support on remote systems (via modem!) and I would have a session on a customer system, source code and running on our test system and internal stuff. I didn’t have space for a third terminal.
At another job I had an office with a “U” shaped desk. I would spread printouts across half the “U” and swivel around between the computer and the printouts.
My first experience with this food was in Halifax decades ago. The Halifax Donair is a unique thing.
And it’s definitely Donair, not Doner.
I always thought of “Briton” in that last sense, while “Brit” has the meaning of anyone living in the UK (almost). But that’s from an outsider’s perspective.
As my English cousin corrected me, though, “I’m English, ‘British’ could be anything!”. She wasn’t, of course, talking about the difference between English and Welsh, or Scots.
It’s just a modern version of “Fuzzy Logic”