• 2 Posts
  • 16 Comments
Joined 9 months ago
cake
Cake day: June 7th, 2024

help-circle
  • We’re in earthquake terrain (a fault line runs through the middle of town). My concern would be what happens in case of a Loma Prieta scale quake. Going to do some research on fault tolerance, redundancy, and avoiding single points of failure.

    Have a buddy who works at a FAANG and has been doing a lot of work on DR. He showed me a picture of his stash of prototypes. Turned out all were built on top of Meshtastic. Going to hit him up for tips next week.








  • My first tech job out of college, I was told to go talk to “Dave,” the guru old-timey programmer and learn the lay of the land. He turned out to be this crotchety old guy, with low tolerance for idiots, but a soft spot for someone who actually paid attention.

    A few months in, I was told to go fix a feature in the company’s main product which was sold to power utilities. This was a MASSIVE code base, with a mix of C, C++, assembler, and a bit of Fortran thrown in. I spent a week poring through all the code trying to figure things out. Then I hit a mystery workflow that didn’t make sense.

    I walk over to Dave’s office and ask a specific question. Now, mind you, he had worked on this years ago, and had long moved on to new products. He leans back in his chair, stares at the ceiling, then without looking at the screen once tells me to go look at such and such file for such and such variable, and a list of functions that were related. I go back to my desk and damn if it wasn’t EXACTLY as he described.

    Now, I’m probably as old as he was then. I don’t remember what I wrote an hour ago. No matter what I build, I’ll always be in awe of Dave and what he could keep in his head.




  • Most IoT devices that died did so because the vendor went out of business and had to shut off the servers. Most lived in hope that a last minute investment would keep them afloat. In a few other cases, it was the middleware software provider (like Google IoT) that shut down and bricked a device.

    This legislation might apply to a big company that decides to discontinue a product line and could then send notices out, but most startups won’t know (or admit defeat) till the last possible moment. By then it’s too late.






  • Just had a thought… here’s a prime example of one of the stated advantages of the Fediverse. If you get locked out of one account, you can move to another instance.

    Question is: do you get to carry over your profile, subscriptions, followers, comments, saves, up/down votes? Or do you have to start from scratch.

    Because if it’s scratch, somebody should change the “Fediverse Promise” so users know what to expect.

    I’m guessing I know the answer, but this could be something Voyager could handle. Maybe even for a sustainable fee 🤔