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.

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

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

For me Bazzera Magica and Baratza Vario grinder some time back. Better coffee than most cafes.

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.

Kermit on top of FTP can work really well. Kermit has its own communication and transfer protocol, IIRC, but updates in the 1990’s allowed it to be used with TCP/IP and FTP. So you can write a script to log into a remote system, run some commands and then initiate a file transfer. The scripting allows you to wait for responses and act on them.

St Peter the Martyr!!

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.

That used to be really true when I was a kid in the 79’s, but not so much today. Back then, a quality guitar cost way more than the cheap stuff and the cheap stuff was rubbish.

Nowadays, with CNC machines everywhere, there are lots of modestly priced guitars that are very playable. The junk that we used to have to settle with back in the day only exists in the realm of “toy” instruments that almost aren’t intended to be played.

Seriously, $300 can get you a very playable instrument, especially in electric guitars.

The workplace should have a zero tolerance policy about abuse of the staff. If the particular location is one where there is a significantly non-zero chance of such incidents happening, then there should be a big red button on the wall that sounds and alarm, and summons security and possibly triggers a police response.

Employees should be trained to hit the button at the first hint of abuse. The employer should support them.

From a practical perspective, I think that viewing SRP as referring to “direct” responsibility is good enough for making programming decisions.

Take the example from the Wikipedia entry. A module that compiles and prints a report. If that was split into 3 modules: one that compiles; one that prints; and one that delegates to the previous two modules to produce the output, then you would have achieved SRP. Yes, the third does two things, but it delegates them and is therefore not directly responsible for them.

At the same time this holds with the spirit of the official definition. Each module is only responsible to one source of change.

At a certain level of detail, your sources of change start becoming other modules and not users or Product Owners. Then it’s harder to think about SRP the “official” way. But direct responsibility is easier to make decisions on.

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.

If I remember correctly, Objects were introduced in Turbo Pascal 5.5, not version 7.

I seem to remember that the “add potatoes if too salty” bit has been tested and disproved.

It doesn’t have to be BYOD. The firm might willing to procure a specific machine for her. Or she might have enough clout to make them get her what she wants.

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.