Ricardo

"I didn't think people are supposed to downvote remarks on r/science just because they disagree with them. Total hypocrisy, especially as no one has actually made a valid counter to my arguments." - Ricardo

"TL;DR Gradle is imperative" - Ricardo

"Not sure how I have this backwards, the focus is curing individuals (whether that is part of a group or not) vs. risks to future offspring of those individuals (or groups). But I'm sceptical about your claim that "nothing would be irreversible", hence my remark about it being "too late". For example, if an unintended consequence of a genetic change were fatal or caused severe congenital deformities in future generations. I imagine the aforementioned multi-generational population trials would be possible, I'm not certain how ethical they would be and you'd still have exactly the same ethical concerns as I've mentioned above." - Ricardo

"No one mentioned violence, except you. I think your reaction is more extreme than anything I've said. Also, not sure why you keep addressing your remarks to me, I'm not on a medical ethics committee." - Ricardo

"You can impotently swear all you like at me, fortunately medical ethic committees work outside of your extreme individualistic world view and hopefully do take into consideration the possible harm caused by these kinds of interventions outside of just a single individuals concerns." - Ricardo

"Ignoring your callous disregard, changes to your genes can be shared with your offspring, and their offspring, etc. so your point doesn't really stand." - Ricardo

"That doesn't seem satisfactory if the unintended consequences of an intervention might require multiple future interventions to correct. And By the time anyone notices any harm caused it may well be too late. In other words, the benefits for an individual may well be out weighed by the potential harm caused to future generations." - Ricardo

"The risk is that such genetic changes might have unintended and harmful consequences for future generations. How can this be ruled out?" - Ricardo

"aw did you cut your hair?" - Ricardo

"The Thoughtworks Tech Radar isn't just for Java: http://www.thoughtworks.com/radar But it does focus a lot on Java." - Ricardo

"TL;DR ORMs are really bad so here is my API for mapping objects to relational databases" - Ricardo

"Not sure how your point is relevant: if the code is slow, it will be slow for both unit or integration tests. It will just be slower for integration tests because of the additional overhead of the external dependencies." - Ricardo

"Might not always be possible to install the DB locally. But the network lag referred to third-party web services, or other dependencies not running locally." - Ricardo

"I don't understand your surprise here: plenty of projects start their own instances of in-memory databases like Derby or hsqldb to isolate the data-set for integration tests. Its a common pattern. But if you don't like that, there are plenty of other factors that slow DB integration tests: deleting/creating reference data, network lag if DB isn't hosted locally, etc." - Ricardo

"That implies that the brittleness and slowness of integration tests are something that's fixable and not inherent. Starting/restarting database instances, network lag, etc., all add to the time taken to complete tests. And IMHO brittleness comes from having external dependencies on your tests. That, and of course you get plenty of other benefits from unit testing unrelated to just their stability and speed." - Ricardo

"As someone who has spent a lot of time managing brittle, slow integration tests, I'm a big fan of the rapid feedback and code rigour unit testing gives me. Tests that write to databases or rely on third-party services are slow, are highly sensitive to environmental changes and sometimes have side effects that cause other bugs. I think a lot of people mock for the sake of mocking, or rather unit test to get 100% code coverage which is pointless, but I'd rather that than going back to only unstable integration testing. I also note the DAO mock examples seem pointless at first but they are useful to provide a basic skeleton to build more meaningful tests on top of. As the code develops it may have more complex interractions with DAOs that will make these test more useful." - Ricardo

"They have a custom build system: http://www.youtube.com/watch... Google integration with Maven is very poor, I get the impression from their various projects, they don't use it much internally and have patchy support for it externally. For example, it took ages before Guice was properly available from Maven Central." - Ricardo

"Unfortunately, although its good that some MPs recognise this important issue, an Early Day Motion is fairly toothless and mostly totemic gesture. They aren't "tabled" in the sense that they will be put to vote in Parliament. They're more like announcements and any MP can make one on any subject and most are generally ignored. This is no way indicates that there is a popular movement to pardon Alan Turing: http://en.wikipedia.org/wiki..." - Ricardo

"> Currently only Google Chrome is recommended and supported. When did this become acceptable... again..." - Ricardo

"Hi, I'm the developer for m2e-android [http://rgladwell.github.com/m2e-and...]. It looks as though Basedroid has two projects, a parent POM and a sub-module Android app. This is probably why you are seeing two projects appearing in Eclipse. I'm not sure if this is a good method of structuring Android projects, I would imagine it would be best to have a stand-alone Android project without a parent POM. You might get more milleage out of using the Maven Android Archetype [http://stand.spree.de/wiki_de...] project to generate template projects." - Ricardo

"I'm not sure that's exactly the same problem I'm experiencing." - Ricardo

"I'm experiencing something very similar." - Ricardo

"Thanks for the feedback. On the subject of the Maven ecosystem keeping up with changes in Android, I would note that Google doesn't take third-party projects like m2e-android into consideration when making changes. Frequently, the re-architect the way the ADT works which breaks m2e-android almost everytime there is a new version. Unfortunately, Google can do this because they have full time developers working on the ADT while the Android Maven community is mostly volunteer." - Ricardo

"submitted by reddit to blog." - Ricardo

"thanks for the support, its really nice to hear positive experiences with m2e-android, although the guys who work on maven-android-plugin deserve a lot of praise too." - Ricardo

"I wrote m2e-android :)" - Ricardo