Warning: this comment turned out more "ranty" and longer than I hoped. However, I've noticed too many pre-mature conclusions (I wouldn't call them mistakes as they're very corrigible) that either I or my close friends have made that have -- at one point or another -- led to bouts of intense misery.

I am going to say "stick with it"

0) "Well, ... I've realized that's not what I want to do?" How do you know that you will want to do whatever is it that you now think is interesting a year after you start it?

1) Really, you "don't have any good ideas"? There is no itch that you have that you want to scratch? I find that really odd: what constitutes a good idea in your mind?

I am not saying you should do your own company, in fact I'll probably go ahead and state that you should not: you start a company because you strongly believe you can build a product that has (or will have) a great market, not because you want to "follow your dreams", "be the big boss", or simply don't like your current job.

It's just that it's very strange that you can't think of any product you'd like to use. Just writing this comment made me think of several: a plugin for chrome that lets me use an external editor (there were several for firefox, can't find any decent ones for chrome), a "preview box" for hacker news, and other forum markup languages, a tool that tracks replies to my comments on different sites; these may or may not have built before, but these are all products I'm not using now and would like to use.

2) A "boring" job you don't completely hate is better than no job or the job you hate.

That said, take this impulse with a grain of salt: "a pain I already know" is a bad approach to life. However, you don't have any "aim" in your career, so you might not know what constitutes a job/career that you are likely to like (see point 0).

3) You are (probably?) talented but you don't yet have either (as other commenters stated) autonomy or mastery. Frankly, the examples you've mentioned (learning new programming languages as the pinacle of programming passion) are indicative of that. Programming languages are just one aspect of programming: some people get worked up about nuances of programming languages, but others are more interested in hardware/software interactions, low-level systems programming, scientific computing, machine learning, data analytics, etc...

You are just one year out of school. Did you have any internships? If so, why did you chose to stick with programming despite the experience of your internships (does this reason still hold?)

If you did not have any internships in college, whatever job you have, is very likely extremely entry-level and isn't a good starting point from which to draw conclusions.

4) Product management is a great career, but best product managers are former software engineers: the role of a product manager should be "do all it takes to get a product shipped", which may or may not involve writing code.

I greatly respect product managers, but specifically for the reason that they are capable of doing technical work (whether coding or something else) and usually love it, but are willing to put that love aside and do "boring" work (sending email, getting "highest people in the room" to agree on product requirements, talking to customers) that is required to ship a product.

Seriously, if you think programming is boring, see what product managers (real product managers who have shipped products, not self-styled "product guys" with no qualifications who think that a turtleneck makes them the next Steve Jobs) actually do day-to-day.

With all this in mind, here's what I advice:

1) Identify N people at your current workplace whose jobs you think you'd like to have. Talk to them, see what they actually do day to day, learn about how they got to their current role and what it would take for you to follow their path.

2) Identify N growing skills within the software industry that you think are interested, but (here's the catch) aren't something you find regularly on frontpage of HN (i.e., no node.js, MongoDB, or other trendy technology of the week). In other words, think at a deeper level ("high-performance distributed computing" and "data analytics" instead of "Hadoop"; database internals" and "distributed systems" instead of "NoSQL"). If you are at all interested in any of those fields, start to slowly dip into them (whether at work or at home).

This is similar to Cal Newport's advice of "become so good that they can't ignore you": http://calnewport.com/books/sogood.html

This is what Steve Jobs actually did instead of what he said he did, i.e., this is why you are able to enjoy playing with the latest Apple products.

3) Talk to somebody in med school or pharmacy school: not because you should be a doctor, but to see what it takes to join most any other viable career-- 18 hour rotations, crying because you're being constantly yelled at and verbally abused, insane competition, limited number of degrees that can be granted, low-paid long-hours during residency, etc...

4) If you don't already, read fiction and/or study philosophy: this should help you answer "really, is this all there is" question -- no job will help you with that.