I wonder why there's such a huge gap between my experience and this professor's; undergrad vs. graduate school? CS vs. business school? Moss vs. Turnitin? Arizona vs. New York?
358 karma · joined August 31, 2009
I wonder why there's such a huge gap between my experience and this professor's; undergrad vs. graduate school? CS vs. business school? Moss vs. Turnitin? Arizona vs. New York?
So, I don't think it's possible for us (people who work at companies whose product is technology) to help create jobs for people without tech skills.
I've now got as much skin in the game as him - neither of us is making a salary yet.
There's no one way to find your technical cofounder - we're all motivated by different things, and maybe what you've already got will click with someone. Just keep meeting people and putting your idea and self out there.
Then there's the solipsist point of view, which is to say, it doesn't matter that someone else thinks you are deluding yourself, because all that is knowable is in your own mind, so you aren't capable of validating anything anyway.
Either way, the experience is validated, to one's self or to the world.
The other day, after upgrading, I could not for the life of me figure out how to bring up the number key pad while on a voice call. I needed to "press 1 for X", but I couldn't do it. This used to be easy in Old Skype.
If a power user like myself can't figure something out, chances are it's too difficult or hidden for casual users too.
http://adb.nikkei.co.jp/ad/logo/2008b/NikkeiWeekly080722-NNI...
http://en.wikipedia.org/wiki/Hedy_Lamarr#Frequency-hopping_s...
A wise friend once told me "If someone else can do it, you can totally do it."
For workflow tasks, Automator.app on OSX is pretty great, even for non-programmers. There's probably something analogous on windows/other OSes.
For document generation... that seems like a fun weekend hack. I'm imagining some kind of more configurable madlibs-style app.
In my experience, the time it takes to become proficient with an existing framework is generally a lot shorter than writing a framework yourself. And, generally, the existing one will have been vetted by thousands of people before me.
Most the points on the list have a subtlety, I think, and are non-obvious. They all require imagining yourself in the marginalized minority's shoes. They aren't the glaringly obvious examples of sexism that (really infrequently) happen, like Aimonetti's slides. That's where the real work can be done, because eliminating obvious sexism is the easy part.
"it suggests this is a problem we (HN programmers or some other applicable group) can and should solve."
But then you said:
"stop whining and start trying to change something."
This list is absolutely on the right path - by recognizing and bringing attention to a list of privileges that male programmers might not have thought of, this list (and the people behind it, following in the footsteps of many other feminist/egalitarian privilege lists that have been created), they are doing something about the problem. Raising awareness is action - arguably the most important action in ameliorating sexism in this space.