[Kon-Peki]

It's never going to be like it was in college. People don't pay you lots of money for that.

I can't tell you whether to stay or leave, but you have to understand that any job you land will be a job, and someone else is going to be in charge of the what and the how.

Also, please don't spend all of your free time coding. By all means do a bunch of coding in your free time. But do lots of other stuff too.

[streakofred]

This is a hard pill to swallow. I'm hoping though that there might be positions where I at least like the day-to-day work even if I can't get behind the what and how.

> Also, please don't spend all of your free time coding.

Sadly, I'm pretty drained after work these days so I usually do everything else.

[Kon-Peki]

Ok, one last piece of advice from someone who knows almost nothing about your day-to-day, just what you initially wrote.

Your value isn’t from the skills you have, it comes from your ability to apply them to problems to produce a useful outcome.

What parts of your job can benefit from applying your software engineering skills? It could make things a lot more bearable, perhaps even enjoyable.

[streakofred]

> What parts of your job can benefit from applying your software engineering skills? It could make things a lot more bearable, perhaps even enjoyable.

Thank you, this sounds like a good first step to getting some more passion into my day to day.

[quickthrower2]

That said they are definitely jobs where you spend 80% time coding and there are new features to code if not greenfield work. Finding them is a challenge to itself though, but asking in the interview is a good idea.