Are You Perceived as a Low Status Techie?
codebelay.com
codebelay.com
Er... I think if you're the vice president of a company, any company, with nearly $60 billion dollars worth of assets then you'll be invited to a red carpet event.
You're even more likely to be invited if that same company is always in the news under such hot topics as "pulls out of china due to foreign hacking", "driverless cars" and "did Do No Evil Inc., do evil?".
Honestly, you could do better than pick a Google VP as an example of a techie being treated as high status, only because they're in San Fran.
• I don't see how social capital or track record is zero sum. When you build something awesome that gives you a reputation, that doesn't take away from other people's achievements.
• Techies are low status people except for a few elite (kind of like 99% of regular people as well?). I'm not sure I understand what it means to be low status and its implications on a person.
• "Manipulating people is hard". I think you mean "managing people is hard". I understand your bias against non-engineers being responsible for product development, however just because someone isn't a programmer does not make them bourgeois to proletariat. The truth is 100% of people who get paid to work are also told what to work on.
The highly respected member of society is always a small percentage of the populace.
That said, who gives a shit? People focused on status tend to be incredibly lame.
Who cares? Well, status is a currency in many professions. The most obvious are performers. Status allows options which allows better pay or more personal projects. Status allows a programmer to talk to graphic card companies and have a hope of changing their minds. As much as I wish it were so, pure competence or brilliance doesn't buy that. You have to use the skills to acquire the status. The guy in the back room churning out just as good of code doesn't have the influence (probably some exec does in that case).
That said, I agree with you about focusing on status.
The set of people who are _most_ highly respected could be a small percent of that population depending on the amount of variance in respect people have of each other.
On a basic level, status is just recognition of your deeds. There are very few fields so glutted with great deeds that doing something new will necessarily lead to somebody else's status dropping. Pure socialites are sometimes in such a field. You probably aren't.
Social pecking order is zero-sum, but social status isn't. In some places (New York?), everyone has a low opinion of most other people. In other places (Canada? Some parts of California?), people generally treat each other with respect.
I'm glad that you think that's true for you, but it's not for 99% of coders. You are probably 20-25 with a degree and live in silicon valley or a big city.
Also, consider the fact that some people want jobs like that. They can walk in the door at 8/9am and be out by 4/5pm with no worries and few long hours. Not all techies have the drive and desire to "call the shots", shoot up the social ladder, and achieve some level of public recognition for their work. For a coder who wants to work and do hard things, getting stuck at a non-technologist company could be akin to being in coder's hell. For a coder who want's a stable 9-5 and lots of free time to do other things--like hang out with friends/family--the "low status" work doesn't really look that low status anymore. It's all about cost/benefit analysis for each individual than extrapolation to a group of people.
That's just not true. There are plenty of places that do pay fairly (and a few that do interesting work), but the places that are truly "engineering-driven" (as opposed to driven by product management or marketing) are a few in between. These kinds of places (select few groups at Google, Palantir, places like Jane Street capital) are also enormously picky about who they hire (since engineers are responsible for a lot more than implementing a PRD with commercial/open-source components).
I stopped reading. The emphasis of the article was on "coders" (fair enough) and then Marissa Mayer was bought into the equation.
No one considers Marissa Mayer a 'techie' - she's a business executive at a technology company. Two different things.
> But then, one Friday night in mid-April, Mayer was eating a bowl of pasta in her dorm room and scanning her email when she spotted a message slugged, “Work at Google?” Just as she was about to hit delete—her reflexive response to new recruiting pitches—she leaned over and inadvertently hit the space bar key, opening the email. As she read, she remembered a conversation she’d had in the fall with her mentor, computer science teacher Eric Roberts.
She had just returned from nine months in Zurich, Switzerland, where she was working with 30 other researchers to build a recommender system for the web, similar to the one Amazon uses to suggest books based on a customer’s previous purchases. As Mayer talked to Roberts in his office, he nodded and pointed upward. “There are two guys on the fourth floor who are building what you built,” he said. He apologized for not being able to remember specifics about the company they were forming, except that it had a funny name, but he thought maybe she should get in touch.
...
> The following afternoon, Mayer was interviewed first by Amit Patel, the company’s eighth employee. His opening words to her were, “I’m not sure I’m able to interview you, as I started this morning and I don’t know what we do yet.” He eventually posed a number of general computer science questions about the way memory is allocated in different programs.
http://www.sanfranmag.com/story/adventures-marissa
[1] "Glamour at Google" http://online.wsj.com/article/SB120881523314732607.html
What did people think of the article's use of opening night at the opera and symphony as examples of attaining insider social event status in the bay area? I am a bit skeptical of this since opening night is not by invitation only, seats are available to whoever wants to buy a ticket. On the other hand, most charity galas and such that end up on the social register page are also available to whoever has the money to buy a ticket as well.
I know someone who used to be a very successful fundraiser for a museum. The unwritten subtext is if you want to be 'Chair of the ball' is that it is a sizable donation ($25-$50k to start).
Money is the price to entry but navigating the social hierarchy (e.g. socialite) is something that requires acumen, not just money.
I am reminded of a Brasilian girl who moved to our neighborhood/school district in middle school (most of us had known each other since early grades). She invited literally everyone to a big party (not extravagant by any means). Quickly become integrated into the social circles. But her ongoing popularity was more due to her acumen and personality.
Attention.
If you don’t like that example, pick another: learning a programming language. What is lost by me learning a new programming language? It takes time for me of course but that time would have passed anyway.
Any product worth seeing/writing about/using has to be attention worthy enough in the first place, and then competes with other products for attention. Just like if two hot dog stands compete on the same street and one leaves. If the remaining hot dog vendor produces the ugliest nastiest worst tasting hot dogs, he does not capture the rest of the market afforded by the absence of a competitor. But if they were the two best hot dogs stands in the city, people flock to them and their market size actually grows.
It doesn't have to. Yes, an endeavor may fail to capture any attention, but in that case, it hasn't gained the person any social/track record capital.
>It’s kind of insulting when I hear the phrase "translate things into English." It puts the blame on the person on the team most equipped to solve the problem. The person, who wants "things translated into English," is the problem, not the coder.
If all us coders get together and decide to walk out if we don't get respect like the highest status careers, then we will get it. Usually techies are not concerned with being seen as baseball stars or heros, we care about contributing to society and making as much money as possible. It's supply and demand.
In any case, one shouldn't need to demand respect, one should command it. The difference is that the former is impossible unless you equate fear with respect, the latter is a natural result of the transferability (or other relative metric) of your talent/skill/ability.
As a coder, I'm sure you understand separation of concerns. Well, it works the same way in a sufficiently large company. Coders can't and shouldn't be doing everything. Let's say a build vs buy decision needs to happen. Someone needs to be mindful of the budget and time to market. Sometimes you want a feature that might step on the toes of a partner. Someone needs to keep up with those relationships. If you left it up to coders, they might spend all their time coding things that interested them.
The problem arises when the people making decisions don't listen to the recommendations of the technical people. But that does not mean that technical people necessarily need to run everything.