4,545 reputation
1434
bio website linkedin.com/in/ethelevans
location Seattle, WA
age 30
visits member for 3 years, 10 months
seen Apr 9 at 23:35

SDET with 5 years of experience in software testing & BS in Computer Science. I'm also not very good at filling out "About Me" sections. I'm not as much of an expert as I'd like to be, so am trying to soak up knowledge as fast as I can while balancing work and "real life".


Jun
20
comment Jobs that use programming which aren't in the technology sector
No, it isn't. I'm trying to convey that I am not familiar with the research world, and so what the author says may be true there - but it also may not be true. I wouldn't know. In the non-R&D business world, and IME, what the author says isn't true. But I know enough to know that research follows different rules, and that's probably where most of the cross-disciplinary coding is.
Jun
15
comment Bugs keep reappearing in our GUI software during development. How should this be addressed?
You might get better answers at sqa.stackexchange.com, since building maintainable automated UI tests / deciding when to automate is really a tester "thing"
Jun
15
comment TDD: What happens before the first unit test?
Thanks, that's very helpful. How does this work on larger projects with multiple developers, though? While I'm working on personal projects w/ TDD, my goal is to learn how it actually works when used in a team.
Jun
15
comment What was Java enterprise programming like before Eclipse?
Vim vs. Emacs FTW!
Jun
15
comment TDD: What happens before the first unit test?
Could you elaborate on "Before you write your first test, you have to think about what your first bit of functionality is going to be, and what your program would look like if that functionality were working."? How much should I work out before starting? At what point am I over-designing and losing the benefit of letting my unit tests drive my design? I assume I don't want class diagrams, that should be driven by refactoring, right? But this example sounds like "Have an idea, invest 15 seconds of thought, then write a test." Is that really all I want to do?
Jun
15
comment TDD: What happens before the first unit test?
I like this. It's a very clear process I can follow: List features, make a sub-list of user stories for each feature, make a sub-list of tests for each user story. I'll give this process a try.
Jun
14
comment Interview approaches and questions for a software developer intern
Yeah, I use "guys" all the time for mixed-gender groups, e.g., "I'm one of the guys in the Corporate Platform Group."
May
23
comment Do testers have to look at source code?
+1 for tester code reviews, and wish I could +1 again for the excellent paper!
May
20
comment How do you write tests for code that depends on concrete external implementations that can't be mocked?
+1 for hiding untestable code. Then you can do manual tests until you work out what needs to cross that interface to get the right result, and unit test for that being generated properly to get your regression unit tests.
May
17
comment Doing a passive job search while employed, dealing with the barrage of messages from untargeted Recruiters, HR people?
I disagree that using recruiters is a bad sign. Morale went up in my company once we quit making the PMs and top devs spend hours a day sifting through resumes, mostly poor-fitting with certs and padding but no real experience. The recruiters cut out the 90% that was crud that didn't match what we wanted and we got more candidates for phone screens and on-sites who were generally qualified per week when we started working with the recruiters.
May
17
comment Doing a passive job search while employed, dealing with the barrage of messages from untargeted Recruiters, HR people?
One trick if you just don't like recruiters but find a good position: Copy a distinct line of text from the ad and search for it. Often you'll find the same ad on the company's website, and then you can apply directly.
May
13
comment Are testers considered low profile?
I find this amusing, too. SDETs have better job security than SDEs because there aren't that many of them. That's part of why so many companies end up making junior SDEs work as SDETs. Sure, cross-disciplinary experience is also great . . . but I've never yet heard of a company forcing an SDET to work as an SDE for that cross-disciplinary experience. They're really doing it because they can't get enough good dedicated SDETs.
May
13
comment How to get a job with no experience?
I would agree with unpaid work being a last resort, and even low-paid work should be avoided until you are sure there is nothing better. Your internships and first job set the tone for your entire career; you don't want to be haughty, but you also don't want to sell yourself short. Start with high goals, and lower your expectations gradually. Otherwise, good advice.
May
11
comment How do I design an arbitrary system in an interview?
I think simplified UML would be a common part of the answer. Server diagrams could also show up. The key thing is to show that you aren't stymied by the size of the problem and that you can move smoothly from a vague concept to a real architecture (with concrete - not vague - problems to be solved). And then communicate that architecture. The interviewer might also be listening for whether you go for current best practices or head towards solutions that are out-of-date.
May
3
comment How do you identify “edge” cases on algorithms?
One more thing to add . . . analyze the code and look for special cases in the code. If the developer handles 0 to 13 differently than 14 and greater - maybe the dev is using different algorithms for small and large values for performance reasons - you have edge cases at 13 and 14. +1 for great list.
Apr
29
comment How important is working with a team?
Great response! You don't know what you don't know, and it's hard to beat working next to senior devs at this point in your career. Best boost you'll get is working closely with someone way more experienced and better at coding than you are. Also, don't underestimate the power of a recognizable name on your resume. It opens doors. If you are concerned about the team, ask for informal phone conversations with some of them before you accept.
Apr
27
comment Bridging the gap between computer science research and software engineering
@Berlin, I think that's the problem frameworks are trying to address. Either way, we're moving in the right direction. Think about how much genius, etc., used to get wasted filing records in cabinets!
Apr
22
comment How does one build skills to be a successful software entrepreneur?
Thanks, every answer was useful - wish I could accept more than one. I'm going to read up on business, start hanging out on "onStartups.com", and see if I can throw together a very simple mobile app over the next year or so. Longer term, I'll start looking for incubator programs / entrepreneurship training and see if I can continue releasing small products (probably getting gradually larger as I get more experience and the kids get older) until I'm ready to stop my job and take some time to focus on one larger business idea. So now to come up with a business idea that's 'fun-sized'.
Apr
22
comment How does one build skills to be a successful software entrepreneur?
Hrm . . . I hadn't thought about 'micro-products' like mobile apps that do just one simple little thing. That's a great idea. I could probably pull off something very, very small in a year, and releasing even a very simple product would be great experience.
Apr
22
comment How does one build skills to be a successful software entrepreneur?
Mmm . . . thanks for pointing out OnStartups.SE, seems like a great resource. Thanks, this is really handy.