• 6 Posts
  • 188 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle







  • Thanks for your input.

    I think I would like to follow all these people and their work on C, and their in depth knowledge. But free time is sparse, and I don’t have the mental energy when I do have some time.

    As for my work, I work in a startup where I am the only one doing what I do. However, I have a lot of leeway in how I code, so I am always somewhat read on best practices. So I can’t really refer to a senior dev, but I can self-teach.

    I think I coded enough that a lot of what I do is a reflex, and I often can approximate a first solution,but I have doubts all the time on how I implement new features. That makes it so that I am a slower coder and I really struggle to do fast prototyping.

    I am aware enough of what I do well, and what I struggle, so there’s that.


  • At least, we know emotionally that it will get better with the second one haha, even if the day to day is rought.

    With the first one, it felt like we would never get to the other side of it. But we did and we will for the second one.

    I am eager to learn new things, so having so little free time is definitely tough. And the lack of sleep/energy makes it even harder.

    Thanks for the encouragement, it’s nice to be acknowledged by someone else that went through the same thing. We often forget that we are not alone and a lot of people got through it before us.


  • I work in a startup, so I’d say that almost every day, I learn something new. So I don’t really need to look in-between tasks because a lot of tasks bring new challenges.

    When I worked in corpos, my job was restricted to the same tasks and specific knowledge. Now it’s the opposite where I need to learn what I need to create a feature or fix an issue.

    I guess that lately, a lot of new things have popped up and I need to absorb a lot of information to implement the features I need. And that is probably what is triggering the imposter syndrome.

    Thanks for the insight, it is appreciated.


  • 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.




  • I work in a small start-up where I am the only one doing what I do, so my epiphanies come from the struggles I have.

    Other people I work with often have a blank look in their eyes when I try to explain some issues or what the code does because they don’t have the skillset to comprehend what I am doing. So this isn’t a path for me (yet, hopefully we can grow enough where we need more people in my field).

    But I appreciate your experience. I will certainly think about a way to play in the innards of my language so that I can understand it better.



  • Thanks for the input, it will make me think about how to approach how to get the skills I need.

    I’d say I am decent with FreeRTOS which is pretty much just a scheduler with a few bells and whistles.

    I haven’t used assembly in a long while, so I know where to look to understand all the instructions, but I can’t tell right off the bat what a chunk of assembly code does.

    Algorithms, I am terrible at these because I rarely use them. I haven’t worked in a big enough project where an algorithm is needed. I tend to work in finite state machine which is close to algorithms, but it’s not quite it. And a big part of my job is interfacing peripheral chips for other to use.