Right, we know. Every new grad thinks it's going to be high-level design discussions. It won't be. You'll be a code monkey.

> I meant design discussions, etc.

I think that was understood (at least, that's how I read it). In a good environment at any company, your ideas will be fairly weighed against other options. Most environments aren't "good", by that definition. Don't be surprised if ideas that don't support the status quo are thrown aside.

> I'm sorry you think it is funny that I actually want to participate in the development process.

They weren't making fun of you because you'd like to take part in the process. They were making fun of you because you think it would be that simple.

> I've been keeping busy by having personal projects that most enterprise developers would probably not be able to understand.

Condescending statements like this make me glad not to know you. I've done things that some of my coworkers don't understand, and they've sometimes done things that I never have. Personal projects are fine, but there's a difference between the short+sharp bits of brilliance that you might put in a personal project of a few thousand lines and introducing a major feature into a project that has a whole file for every line that your personal project has.

Weird to see other commenters shutting you down. Mentoring younger or less experienced employees is an important part of many healthy software shops. Work environments where employees are constantly growing + learning interesting and new skills/knowledge are valued, so I would ignore the grumps here.