My question is how much “likely” translates to “voted”. It seems easy to respond, “Yes”, when asked on the phone, but requires a bit more enthusiasm to actually go stand in line and cast a vote.

I wonder how depressed Giorgio Tsoukalos’s dog is???

Agreed, but I don’t know the mindset of those people and how to think of them. Do we just take them out of the voter pool? Are they potentially swing?

My take on 2016 was that the Dems were deeply unenthusiastic about Hillary - and who can blame them - so they didn’t show up to vote. On the other hand the Reps were stoked about Trump so they turned up at the polls.

Swing voters? I don’t get it. I cannot see any rational person sitting in the middle comparing Trump and Harris and picking Trump as a better presidential option. Irrational people? My gut tells me they they are probably sitting and the far ends of either camp.

My guess is that the people closer to the middle aren’t actually swing voters, but they are far more likely to have their enthusiasm to vote influenced than the true believers.

The big question, in my opinion, is how much - or how little - the polls reflect the enthusiasm to go out and vote. My impression is that Dem enthusiasm in high right now, while not so much for the Reps. It’s possible that a 50/50 poll may hide the fact that a big chunk of one of the 50% is much less likely to actually vote.

I’m Canadian, so I see the news but I don’t have day to day experience with US voters. Of course, neither do the 90% of Americans that don’t live in those swing states.

Isn’t that true about all US elections? There are no “undecided” voters, just Dems and Reps and the result is always based on who can motivate their voters the most.

The travel eSIMs are a bit different. My Orange plan covers Turkey and the UK, which I specifically wanted, and probably Switzerland as well. For my wife, I needed to get a “world” plan that covered Turkey, otherwise the Europe plan would have covered the UK.

But that’s an important point. The travel plans are NOT the same as regular plans in some ways.

I would have a couple years ago. In a flash. We replaced our phones a while back specifically to have eSIMs. It truth, considering the cost of Canadian roaming plans the phones have already paid for themselves.

Both of our old phones were single SIM, so using a local SIM would mean disconnecting our Canadian numbers which would put us out of touch with people back home. Which means that this card wouldn’t have work for us either.

I was at the point of looking at buying a portable WiFi hot-spot, when I found out about eSIMs. So we went that route.

I have an Orange eSIM with a France number that I have kept alive by reactivating it at least once every 6 months. It’s good for all Europe, without roaming charges, so that’s easy to do. Having the same number all the time is convenient, but more importantly I have gone through the hassle of providing passport info to Orange, which is a government requirement if you want a number for more than a couple of weeks. I think that’s an EU thing.

The local number is good for calling hotels and for making restaurant reservations. Just having that is a game changer.

For my wife’s we don’t need a number, so I just use Nomad for her data only eSIM, and get a new one each time. The cost is about $12-15, and you get whatever carrier you get, but the service has been good so far no I keep using Nomad.

We can text each other using WhatsApp, and you can even use WhatsApp for voice calls. The sound quality is acceptable.

We bought phones that support eSIM because we do a lot of travelling. Canadian mobile companies charge usurious rates for roaming: $15/day! Times two phones. I can get 2 weeks of data only for Europe for about $11 total on an eSIM. With voice it goes up to about $25. Total.

It has changed our lives when we travel.

It’s just as much a sport as figure skating or synchronised swimming.

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.

Why not? He’s an amazing speaker and he comes across as extremely thoughtful and intelligent.

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.

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.

Technically, he would have three drives and only two drives of data. So he could move 1/3 of the data off each of the two drives onto the third and then start off with RAID 5 across the remaining 1/3 of each drive.

Deal with the ethernet port issue by purchasing a 5 port ethernet switch. Maybe the rest of your issues go away?

Yes, $15 CAD/day to “roam like home”. I have an Orange eSIM that I can keep alive if I use it at least once every 6 months - with a local french number that stays mine. It costs me about $40 CAD for a 30 day - 20GB top up. My wife uses Nomad for data only, we both don’t need local numbers, and it generally costs $12 CAD for 5 GB 2 week top-up.

So I figure about $60-70 CAD for 3 weeks travel virtually anywhere in Europe. Calls and SMS included (for one) without long distance charges. Compared to $630 for “roam like home” for two people from a Canadian carrier - doesn’t matter which one as far as I can tell.

We both recently got new phones to be able to use eSIMs.

And the physical SIMs stay active. So my elderly parents can call my Canadian number if there’s an emergency and it will ring through.

In fact, on our last trip to Rome, when we used a credit card at the hotel, it was refused and then seconds later I got a text from the bank asking for confirmation on my Canadian number. I had no choice but to text “Yes” back, and that single text activated roaming for the day and cost me $15.

In this case you could view a swap partition as a safety net. Put 20-30GB in a swap partition in case something goes wrong. You won’t miss the disk space.

I’m not sure a corvette has ever counted as “major” warship.

Well, there are specific hardware configurations that are designed to be servers. They probably don’t have graphics cards but do have multiple CPUs, and are often configured to run many active processes at the same time.

But for the most part, “server” is more related to the OS configuration. No GUI, strip out all the software you don’t need, like browsers, and leave just the software you need to do the job that the server is going to do.

As to updates, this also becomes much simpler since you don’t have a lot of the crap that has vulnerabilities. I helped manage comuter department with about 30 servers, many of which were running Windows (gag!). One of the jobs was to go through the huge list of Microsoft patches every few months. The vast majority of which, “require a user to browse to a certain website” in order to activate. Since we simply didn’t have anyone using browsers on them, we could ignore those patches until we did a big “catch up” patch once a year or so.

Our Unix servers, HP-UX or AIX, simply didn’t have the same kind of patches coming out. Some of them ran for years without a reboot.

Kanban is probably way overkill as a model for what you want. The key about Kanban is control of WIP/Queues at various stages and pulling items through the workflow. With a simple ToDo/WIP/Done workflow, you’re probably going to find any Kanban apps are too complicated for what you get out of them.