• 3 Posts
  • 66 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle





  • Doombot1@lemmy.onetoMemes@lemmy.mlAmd fan
    link
    fedilink
    arrow-up
    25
    ·
    1 month ago

    Most of the time, the product itself comes out of engineering just fine and then it gets torn up and/or ruined by the business side of the company. That said, sometimes people do make mistakes - in my mind, it’s more of how they’re handled by the company (oftentimes poorly). One of the products my team worked on a few years ago was one that required us to spin up our own ASIC. We spun one up (in the neighborhood of ~20-30 million dollars USD), and a few months later, found a critical flaw in it. So we spun up a second ASIC, again spending $20-30M, and when we were nearly going to release the product, we discovered a bad flaw in the new ASIC. The products worked for the most part, but of course not always, as the bug would sometimes get hit. My company did the right thing and never released the product, though.














  • Doesn’t provide enough power for the cost of the cells, plus having to clean and upkeep them. And the more material you cover them with (to protect them; solar cells are INCREDIBLY fragile), the less efficient they are. I was on a solar car team in college and the cells are so fragile that to clean them, we had to use new microfiber cloths every time. Any dust would scratch and ruin them (which made it quite tough when I drove across the outback in the thing). We kept our cells completely uncovered because we needed maximum efficiency - but even with a super light carbon fiber solar car that’s got very minimal tire contact patches, specialized tires from Bridgestone, and a very aerodynamic shape (plus no amenities like A/C), I think our car could sustain something like 10-15 km/h on a perfectly sunny day in the middle of the outback. It just doesn’t add enough on a huge, heavy EV


  • I started with C++ too, and then ended up finding a job writing firmware pretty much all in C. There really hasn’t been anything we’ve run into that’s made us consider switching to C++; being able to (and needing to) have complete control over your memory means you can do some pretty fancy stuff with the tiny amounts of memory on our ASICs.

    We’ve been eyeballing switching to rust a little bit, but really only for other applications; the root of our main code base is over 25 years old at this point and a rewrite would take a Herculean effort.