I cannot express adequately how different blades are from each other. Some are smoother than others, some are sharper and some improve after a few uses. Some last longer.

I have fairly fine whiskers, so I don’t need a crazy sharp blade like Feather. My skin is also a bit sensitive, so a smooth blade is best.

For me Big Ben, blades made by Lord in Egypt are really good. One of the versions of Shark, also made by Lord are pretty good too.

I find Wilkenson Sword blades to be horribly scratchy, and the name for some of the Gillette blades. Voskhod aren’t bad, except they are Russian.

You don’t realize how different they are until you try.

Blades vary greatly between brands. Get a sampler pack from eBay to find ones you like. Then buy them in bulk. 100 blades will generally cost from $8-$14, depending on the brand. Some, like Feather, are more expensive.

What about Skype?

That’s a little confused. From what I remember, it’s the server that matters, not the domain when being blocked. If you self-host this is a problem, but not if you use your own domain on a commercial service.

The “MX records and such” are all a function of domain management. You’ll have to do this whether or not you self-host.

I totally agree on the toasting, but note that it means the oats take longer to cook in the water. Also, I use a 2:1 ratio of water:milk instead of just water.

Also, also, I add a handful of rolled oats when the steel cut oats are nearly done.

It seems more rikely, if hit by an IBM truck in 1985 that he would be ebcdic’d to Seattle.

That’s me! “Teal”, perhaps?

For me turquoise is turquoise.

The reason for leaving in the password.trim() would be one of the few things that I would ever document with a comment.

You might want to think about it a bit more before putting it to work. The comment with the streams example is far, far better.

https://youtube.com/shorts/zC8eSSvnYXg?si=cqs53b_6ggLjU7NP

Also, the final note on the bass is a mistake, but they left it in.

It goes really well with YAGNI. Also DRY without YAGNI is a recipe for premature over-architecting.

This is also one of the main benefits of TDD. There was a really good video that I can’t find again of a demonstration of how TDD leads you to different solutions than you thought you use when you started. Because you code exclusively for one single requirement at a time, adding or changing just enough code to meet each new requirement without breaking the earlier tests. The design then evolves.

I’ve always heard of your “post-architecture” referred to as “evolutionary design”.

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.

In respect to sitting above the API layer and turning DTO’s to/from Domain Object’s, I’d call them “Brokers”.

I looked and Python has the library support for the GPIO and to do background threading to poll pins. My preference would be to go with a JVM language like Kotlin, but then I’m a programmer. Python, from the little that I’ve mucked about with it is really just one step in complexity from scripting. Maybe even easier, because some things in shell scripts are super difficult to do.

Maybe then you need to move one stop up from scripting into something closer to actually programming. I’d be surprised if Python doesn’t have the library support on a Pi for dealing with both serial and GPIO I/O.

the end stop in external to the serial communication

Does this mean that you have some kind of other signals or pin-outs? If so, this is starting to sound like a great project for a Raspberry Pi, because the GPIO pin array can handle that.

Keep in mind that it has been decades since I last used Kermit, but I’m pretty sure the use case it was originally designed for was…

Connect to a serial port, which had a modem attached. Talk to the modem and get it to dial a number. Presumably, the remote end answered and the port attached to its modem would issue a login prompt. Negotiate the login and then issue a bunch of commands to change directories and then launch Kermit on the remote system. After that Kermit to Kermit communications took over until you terminated the session. Finally, log off the remote system and hang up the modem.

All of this stuff could be done via scripts. I seem to remember that it would actually wait for a response, and then parse the response in the script. I don’t remember ever doing polling loops.

If you’re on a *nix box of some type, it’s totally possible to open up a serial port for manual I/O even in something like a bash script. Even if you have to reverse telnet to a terminal server.