The Myth of the Non-Technical Startup Employee

No, no, no, no and no. Stop it. Pattern matching isn't science. Stop pretending it is.

https://medium.com/best-thing-i-found-online-today/8178b2794...

To be direct: Pattern recognition is bullshit voodoo pseudo-science masquerading as objectivity and meritocracy. It’s sexism, racism, ageism, homophobia, and xenophobia dressed up as science. It sickens me.

I can't upvote this enough! It's why I find jobs where what I do (engineering) is not the core product less rewarding on the whole.

> I was repeatedly asked if an engineer was around to explain the product before I had a chance to say more than hello.

> let's focus on the other assumption: that because a person has a non-technical role, she is fundamentally incapable of assessing whether she is able to answer your question.

> While we’re at it, I’d like to dispel the notion that people in non-technical roles don’t have technical skills. From the VBScript and complex spreadsheet wrangling required to perform analysis of key organizational metrics to mastery of numerous different specialized softwares and systems in order to perform basic functions of the job ranging from accounting to people operations, non-technical employees must have a bevy of technical skills at the ready every single day.

It's difficult to recognize what you don't know. As an engineer, I feel like I didn't understand jack a year ago. A year from now, I'll feel the same way about my current level of understanding & skill. Between now and then, I'll speak with confidence about topics I think I understand but probably don't fully grok.

Earlier in my career, I was "semi-technical" with more [technical] experience than the OP. Looking back, I really didn't understand the product to the extent I thought I did.

A little knowledge can be dangerous. YMMV.

edit : if you down voted, care to explain?

Understanding your company's product, marketing, financials, hiring, and business strategy makes you an _incredibly_ valuable employee (though perhaps difficult to describe with a job title).

An employee like that shouldn't be spending much time ordering food and cleaning. Those things can be outsourced to people who can do them at scale for many companies at once, at a much lower rate.

At my startup we've used ZeroCater (Food for events), HomeJoy (Cleaning), TaskRabbit (Odd tasks), Zirtual (Scheduling meetings, booking flights), and Advsor (Accounting & Billing).

We also have a full time remote assistant that does things like coordinating team outings, ordering new tshirts, researching stuff, spreadsheet jocky-ing, etc, etc. They would also order food for us if we didn't have it provided at our co-working space.

I hope this comment was helpful and not condescending. I do some business ops work myself in addition to writing code and consulting. As the longtime only-female, I too had to deal with the assumptions about my role (outside the company, not inside).

All of these tasks are important and need to happen for a company to run successfully, but they don't all need to be done by an "Office Manager" just because that's how it works at some startups.

I stated outright it was sexism and asked more women to relay those situations so people do understand it. I was just stating from the side of that not all that might be deemed sexism was always meant as such. i.e. usually it is stupidity over arrogance which some assume the latter and more often it is the former. Almost all misunderstandings stem from some aspect of this. Where people are stupid, they need to learn somehow, examples help.

But living in a world with 99% of people not being technical (unless you are at work) you have to assume most people are not and talk to them in that way, nothing to do with gender really. In that aspect talking in a way that a person understands is polite (completely ignoring is another thing entirely -- a good speaker involves all). Once that person lets it be known that they are technical then a new door opens up and you can drop some acronyms. Any person will tune their message to their assumed crowd otherwise they waste alot of air. If you go up to 100 people (or women) and just start talking in programmer/technical jargon most of them will look at you funny. I talk to dudes I work with differently that are in business and programming as well. I don't talk down to them in any way, I communicate. If they get it, all engines ahead, if not, they ask for a simplified version, same deal with aspects of the business on the flipside.

What I see is also a problem in the sexism journey is that sometimes people that are understanding and do see the problem get pulled into it in ways that make them look bad. I almost didn't post the message above because I knew I'd get some of this even though I 100% agree. So they stay away from it, just because there may be gender issues doesn't mean there isn't some give and pull on both sides to help it along.