HamsterRage

joined 2 years ago
[–] HamsterRage 3 points 21 hours ago (1 children)

I spent 30 years working with derivatives of the Pick Operating System and its integrated DBMS. Notably Universe and Ultimate. Back in the day, it was very, very difficult to even explain how they worked to others because the idea of key/value wasn't commonly understood, at least as it is today.

I was surprised at how similar MongoDB is to Pick in many many respects. Basically, key/value with variant record structures. MongoDB uses something very close to JSON, while Pick uses variable length delimited records. In either case, access to a particular record in near instantaneous give the record key, regardless of how large the file is. Back in the 1980's and earlier, this was a huge advantage over most of the RDBMS systems available, as storage was much slower than today. We could implement a system that would otherwise take a huge IBM mainframe, on hardware that cost 1/10 the price.

From a programming perspective, everything revolves around acquiring and managing keys. Even index files, if you had them (and in the early days we didn't so we maintained our own cross-reference files) were just files keyed on some value from inside records from the main data file. Each record in an index file was just a list of record keys to the main data file.

Yes, you can (and we did) nest data that would be multiple tables in an SQL database into a single record. This was something called "Associated Multivalues". Alternatively, you could store a list of keys to a second file in a single field in the first file. We did both.

One thing that became very time/disk/cpu expensive was traversing an entire file. 99% of the time we were able to architect our systems so that this never happened in day to day processing.

A lot of stuff we did would horrify programmers used to SQL, but it was just a very different paradigm. Back in a time when storage and computing power were limited and expensive, the systems we built stored otherwise unthinkable amounts of data and accessed it with lightening speed on cheap hardware.

To this day, the SQL concepts of joins and normalization just seems like a huge waste of space and power to me.

[–] HamsterRage 1 points 2 days ago

I fixed it by installing Shazam. Since then I haven't paid any attention to it.

[–] HamsterRage 3 points 2 weeks ago

"My nipples explode with orgasmic delight".

[–] HamsterRage 4 points 3 weeks ago (3 children)

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.

[–] HamsterRage 10 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Except I'm not actually talking about spelling, per se, but about attention to detail. Spelling errors in a resume is just sloppy rubbish.

[–] HamsterRage 11 points 3 weeks ago (4 children)

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.

[–] HamsterRage 3 points 3 weeks ago

Proper pickled onions and Branston pickle.

[–] HamsterRage 3 points 3 weeks ago

Bob's Red Mill makes an adequate substitute. It's not as uniform as McCann, but it is good.

[–] HamsterRage 1 points 1 month ago

Written by a Canadian Much Music VJ.

[–] HamsterRage 5 points 2 months ago

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.

[–] HamsterRage 3 points 2 months ago

I remember that you could get close to this by running the same card into the keypunch several times, typing different things each time.

 

21
Group Shot (self.crochet)
submitted 2 years ago by HamsterRage to c/crochet
 

For some reason, the wife decided to pull out all of the amigurumi critters that she's made since she started doing this at the beginning of the year.

So, here you go, the group shot:

37
submitted 2 years ago by HamsterRage to c/crochet
 

She said that the pattern was awful and that she had fudge all kinds of stuff to make it work. The hat needed to be completely redesigned.

4
Still Not Ready? (self.fedidrama)
submitted 2 years ago by HamsterRage to c/fedidrama
 

I'm beginning to think that this sub will never be ready. What's the hold-up????

25
Amigurumi! (lemmy.ca)
submitted 2 years ago by HamsterRage to c/crochet
 

The wife has started to make these amigurumi creatures. Here's her latest two.

She uses worsted weight wool (she tells me) which generally results in bigger creatures.

 

I wanted one of these back in 1980 when I was 16. I remember that they were $1,200, but they might as well have been $1,200,000 as far as I was concerned.

Many years later I had the $$$ to buy one, and this one is a beauty. Koa, with Bill Lawrence pickups.

Look at all the knobs and switches!!!

 

This is the beside the time since the post was created. I cannot figure it out.

 

I live in Canada, where we are graced with the most expensive cell phone plans in the developed world. One of the "features" of my plan is something they call "Roam Like Home". With this feature, I can use my data and time from my plan just like I haven't gone anywhere, for the low, low price of $15 a day!!!

This is activated automatically the moment that they detect that I am roaming. I cannot opt out of this "feature", and the only way to avoid it is to put the phone in airplane mode and then activate wifi. There is a cap to the number of days you can be charged, but runs on a calendar month basis, so if you are away across the end of the month, you can get charged more than that maximum.

For me, the answer came in the form of eSIMs. I ditched my old Galaxy S9, and bought a Pixel 7 in May. Then I purchased an eSIM for France for both data and talk (30GB for 30 days for around €45) and went to France for 24 days.

I was really pleased with the Pixel 7 in the week or two that I had it before we left on vacation. The battery life was way better than the S9, and 2 hours at the gym, with YouTube Music on Bluetooth and "Strong" running to track sets and timing left me with close to 90% battery left. It would be closer to 50% on the S9.

No heat issues here in Canada.

When the plane landed in France, the eSIM automatically activated, and I turned it on for both data and voice/SMS. Nothing could be easier, and it works like a charm.

At around this time, the issue with hot Pixels started, and eventually Google found the issue with their servers that was causing this. Hot Pixels with short battery life faded from the news.

But not for me.

Ok, so battery life was still better than my old S9, but not by much. And it got hot, too. It seemed to be particularly bad when I set up a hotspot for my wife - as this was the plan, she would use wifi off the Pixel hotspot since her phone doesn't support eSIMs. Out and about, I could expect to lose up to 15% in the first hour, and then it would maybe go even faster after it was down below 70%.

Taking pictures seemed to be especially hard on the battery, too. Not surprising, really, as the new camera features use a lot of computing power. We had Android Auto in our rental car, and Google Maps would drain the battery at almost the same rate that the car would charge it.

I was waiting for the new updates to drop, hoping that might have a fix, but as of June 13, we still haven't seen it. In the meantime, we've returned to Canada and I've turned off the eSIM.

And now the battery life is back to where it was before we left. I haven't once noticed the phone getting hot either.

So there you go. Has anyone else noticed this kind of issue with eSIMs?

view more: next ›