

It seems more rikely, if hit by an IBM truck in 1985 that he would be ebcdic’d to Seattle.
It seems more rikely, if hit by an IBM truck in 1985 that he would be ebcdic’d to Seattle.
Take a look at this:
This is in the Museum of the Palazzo Massimo alle Terme in Rome, and it comes from an ancient Roman Villa in Rome. Probably painted in the first or second century CE. There’s walls of this stuff in the museum.
It’s not realism, but minimalistic sketches that, in many ways, outdo realism in artistic quality. To me, this looks more like something that you might find in Leonardo’s sketchbook than on the wall of on ancient Roman Villa from 1200 years earlier.
The reason for leaving in the password.trim()
would be one of the few things that I would ever document with a comment.
I used KDE Connect on Ubuntu with Gnome. No issues.
Old school Unix guy here…vi,awk and sed are all that you need.
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.
Also, the final note on the bass is a mistake, but they left it in.
I wonder how depressed Giorgio Tsoukalos’s dog is???
Thank God somebody got it.
“Intercourse!”
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”.
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”.
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.
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.