Hi,

My question certainly stems from the imposter syndrome that I am living right now for no good reason, but when looking to resolve some issues for embedded C problems, I come across a lot of post from people that have a deep understanding of the language and how a mcu works at machine code level.

When I read these posts, I do understand what the author is saying, but it really makes me feel like I should know more about what’s happening under the hood.

So my question is this : how do you rate yourself in your most used language? Do you understand the subtilities and the nuance of your language?

I know this doesn’t necessarily makes me a bad firmware dev, but damn does it makes me feel like it when I read these posts.

I get that this is a subjective question without any good responses, but I’d be interested in hearing about different experiences in the hope of reducing my imposter syndrome.

Thanks

  • nik9000@programming.dev
    25·
    24 days ago

    I’ve learned a lot by breaking things. By making mistakes and watching other people make mistakes. I’ve writing some blog posts that make me look real smart.

    But mostly just bang code together until it works. Run tests and perf stuff until it looks good. It’s time. I have the time to write it up. And check back on what was really happening.

    But I still mostly learn by suffering.

    • MajorHavoc@programming.dev
      12·
      23 days ago

      But I still mostly learn by suffering.

      That resonates so much. Almost every time someone is deeply impressed with something I know, it brings back a painful memory of how I learned it.

    • Croquette@sh.itjust.worksOP
      3·
      24 days ago

      I really like brain twisters. It can get frustrating at times, but it’s the most fun out of the profession to me.