I am overwhelmed in my mind right now and I kinda just need it out.

I'm incredibly divided. There's so much I want to do which is fine I can balance some of it kinda well but when it comes to the programming aspects of what I want to do is where my head gets tugged in multiple directions.

Parts of me really want to continue to dive into C# and learn it a lot more than I currently do so I can continue to write the tools I use for problems I come across.

And the other part of me just wants to go do lower level development with C because that's where most of my goals are being mostly embedded and OS development.

But so many people I know that are incredibly smart devs use C# and I see why it's an incredible language and I'm glad it's one of the languages I know but I feel like there's so much to learn about it and I there's so much shit I see that I'm just like I don't know when I would want to use this, or I can see X feature being very useful but I don't know where I'd use it in my projects. Hell even C#s version of structs I know are very useful but I'm not able to make good use of them

I'm just in that headspace where I'm not learning enough and I feel dumb when I look at someone else's project because there's a lot more complexity In their project that none of my projects have ever had and so many people make use of language features I've never used or thought about using (generics being a good example) and I'm constantly asking questions which I know is okay but too much is happening in life lately and it's just making it harder to handle.

Thanks to anyone that got through it hopefully I'm not alone in these feelings

  • 3
    If your main goal is embedded go do that. More codebases you’re thrown into more you’ll pick up and make it yours(knowledge wise).

    C# is cool and all but if your goals lie with embedded and OS development C# is useless to you. You’ll still be able to make tools you need in it tho which is always a plus and each new thing you make will teach you as well.

    My 2 cents.
  • 2
    I think learning by doing is the way to go. Make some own projects and the use cases for C# features will come up naturally:
    When something seems weird or wrong, google it and you eventually stumble upon some solutions like generics. That way you automatically remember and learn it.
Add Comment