Virtually anything by Bernard Cornwell.

The key word is “immediately”. It is within his power to delay the byelection for months.

We’ll, the article was about the jobs maintaining the robots, not humans building stuff in factories.

I’m not so sure about the “jaws of Victory” bit. I think that Canadians were just fed up with Trudeau, couldn’t bring themselves to vote NDP and ended up polling Conservative. So it wasn’t really support for PP, but unsupport for Trudeau.

Take Trudeau out of the equation and the Liberals came flooding back to the party.

I’m not sure that I can remember that being done for any leader at the federal level in the past 50 years or so. We’ll have to wait and see.

He still gets to be party leader, but he cannot sit in Parliament. There are two remedies for this. First, the party can choose a new leader from their elected MPs. Second, they can have an MP in a “safe” riding step down and then ask the government for a special by-election in that riding.

Wait til the OP learns about the Easy Bake Oven.

20.5 in winter and 21.5 in the summer.

L’esprit de l’escalier

I call BS.

I’m Canadian and my parents immigrated here from England before I was born. I have a UK passport as well as a Canadian passport.

I’m not English-Canadian, I’m just Canadian. No one hyphenates in Canada, and you cannot say that Canada has any more unifying cultural heritage than the USA.

I am fascinated by his thumbs.

Kotlin is a very easy transition, and it sorts out a ton of issues that you find in Java. Certainly easier than moving to Rust.

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’m not sure that what developers really, really need is faster programming cycles. Most teams could benefit more by controlling the process - from idea to deployed. How much technical debt is incurred because users/customers can’t prioritize features or give accurate requirements, there’s way too much WIP, features are huge, releases are huge and infrequent and the feedback cycles are far too long.

So yeah, as programmers it’s always cool to look at ways to program faster, but what’s the point in programming stuff nobody needs faster? Or programming the wrong things faster?

I’d be willing to be that if you asked any team, “What are the biggest impediments to delivering value to your users faster?”, the answer would be that you can’t cut code fast enough.

Calling customers, “guests”. A customer is someone with a business relationship with someone/something else. They’re exchanging money for goods and services and have a right to expect certain value for their money.

A guest is something else entirely. A guest has no implicit right to expect a certain any particular level or quality of services. They are dependent on the magnamity of the “host”.

Calling a customer a “guest” robs them of status.

Nothing formal. Pull, pull, legs and a rest day. I stick to fundamental exercises like bench press, chin ups, squats, leg presses, cable rows, lat pull downs, preacher curls, lat raises and Arnold presses.

I start off with about half my normal weight and comfort 20 to 25 reps as a warm up for most exercises. I aim for 8 to 12 reps, of the same weight for 3 sets of the same number of reps in each set.

I use the free version of an app called, “Strong”. It lets you keep three different active workout routines, which is just enough for pull,push,legs. It makes it easy to keep track of progressive overload. Personally, I aim for 1 more rep each day until I get to 12+ reps. Then add more weight. Rinse and repeat.

I went from doing all my sets “to failure”, to first set 8RPE (rate of perceived exertion). So three sets, all the same number of reps and weight.

I work it backwards. The third set should be very close to 10RPE if I get 8RPE right on the first set. If it’s under then I do extra reps to get there. The next time I do that exercise I can see the extra reps and adjust accordingly.

This is SO much better on my aging body, and I’m still able to keep up progressive overload at the same rate as I was with “to failure”.

For those who don’t know RPE is a self assessed evaluation about how hard a set was to complete. It’s a scale from 1 to 10. 10 means there’s nothing left, complete fatigue at the end and no hope of any more reps. 8 generally means that you have about 2 reps left in the tank.

The head is shaped like a mushroom, so it cuts on the side and right on top. Unlike the others which are tube shaped.

I just tried it. It does a pretty good job, but I don’t have really furry ears.

That’s what I thought until I got that one. Then I realized what I had been missing all along. Marketing? Nope. Just sharing what I found to be good.

Every time I go back to Java I feel sad.