4,603 reputation
1537
bio website linkedin.com/in/ethelevans
location Seattle, WA
age 31
visits member for 4 years, 5 months
seen Apr 15 at 18:27

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".


Apr
22
comment How does one build skills to be a successful software entrepreneur?
The main reason it's being postponed is because a higher priority wasn't postponed: Having children :) I have three beautiful daughters, 5 and under. I don't want to miss out on the joys and challenges of what I already have by taking on too much at once.
Apr
22
comment How does one build skills to be a successful software entrepreneur?
I updated my OP to explain why this isn't an option right now. If circumstances were different, I would absolutely be doing this.
Apr
21
comment Things to do to get better as a Software Development Group
One more question from me, also - what software development paradigm do you use currently? A form of agile, or what?
Apr
21
comment Things to do to get better as a Software Development Group
What areas are you looking at targeting? Code quality, estimation, teamwork, etc.? Definition of "better" is probably the first step.
Mar
29
comment In term of performance : while , for … Loops VS recursion
Thanks, Dan! Much appreciate the comment.
Mar
25
comment best practices in creating a product backlog in scrum
The rule of thumb is that tasks should be between 1 and 8 hours of work. If it is more than 8 hours (estimated), break it down more. Beyond that, you'll just need to try it and see what works for you.
Mar
25
comment Turn away a bug if no reproducible test case exists?
+1 for getting a record of the bug even without a repro; there's also the possibility that your testers might see the record and have a clue what happened.
Mar
25
comment Where is the golden mean between language monoculture and polyculture?
+1 for mentioning being replaceable. There is definitely a higher bar to new hires / other team members when the number of technologies starts to get out of hand.
Mar
24
comment How do you know you're writing good code?
+1 for being able to jump straight in after the weekend off. I'd say that's the biggest change I've seen in my code since college.
Mar
24
comment Can “Junior” be used in a resume?
@HLGEM - that's why I like it. I want employers to eliminate me if the position doesn't match my objective. It cuts down on poor fit interviews.
Mar
24
comment Project In A Week / development bootcamp
I disagree with having testers off-site for this. I think having dev / test work closely in this environment could have some big wins, and would make testers feel more like an integral part of the team and not second-rate citizens. Of course, I speak as an SDET
Mar
24
comment Project In A Week / development bootcamp
Agree with incentives. Here are some things that would appeal to me as a breadwinner / mother of 3: Double-comp time for overtime (2 hours off later for each hour worked, taken at my discretion). Double pay. An extra week of vacation and a bonus so I can use it to take my family somewhere nice. The key thing is that, whatever it is, it has to compensate both my husband and I - because when I work longer hours, so does he, as the SAHD; and, it has to be partly certain - not just "only if the product does well" income.
Mar
21
comment stuck on a programming problem solution
In college, this was called the "Gilligan's Island" approach - if stuck, go watch an episode of Gilligan's Island and then come back to it. They didn't mention specifically right-brained activities like drawing, but that does sound like it's worth trying out.
Mar
18
comment How is performance testing integrated into your product lifecycle?
@Evan, we're not (yet) dealing with a situation where such high levels of consistency are necessary or even valuable, and probably will never get to that point. We're not dealing with a system that needs to be highly optimized, we just need a heads-up about (a) how much traffic we can handle, and (b) if a code change causes a serious impact to our performance that we can't explain (suggesting a bug). I know one of my old teams was always fighting weird inconsistencies in context switches, however . .. sounds like something they might have been interested in trying
Mar
18
comment How is performance testing integrated into your product lifecycle?
Can you tell us something about your application? Is it a web application, desktop app, is tight performance very important? Or are you just wanting alerts for major regressions?
Mar
18
comment Why do ads for s/w engineers always say they “offer a fast-paced environment”?
I really disagree with this point of view. Fast-paced means that the team is really efficient and releases frequently. Yes, some companies abuse the phrase, probably stealing phrases they see used by successful companies which they pretend their own company is like. If the job sounds good, go to the interview and make sure you tell them your expectations for work hours in no uncertain language. Good fast-paced companies don't want martyrs, but do want efficient, reliable people with time management skills.
Mar
17
comment Why do ads for s/w engineers always say they “offer a fast-paced environment”?
@Chuck . . . thought about this a bit more, and decided the point isn't really off-topic. Thanks for the feedback, I updated the post.
Mar
17
comment Why do ads for s/w engineers always say they “offer a fast-paced environment”?
@Chuck - I agree that it is relative to the project. I'm not trying to say all projects should be fast-paced. My specific point above is that fast-paced shouldn't mean, "Constant emergencies and shoddy work", but "able to deliver significant business value frequently". What you are mentioning - that not all projects should be fast-paced - is very true, but not really on-topic (since they wouldn't be advertising as a 'fast-paced' work environment). But, yes, there are some projects that need a slower, more in-depth approach, and they have advantages as well for devs, depending on goals.
Mar
17
comment Code Documentation First?
+1 for TDD. Absolutely a better option than documenting, then having to change significant amounts of documentation if the code changes.
Mar
17
comment Not getting paid for hours you've worked?
@Frustrated: Management couldn't do that for me. I have children and a husband. Management can't do anything about my husband's irritation when I don't have time to do any housework, nor can it do anything about my kids losing touch with me (well, not entirely true . . . they could pay for a housekeeper for our family and invite my family to the provided meals when I work late, so I still get to see them at dinner - but haven't heard of this ever happening). IMO, it's up to management to make sure that people don't need to put in extra hours.