For the last nearly 2 years I make living from doing part-time gigs. At one gig I was lucky to have a rather experienced manager and he taught me about OOP design, a bit on Agile practices and testing. That was an eye opener and put me on the right track for other gigs.
When my class mates talk 'oh man that agile thing is such shit, I just wanna write some code' I tried to convince them at first, now I just smile :)
If that's the only 'Agile' you've been exposed to, then it's perfectly reasonable to think 'oh man that agile thing is such shit'.
I believe that manifesto is the only important part of Agile. Everything else is just suggestions about how to accomplish that goal. If a particular practice does not make sense for you, in your particular situation, then it's garbage. So, look at your team's processes and ask yourself this:
If you were to reverse engineer a process that would accomplish the goals of the Agile Manifesto (e.g. the developers know what needs to be built, and there's short feedback loops between developers and stakeholders), would you end up with something that looks like what they're doing? Could you drop any part of your process and have things still work?
If you discover too many red flags -- things that serve no purpose except to "look Agile" -- then you may be in a cargo cult.