• 1 Post
  • 108 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle








  • jballs@sh.itjust.workstoMicroblog Memes@lemmy.worldThe moon
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    2
    ·
    6 days ago

    If you’re from the US, the moon is the size of a dime when viewed from 6 feet away. I don’t know what a universal measurement would be for folks outside the US.

    Anyway, it always cracks me up when people get hyped for a “super moon”. This tiny object in the sky is going to be indistinguishably less tiny!


  • Unfortunately, I think this is the most likely scenario. Going from our modern technology levels, which are more than capable of destroying the world, to Dyson spheres is a huge leap that will take who knows how long (decades? centuries? millennia?).

    Before that happens, we have to live together on a planet without blowing ourselves up or making the planet uninhabitable. As technology continues to advance, walking that knife edge of survival seems more and more difficult. The pessimist inside of me says that no civilization has been able to accomplish it.


  • Yeah, it seems very possible that at one point, civilization will turn inward instead of outward. Why go through the time and effort to colonize the stars when you can just create a cyber-utopia? If you’re advanced enough, you could make it feel like an eternity while almost no time passes on the outside.

    Sure, your planet might get destroyed by a cataclysmic event in the far future, but if you can make that feel like billions or trillions of years, who really cares?





  • Same. Especially since I’ve been building EDWs for most of my career. People are always surprised that it actually takes time to integrate with different systems.

    “What do you mean you can’t just pull all the data out of this system that we don’t have database access to and are still building out the APIs?”

    I kid… The people asking for stuff don’t know what backend databases and APIs are.




  • I got pulled into a meeting with a team from AWS. I was told they were looking to implement a new solution, so I had to explain in detail how our data lake and data warehouse solution worked. I showed them how we pull data from all these different sources, how we have different integration patterns, etc.

    At the end of my presentation, I asked “does that give you what you guys need? Or do I need to go into any more detail about anything specific? I don’t know what you all are actually building, so I’d be happy to provide more detail where you need it.”

    Their response was “yeah that was all great info. We’re looking to build an app using AI and ML that allows you to run the business with a click of a button.”

    I’m glad it was a remote meeting without cameras, because I literally face palmed. They didn’t have an actual use case or problem they were trying to solve. They were literally just selling a solution built on AI and ML. They didn’t know what it was gonna do, but by God they were committed to selling it.


  • This picture is actually a lot more impressive than it looks, because there were no color cameras available when it was taken. Instead, he had to take three different pictures, using three different color filters like RGB, and then combine them to make it color.

    From one source:

    Prokudin-Gorsky’s camera design required a camera operator to take three individual negatives after each other. Given that Prokudin-Gorsky is seen posing in the image, it is more likely that one of his assistants took the picture.

    And another

    To this day, nobody knows exactly what camera Prokudin-Gorsky used, as no documentation of his equipment is known to exist, but it was likely a large wooden camera with a special holder for a sliding glass negative plate, taking three sequential monochrome photographs, each through a different coloured filter.


  • The problem I ran into was the response returned a JSON body, but then had an “error” attribute that was returned in it that had the error details. So we were parsing the JSON and loading elements into our database. We were hitting the API passing in a datetime of when the last success job was run, so basically saying “give me everything that’s changed since I last called you.”

    So yeah, eventually we noticed we were missing small chunks of data. It turned out that every time the API errored out, we’d get a valid JSON response that contained the error message, but it didn’t have the attributes we were looking for. So didn’t load anything, but updated our timestamp to say when our last successful call was.

    Huge pain in the ass to troubleshoot, because the missing data was scattered with no distinguiable pattern.