That is, "business developers" in contrast to "software engineers".
I'm at a place with them now, since returning to work after the Great Recession. (And I fear that I might be working with them, when I can find work at all that is, from now on.) I worked with them at my 2nd startup during the dotcom boom (a VB shop). During my time there I once overheard some of the senior developers talking amongst themselves and making fun of C/C++ devs for being nerds, and how in constrast they're "passionate about solving business problems", and not wanting to "get bogged down in the technology". I saw that again in the "about me" section of someone's blog years later, so I suspect it's an actual culture, that I've only bumped into a couple of times in my career so far.
They call themselves "developers", not "programmers". One person at my current shop felt the need to say out loud to the group once that she is definitely not a nerd. I concur. She's a mommie, not a technologist.
They talk about watching sports, and getting blitzed on beer. These aren't kids, some of them are early 50's, so they're not "bro-grammers", they're not the Jersey Shore of developers, they were just probably frat boys in college in their time. They're normals, not nerds They have zero awkwardness in speaking (they make BHO look like a stumbling, bumbling imbecile, in comparison, which he certainly is not), and always know what to do given the social situation.
They generally graduate with IS or MIS degrees as opposed to CS degrees. Or they get a CS degree but at one of the colleges in California's lower tier university system. Like I did*, but unlike me, they generally had to rely on a circle of friends/classmates to help them get through it. You couldn't help but notice these people; they were like wildebeests, always in proximity to their herd, for protection from carnivorous technical coursework trying to overwhelm and weed out the unfit.
*I transferered out of the upper tier system because I didn't want to pay that much/couldn't afford to (running up college debt wasn't what we did back then) . And I didn't want to work that hard, at that point in my life, since my thinking then was it was just to acquire the stupid token piece of paper to finally start my career and stuff of actual importance. (I don't totally agree with that now.)
I remember a classmate who I worked briefly with on a project I think in senior year. (At that school, sometimes larger programming projects were where you could optionally pair up with someone on it. But I never did, thinking that I'm going to have to be able to do this on my own in the real world. But some analysis & documentation assignments were sometimes mandatory pair or group assignments.) He was not a geek/nerd/pinhead/intellectual. He dressed well, spoke well, was smooth, he could be a CEO by now.
Now some people want to do something with computers in their career, not on computers. And that's fine, but they should go into QA or documentation on the way to management or whatever. For things like programmer, sysadmin, network admin, and DBA, that require real technical commitment to nerdy stuff to be able to excel at, the rest of us would appreciate if they'd stay away from those. So we can get our jobs done.
And some apparently have settled on working on computers, maybe giving up the aspirations of ever becoming a suit, but don't want to get too involved with them. A hybrid suit/developer, but 67/33 suit/programmer.
So you get what I have where I'm currently at. Managers love these people because they look and act and talk well, just like them. I hate them because I have to work with them, and on the code that they write (topics of part 2). So it's occurred to me, I'm not just a little out of place, I'm actually in a sense underemployed right now. Not as severely as if I was flipping burgers right now, but still.
In pay and also in what I can do. So I'll probably start looking in another year or so. There's a few more books I want to read to get myself at what I perceive to be a good foundation in this newer (to me) stuff I'm doing. The environment of the business developer has actually been a good place to start, as simplicity and just straightforward grunt it out coding is the rule, so it's good for someone coming up to speed in different tech for a somewhat career shift.
But like I said, since I'm doing web development in a managed language now, vice desktop development in lower-level more hard-core languages before, I fear that I'll never be working with what I consider to be my peers anymore.
Somehow, ideally, I need to find a C# shop where the propensity of them came from a C++ background and not just from Visual BASIC. And where they're not afraid of just a sprinkling of design patterns, and actual software engineering concerns like SOLID, DRY, and (gasp) OWASP. I need to think about a way of determining in an interview what kind of shop it is, without giving it away and offending in my question. (Any suggestions?)