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

  • Croquette@sh.itjust.worksOP
    2·
    1 month ago

    What I like about embedded is that it’s between software and hardware, where you have to know both to a certain extent. It kinda feels like being a mad scientist bringing a monster to life. Seeing that my code makes physical actions (lighting a LED or controlling a motor) never seems to get old, even when trivial.

    I am confronted everyday about the things I don’t know because I work in a startup and I am the only one that does what I do. Any issue that I have tells me what I need to learn to fix the issue.

    You are right that for a lot of people, what I do seems like magic and we often forget the extent of our knowledge because it has become innate.

    Thanks for the insight, I appreciate it.