Also, the final note on the bass is a mistake, but they left it in.
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.
In respect to sitting above the API layer and turning DTO’s to/from Domain Object’s, I’d call them “Brokers”.
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.
Give credit to George Carlin for that one.
FORTRAN IV was the first language I learned to program in. Punch cards!!!
I retired now, but I still write code for my blog. I totally prefer to write with Kotlin. Java just feels clunky to me now.
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.