Not bad, not good.
Style is a lazyness issue. It's a matter of being lazy to not follow the team style, it's also a matter of being lazy to not run the code through a pretty printer to correct the style problems of others. I kind of think that future development environments will allow for customizable style settings and let each developer indent as they like, maybe even name variables as they like and when you extract the code it will format it into your style. It's an ease of reading issue and it should be personal and catered to each code reader.
Hungarian notation is a relic. It is one of the easier ways to make code harder to read. The idea is good but I think that the same if not even more information can be propagated by having good variable and function names. It's also not usually too tough to look back through the code to find the declaration, if you have to go way way back or to a different file, I think that is a much bigger problem. Tersness in general is something that kind of bugs, I understand the dislike of 30 character names but the difference between a 4 letter Hungarian symbol and an 8 letter word isn't so bad. I'd rather see "dayOfWeek" than "piDay" and I think it has more meaning in some contexts.
even variable names can be corrected for easily. sed isn't that hard to use and Hungarian notation is something that can be programatically inserted. Conventions are a good thing in so far as they help keep the lazy coders in check. Conventions are a bad thing when they try to make good programmers out of poor ones. No amount of guidelines or coding conventions will turn a lousy programmer into a good one. If your team has someone who spends an inordinate amount of time policing code conventions then they probably aren't good conventions or you're being too pedantic with them.