I'm a Web Developer, a.k.a. Web Programmer, usually shortened to Developer or Programmer. I create databases, write stored procedures and write the code for applications you see on the web. I also create the user interfaces and worry about UI / UX. I work in a small team so have to do a bit of everything, including support. I spend most of my time programming which is why I usually refer to myself as a programmer as opposed to a web applications developer. The latter is more accurate.
Disclaimer: this is only my experience (have spent 10+ years in the field now). Others in my field may disagree with my observations.
Programmers are a surprisingly moral bunch who care. I think there's this idea from TV etc that we're all just a bunch of corrupt hackers, which isn't true at all. The hackers I know hack for good. Some are known as 'Security Specialists' or 'Penetration Testers'. We are taught about ethics, not just about the technical stuff. Some of us write software for cars, robots, the finance industry, etc and it has to be robust else someone might literally die.
We don't go into programming for the fame, glory or the money. In fact, I'd say we're one of the most unrecognised and unappreciated groups because, for the most part, people just don't understand what we do (including, oftentimes, our managers).
Sadly, there is still a huge imbalance in that the vast majority of programmers are men (I'm obviously one of the exceptions). I go to conferences at least once a year and there you'll find swathes of men in jeans and hoodies, living up to the stereotype. Because I don't fit the stereotype, people often don't believe I'm a programmer, it's assumed I work in admin (#everydaysexism). I am always correcting people - yes I work on the web, no, I'm not in some kind of editorial role, I built that site. Yes, I'm the architect if you like.
In terms of scandal, I'd say that we're always pushed to cut corners by managers / project owners. We hate doing this because a large part of why we do what we do is because we get satisfaction from producing something good; no-one likes to release a pile of crap, but that's often what we're asked to do which means mistakes happen. I'd also say that in every organisation they'll be at least one mission-critical legacy system that is running on ancient technology and no-one knows anything about, so no-one wants to touch it.
In every project I've worked on, UAT (user acceptance testing) is usually the phase that's cut short, meaning that when the application goes live you can be sure that more bugs crop up than should because it wasn't tested properly.
I deal with support, which means dealing with the public sometimes. I'm third-line support which means that requests go via other, less technical people before arriving at my desk. Yes, occasionally we deal with people who aren't very computer literate, but actually, the most frustrating people are those who come to us with a work request who want it done yesterday. We call these people the 'moon-on-a-stick' crowd and they make us angry.
Our jobs can be stressful so there's often quite a lot of creative swearing that goes on. I couldn't work in an office where swearing was banned, I'd implode.
Not much scandal I'm afraid.