chrisbuchino
chrisbuchino on Hacker News
I 100% agree with this article. Quality is everyone's job, not just the QA teams' and I believe that, in most cases, developers can and should be responsible for developing, testing, and releasing their code. When developers can't "throw code over the wall to QA" because there is no QA, they will do a better job testing it themselves.
I don't buy the popular opinion that developers can't test their own code like there is some sort of magic that goes on in the mind of QA engineers that causes them to be able to find bugs that developers couldn't find themselves. In fact, I think the opposite is true - developers are better suited to test the features they are writing because they know the code and know the risk areas, where things need to be regression tested, where more attention should be placed, etc.
I do think that it can be helpful for another set of eyes to look at a developed feature and this is where pair programming can be useful. It does not need to be QA doing this.
One caveat is that this approach does not work for all teams. This works for small, agile teams where roles and responsibilities are less defined. If you fire your QA team but your developers can't test their own code because they are set in their ways of writing crap because they expect QA to find the bugs, you may end up firing your dev team too....
Wow. I couldn't disagree more. Having plumbing like MVC and ORM built-in increases speed and means less code to maintain. The selection of which one (i happen to like Django) may be a toss up, but there is huge value in a server-side framework.
I like the design but don't really get the concept other than providing feedback and others do this already, and cheaper. Idea.informer.com is completely free and uservoice.com is cheaper. Need to get either explain features better or just simplify pricing altogether.
I appreciate the pragmatism from a "devil's advocate" point of view but think this is bad advice in general. What is an entrepreneur if not a visionary and eternal optimist.
I have hired (and fired) a lot of software developers and cannot stress enough the importance of having candidates write code up-front. Having made poor hiring decisions myself by not doing this well and having "inherited" team members who whose coding skills left something to be desired, I would argue that few things are as crippling to an organization as bad programmers. Someone can be the nicest person ever, but if they don't write code well - they will cost you in time, money, and unnecessary technical debt.
I don't agree that FizzBuzz tests are the ways to screen developers though. These types of questions may give insight into IQ but I've seen really bright people be really sloppy coders. The way the problem is solved is just as important as getting the problem right and making it fast. If it isn't readable, you better hope that person does not get hit by a bus because if you need to modify it later, you're in trouble.
Great explanation. When I was drinking 10+ cups of coffee/day, I was not only not feeling perked up (pun indented) but more tired. I guess I was producing way too much andenosine.