Reputation
4,538
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
16 40
Impact
~282k people reached

  • 0 posts edited
  • 2 helpful flags
  • 360 votes cast
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
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!
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?