• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle

  • As an IT/Development manager, I only had one role that I hired for where the skills for getting the job matched the skills for doing the job: Business Analyst. Not job entailed presenting information clearly, both written and verbally. So I expected the resume and cover letter to be organized and clear.

    Programmers, on the other hand, I wouldn’t expect the same level of polish. But I would expect a complete absence of spelling errors and typos. Because in programming these things count – a lot.

    A lot of the people that applied, and that I hired, did not have English as a first language. So I gave a lot of latitude with regard to word selection and grammar. But not spelling. Use a goofy word or two, but spell them right.

    I figured that most people were highly motivated when writing a resume – about an motivated on you can get. And if not level of motivation cannot get you to take care, then you’ll just be a bug creation machine if I let you touch my codebase.


  • Back in the 70’s and 80’s there were “Travesty Generators”. You pushed some text into them and they developed linguistic rules based on probabilities determined by the text. Then you could have them generate brand new text randomly created by applying the linguistic rules developed from the source text.

    Surprisingly, they would generate “brand new” words that weren’t in the original text, but were real words. And the output matched stylistically to the input text. So you put in Shakespeare and you got out something that sounded like Shakespeare. You get the idea.

    I built one and tried running some TS Eliot through it, because stuff is, IMHO, close to gibberish to begin with. The results were disappointing. Basically because it couldn’t get any more gibberishy that the source.

    I strongly suspect that the same would happen with Trump’s gibberish. There used to be a bunch of Travesty Generators online, and you could probably try one out to see.



  • I would have a couple years ago. In a flash. We replaced our phones a while back specifically to have eSIMs. It truth, considering the cost of Canadian roaming plans the phones have already paid for themselves.

    Both of our old phones were single SIM, so using a local SIM would mean disconnecting our Canadian numbers which would put us out of touch with people back home. Which means that this card wouldn’t have work for us either.

    I was at the point of looking at buying a portable WiFi hot-spot, when I found out about eSIMs. So we went that route.


  • I have an Orange eSIM with a France number that I have kept alive by reactivating it at least once every 6 months. It’s good for all Europe, without roaming charges, so that’s easy to do. Having the same number all the time is convenient, but more importantly I have gone through the hassle of providing passport info to Orange, which is a government requirement if you want a number for more than a couple of weeks. I think that’s an EU thing.

    The local number is good for calling hotels and for making restaurant reservations. Just having that is a game changer.

    For my wife’s we don’t need a number, so I just use Nomad for her data only eSIM, and get a new one each time. The cost is about $12-15, and you get whatever carrier you get, but the service has been good so far no I keep using Nomad.

    We can text each other using WhatsApp, and you can even use WhatsApp for voice calls. The sound quality is acceptable.




  • 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.



  • As a boomer (at the tail end, admittedly), I too have lived through all of these things. Plus the other thirty years of shit that happened before it.

    The world threat that was the USSR and Mutually Assured Destruction. The Vietnam War, two Gulf Wars, and 9/11.

    The “Troubles” in Ireland and IRA bombings in London. The Munich Olympics Massacre. The rise of global terrorism. The FLQ crisis. Kent State. Watergate.

    Acid rain. Leaded gas and smog.

    15%+ mortgage rates. The oil crisis. Wage and price controls. Multiple recessions. The Dot Com bubble.

    Police raids on gay clubs. Racial slurs in everyday language. Massive gender inequality.

    24" black and white TVs. It took a week to find out how your photos came out. Watching f@#$ing “Tiny Talent Time” on a Sunday afternoon because there wasn’t any else better on the other 5 channels (if that doesn’t traumatize you, nothing will).

    You had to go to a library if you wanted to look something up in an encyclopedia.

    Cars without seatbelts, crumple zones, anti-lock brakes, traction control or airbags.

    F*CK me. “No experience”. Maybe just enough to know how much better things generally are today.

    Kids always think that they know more than their parents…until they don’t.


  • Well, there are specific hardware configurations that are designed to be servers. They probably don’t have graphics cards but do have multiple CPUs, and are often configured to run many active processes at the same time.

    But for the most part, “server” is more related to the OS configuration. No GUI, strip out all the software you don’t need, like browsers, and leave just the software you need to do the job that the server is going to do.

    As to updates, this also becomes much simpler since you don’t have a lot of the crap that has vulnerabilities. I helped manage comuter department with about 30 servers, many of which were running Windows (gag!). One of the jobs was to go through the huge list of Microsoft patches every few months. The vast majority of which, “require a user to browse to a certain website” in order to activate. Since we simply didn’t have anyone using browsers on them, we could ignore those patches until we did a big “catch up” patch once a year or so.

    Our Unix servers, HP-UX or AIX, simply didn’t have the same kind of patches coming out. Some of them ran for years without a reboot.