Literally every single day.

I remember when I was dying to get in the field. Now that I am in I realized there are a lot of bleh moments.

Love my job tho, but shit ain't nearly as exciting as I thought it would be lol

In general, a job (regardless whether selfemployed or not) comes with constraints. That constraints most likely don't perfectly align with what you actually want to do.

If you are lucky, making your hobby your job nets you a not-that-bad job.
You certainly lose your hobby on the way, because coding is a mentally taxing activity.
But it may still be better than having a really shitty job.

If you aren't lucky, making your hobby your job nets you a shitty job while you also can't have fun coding in your free time, because there is no mana left after a full day of coding for the job.

@Oktokolo @M1sf3t you are both correrect my dudes.

I have told the head of my department that my guys are constantly on maintenance mode for things they didn't develop that are badly implemented and developed to begin with. As a veteran (strictly referring to military actually) I know that de-motivational duties are mind-taxing, and it is the same reason why I really make a case in point to rewrite entire projects in things that would make everyone in the team feel proud of.

I have gotten to the point in which I want to change to a different field. I have always wanted to try my hand at embedded C development, if you ask me there is no higher form of development than this, it frees and at the same time opens your mind to an entirely new world of possibilities. Which is why I am betting on my dude @QuanticoCEO

@AleCx04
Hmm, embedded is certainly an interesting field - but C is one of that languages where the most trivial bugs have the most dire consequences - and even the best C coders still produce a lot of CVEs.
Would at least try to go OCaml (Mirage OS), Erlang (OTP), or some other less error-prone language. Then you still get DoS bugs - but at least there are probably no RCEs...