HamsterRage

Paywalled

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.

Most people aren't going to need to top up more than 30-40km worth of charge every night anyways. So that's probably only a couple hours on 15amp.

So write it properly from the get-go. You can get 90% of the way by naming things properly and following the Single Responsibility Principle.

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.

And yet I never see any mention of this anywhere. Even here, it seems that Biden is more concerned about whether the court can administer justice because it is so much out of balance. No mention, though, that the "balance" shouldn't even be a factor.

SCOTUS justices are appointed for life because it's supposed to put them above political considerations. No politician can influence them by threatening removal. Yet, there you are, SCOTUS is just as political as the other two branches.

To me, as a non-American, the most baffling thing is that everyone in the States just assumes, and accepts, that these appointed justices are going to rule according to some political bias.

That's not the way it works in the rest of the free world. Judges are, by definition, trusted to be impartial interpreters of the law/constitution. That's their role.

I live in Canada, and I'm vaguely familiar with some of the names of our Supreme Court justices, but I certainly don't know their political leanings, nor do I care. Nor does any Canadian I know. That's the way it's supposed to be.

So as far as I can see, the problem isn't that SCOTUS is stacked with Republicans, nor that it can be. The problem is that everyone seems to assume that this is the way it should be.

"Row headers" seems wrong to me. Maybe "row labels"?

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.

I don't really agree with the degree of doom predicted by the article.

The crux of the matter seems to be that once the workers went back to work they needed to give 72 hours notice to walk off again. That maybe a mistake by the Board, but hardly a calamity. They put in notice and walk off again. At worse, it stretches the length of the negotiations by 72 hours. In this case, it did not.

If this is how the labour boards are going to interpret the laws, then the most likely outcome is that unions are going to stay off work until a tentative deal is accepted and ratified by the members. Why risk having to put in another 72 hours of notice?

Is this good for the workers? No.

Is this good for the employer? No.

So maybe they have an agreement that no notice is necessary to go back to the picket lines if they return to work before ratification.

I don't see any greater threat to worker rights here.

I think that defining "done" as QA tested is way better than "the code compiles", which is essentially what most teams seem to use.

Developers need to get into the habit of not writing bugs. That's technically the answer to all of these problems. "We have issues dealing with bugs found in the QA phase". So stop writing bugs for QA to find, then the problem goes away.

If the attitude is "Bugs found in QA kick the feature out of the release", then the programmers are going to find that they work all week and end up contributing nothing to the release. Maybe the release is completely empty. Hold them responsible for it. Attitudes will change.