• 0 Posts
  • 16 Comments
Joined 9 months ago
cake
Cake day: October 18th, 2023

help-circle
  • I moved within the US in part due to this. I realized that we’re just on the cutting edge of the rise of neo-fascism. Europeans have their own issues, Canada has theirs too. New Zealand was always super appealing, but my specialization isn’t well represented there. Australia is like fucking impossible to immigrate to, as is anywhere in the UK, so Scotland is off the list. Ireland seems like they’ll take you if you have 10 bucks and promise to work and pay taxes there, but also it’s pretty culturally conservative.

    I feel more at home in my new state than I may have ever in my old one.




  • This has been stored away in my gm vault for demonstrating what an evil government might mete out as punishment.

    PCs walk into town and there’s a public execution happening, it’s all horrifying screams burning flesh etc, until it finally stops and a hush falls over the gathered crowd. The silence is broken when chanting, faint at first, gradually grows louder and louder until it feels like you can hear it in your mind, just when it feels intolerable a flash emanates from the stake, and the screaming begins anew.




  • Dollars to donuts their infotainment system shares a CAN bus with nodes that affect control systems. If they can’t handle the easy stuff, what the hell else are they fucking up?

    It’s not about the infotainment system, it’s about the culture that leads to this problem.

    This company will not end because of this issue. Boeing is still kicking and you can actually count the number of people they’ve killed with shitty software/system integration process.

    I’ve spent my career working in embedded systems and embedded test and verification. This issue is not the first or only issue to get by. Maybe they take this like the red hot poker it is and fix their problems, maybe not. I’m not gonna gamble on their products though.


  • Anyone who builds software that runs on actual hardware should know that you NEVER deploy builds that haven’t been fully exercised on actual hardware.

    This tells me that their software QC process is non-existent at best and actually malignant at worst.

    If their software is supposed to be their defining feature this is the equivalent of McDonald’s “accidentally” shipping frozen discs of literal shit instead of burger patties to franchises who then serve them to customers without question.

    If their company dies because of this (it fucking should imo) they 100% deserve it for the countless unknown dangers they’ve exposed their customers to. It’s not this particular thing, bricking the infotainment system, it’s the demonstration that they have no or bad process.









  • The short answer is “practice”

    The longer answer is, do it a lot. Listen in code reviews. When you investigate bugs, do actual root cause analysis, understand the problem, and understand how it got missed. Don’t stop learning, study your languages, study design patterns, be intentional in what you learn.

    I had good mentors that were hard on me in reviews. Developing a thick skin and separating criticism of you from criticism of your code will help a lot in terms of learning in reviews.

    Source: 10 years in the field. (Senior SW Eng. Focused on embedded systems and VnV)