“This is what we have, and this is what we’re going to win with.” How to be a web developer, graphic designer, u/i research, sysadmin team, as one person.
- Plan and prioritize your site goals and organize your plan of attack accordingly.
- Version control is necessary (!) even as a one-person developer.
- Set realistic time milestones
- Accept and move on when you’re not PERFECT.
Notes: Cheap and easy U/I feedback. Buy a bunch of non-geek friends a pizza and watch them tear your site apart. Find the community in which you can ask/receive help … LUGS, Regional events, IRC.
Pitfalls for the solo web team include featurtis creep … feature curve -> too many features can actually diminish usability.
Observation: Finding it easier as a female to ask another female for help. RTFM issues. Discussion on gender hiding, yes, it happens for various reasons.
Some resources: drupalchix, phpwomen, .51, women who tech.
Multidisplinary approach draws from resources in other fields. Quick poll … how many came from a non-tech field into tech? Many. (Flosspols point of interest … acknowledge non-coding contributions as just as valuable as code contributions as a way on increasing diversity.)
KD personal path … came from art field and followed inclination into web development, and here she is.
Gender activitism in Ruby started with RubyCon in SF … presentation would have been different with 150 men/150 women as opposed to 292 men/6 women ration. Increasing gender diversity means changing the environment by changing the ratio.
1 year ago 2% women, this year 18%, target 50%
Process in Ruby community: Set goals, Do events, Cultivate people. All three necessary, most just focus on ‘Do Events’. Important to work on attainable goals, i.e, increase participation for monthly meetings. Picked specific target, 1) women who were not programmers, but worked at companies who were tech focused, and tech women who have been out of the workforce for a period of time and were looking to update skill sets.
Logistics tips: Offer childcare. Technical women are more likely to have a technical spouse (Anita Borg Inst statistic) and would be likely to attend same events. Just the fact that it’s offered sends positive message -> low cost high signal message. Social component important … after party incorporates women into wider community.
Visibility -> put name on events makes a difference, contribute to mailing lists, and do talks.
Expected outcome: After year more women have attended monthly meetups, and more women at events.
Unexpected outcome: mailing list activity has picked up with more signal than noise., more interesting talks, more women giving talks, and MEN are feeling more comfortable in not knowing everything. (Guess not wanting to appear ‘dumb’ is one of those universal traits , and events have become more newbie friendly.
Pretty In Print
Associate Publisher, Linux New Media
10 Tips for Getting Published
1. Don’t be afraid!
2. Writing samples optional
3. Know your topic
4. Know your publication
5. Know your editor
“Don’t try to be clever. You use Linux so you already are clever. Write about the trivial things . . .”
“Revise, Revise, Revise!” –Rikki Kite
7. Submit . . . & wait
8. Be clear on compensation
9. Know your rights
“Review your freelance agreement carefully.” –Carla Schroder
Rikki Kite gave a beautiful and concise talk and actually intended this topic as a lightning talk, so it was quick but very informative.