Humans are expensive. And it's hard to find people that want to do QA, let alone competent people with a good programming background. I manage the QA department and we've had an open position for over a year. Automation is almost a necessity at this point.
Note, what I call QA might be different than what you call QA. We have one guy on our team whom I would say is a bad programmer. He does the bulk of the test result review because that's what he's good at. And even then, I'd like to automate that as much as possible and have him spend his time on other stuff. All the other positions in QA must be good programmers because that's what they're doing most of the time. Not running manual tests.
This is part of the reason why I sometimes hesitate telling people that I work in software QA. Their impression of software QA is mindless drones with no programming experience.I applied for a QA position (20/hr) in Portland that was going to turn into a QA manager(70k) job after 3 montha that oversaw romanians for Glu, a unity developer that makes celeb games (kardashians,tyra,etc).
This dickface said I was overqualified and could a better job anywhere else. I was like, wow, fuck you bro.
It's better, but not by much.I know some people who do software QA at one of the agencies. Yeah... not the brightest bulbs. I just assumed that private sector is better, though.
Okay, we are developing a WebAPI so we need to validate that the models coming in are correct.Got any examples?
Are you guys coding in pairs or are these things coming up during code review?
public class MyModel : IValidateableObject
{
...
public override IEnumerable<ValidationResult> Validate(ValidationContext validationContext)
{
var service1 = validationContext.GetService<IMyService1>();
var service2 = validationContext.GetService<IMyService2>();
var service3 = validationContext.GetService<IMyService3>();
var service4 = validationContext.GetService<IMyService4>();
bool exists = service1.DoesExist(SomeProperty1);
bool canIDoThis = service2.CheckSomething(SomeProperty2, someCondition);
bool whatAboutThis = service3.CheckSomething(SomeProperty3, someCondition2);
bool andThisToo = service4.CheckSomething(SomeProperty4, someCondition3);
if (!exists) {
yield return new ValidationResult("Can't update! Doesn't exist!");
}
if (!canIDoThis) {
yield return new ValidationResult("Can't update! You can't do this!");
}
if (!whatAboutThis) {
yield return new ValidationResult("Can't update! You can't do this!");
}
if (!andThisToo) {
yield return new ValidationResult("Can't update! You can't do this!");
}
}
}
Conceptually, I would agree with your senior developer. Database access can often be the bottleneck for performance.
Just go with the cheap one for now and buy the more expensive domain later if you feel the need.OK new dumbass question. Thanks for the web development help earlier in the week by the way, website is coming along quite nicley.
I'm thinking about buying a domian name but only .info is affordable. I've seen conflicting statements on if .info is a bad choice for search rankings, some say it doesnt matter and some say that .info is assosicated with low quality spam websites and has a search ranking penalty. It's only something like $4 for the .info so no big deal, but I'd rather get this right before I go live so I don't need to change the brand name later on.
The .com is availiable but is a few thousand dollars so I'd have to buy that in the future if the website does really well, which realistically isn't likely for a long time.
I've found it hard to think of a good brand name which has an availiable and affordable .com assosicated with it.
Failed CCNA with a 798 and needed an 810 to pass. I was the highest score of 12 people in a two week class.
It was the composite test which has like a global pass rate of maybe 30% so I don't feel bad at all.