NoahSussman
Just keep in mind that, whatever growth you've observed, the number of women in programming now is much lower than it was in the 1980s.
For some historical statistics see http://articles.washingtonpost.com/2011-08-26/opinions/35268...
Add to that the "normal" stress of doing course work and... I wound up dropping out after a year and a half. Two weeks later I was back at work as a programmer. It's been almost ten years since then and I've consistently had recruiters after me the entire time -- I've never had to actively look for work. I've met many other people with similar backstories to mine, and all of them were gainfully employed and relentlessly pursued by recruiters.
In the first 3 years of my career, I was asked about my degree in every interview. I'd say: I'm on hiatus from school due to financial concerns, but I have every intention of finishing my degree as soon as possible. This was a) true and b) enough to satisfy every single interviewer, without exception. Because all interviewers care about is your ability to deliver. As my career progressed, people pretty much stopped asking about my degree. Recently one of my managers told me (after 2 successful years of working together) that he'd never even checked whether or not I had a degree. He'd hired me solely based on my past accomplishments in the industry. I think this is a typical attitude for hiring managers, especially given the current, extremely tight market for programming talent.
School was extremely useful and I still intend to go back and complete my degree some day. But when I do, it will be for my own satisfaction, not because of the impact a degree would have on my career.
Very insightful observation. Bad code is a problem that is both technical and social. Purely technical solutions won't cut it.
Here's a very old Selenium 1.0 example that scrapes the full, rendered HTML of a page. After performing a scrape like this, I would then feed the HTML into a parser such as Nokogiri http://snipplr.com/view/7906/rendered-wget-with-selenium/
And of course now I'm wondering what I'd have to do get this working with code that targets a Web browser...
I did at one point say "there's no such thing as rolling back." This is an idea to which I'm pretty dedicated. I've seen first hand many times that using an SCM revert command to attempt to restore "last good state" is a risky endeavor, especially when a large changeset is involved.
1. For any non-trivial project, it is possible to estimate development time and/or effort with a reasonable degree of accuracy.
If on the other hand it's just the test code that's flaky, usually such problems can be alleviated by refactoring such that one passes the time function as a parameter. This is in preference to hard-coding calls to the system time in test, which imho one should never do.
Once an arbitrary time function can be passed as a parameter, one can provide a mock or fake system clock for test purposes. Ideally one would still want to test under daylight savings' conditions. But at the least this approach leaves one in a place where one can test the common 24-hours-in-a-day case without having the tests spuriously fail two days out of every year.
[1] http://www.amazon.com/gp/product/0321601912
[2] http://timothyfitz.wordpress.com/2009/02/10/continuous-deplo...
There is intended to be no end user impact whatsoever. Releasing behind config flags means that feature rollouts are decoupled from deploying code. New code runs "dark" for a long time in production. There we can log and graph and adjust its performance before it is ever visible to the user.
And of course, we can see dark features in production before they're released or even complete. This means that at Etsy we've been using and tweaking our features long before they are made public.
Since we've been closely monitoring and recording the performance of each new feature since its inception, we are highly aware of how that changes once the code is live to a known, small number of our users. Gather data, make adjustments, rinse and repeat until eventually the feature is live to 100% of users.
See also
http://codeascraft.etsy.com/2011/02/04/how-does-etsy-manage-...
http://codeascraft.etsy.com/2010/12/08/track-every-release/
http://codeascraft.etsy.com/2011/02/15/measure-anything-meas...
Etsy's engineering culture puts great emphasis on personal responsibility and taking pride in the quality of one's work. Because of that, no, there has never yet been a problem with people taking tests offline simply so they could deploy. The issue is more that tests "wear out" over time and need to be either rewritten, replaced or discarded (for more on this phenomenon see Boris Beizer and his "pesticide paradox").