We Took A DNA Test • The Test Friends

Can you handle the truth?

Check out more awesome videos at BuzzFeedVideo!
http://bit.ly/YTbuzzfeedvideo

MUSIC
Vitesse
Return of the Zombies
Fireflies
Devious Thoughts
Brooding Mind
Hard Data
Licensed via Audio Network

SFX provided by Audioblocks. 
(https://www.Audioblocks.com)

Made by BFMP www.buzzfeed.com/videoteam

GET MORE BUZZFEED:
www.buzzfeed.com/videoteam
www.facebook.com/buzzfeedvideo
www.instagram.com/buzzfeedvideo
www.buzzfeed.com/video
www.youtube.com/buzzfeedvideo
www.youtube.com/buzzfeedyellow
www.youtube.com/buzzfeedblue
www.youtube.com/buzzfeedviolet

BUZZFEED VIDEO
BuzzFeed Motion Picture’s flagship channel. Sometimes funny, sometimes serious, always shareable. New videos posted daily! Subscribe to BuzzFeedVideo today! http://bit.ly/YTbuzzfeedvideo

http://www.Cppcon.org

Titus Winters & Hyrum Wright
“All Your Tests are Terrible: Tales from the Trenches”

Presentation Slides, PDFs, Source Code and other presenter materials are available at: https://github.com/cppcon/cppcon2015

Thousands of Google engineers have collectively written about 100,000 separate C++ test binaries in the last 15 years. Not all of those was a perfect test. In this talk we’ll focus on how to write good tests and adopt a good testing philosophy, with lots of examples of what not to do (and why).

Titus Winters has spent the past 4 years working on Google’s core C++ libraries. He’s particularly interested in issues of large scale software engineer and codebase maintenance: how do we keep a codebase of over 100M lines of code consistent and flexible for the next decade? Along the way he has helped Google teams pioneer techniques to perform automated code transformations on a massive scale, and helps maintain the Google C++ Style Guide.

Hyrum Wright hates C++ less than the rest of the programming languages he’s worked with, and works on C++ library infrastructure at Google. He writes programs to rewrite other programs, and will eventually put himself out of a job. In a former life, he was an author of Apache Subversion, and still retains membership in the Apache Software Foundation. Hyrum enjoys cycling, but didn’t bring a bike to Seattle. Twitter handle: @hyrumwright

Videos Filmed & Edited by Bash Films: http://www.BashFilms.com
Video Rating: / 5

26 thoughts on “We Took A DNA Test • The Test Friends”

  1. Why are people disappointed in being just a white person? What is wrong with that? Look into your heritage, have pride in where you ancestors cam from and how much they did and sacrificed to bring you later generations to a new prosperous land!

  2. I really want to strangle the chic and the dude who were just like 'we're just basic white people'- I totally think they have no idea how many amazing and diverse cultures and historical backrounds there are within Europe! Okay, I understand it's not as exciting as learning you, a white dude are actually made up of 99 percent middle eastern and african but they didn't even give themselves or their heritage one try! I love how Daysha aproched it, it was an awsome experience and she found out about some heritage within Africa that she didn't really knew she had ancestors in! So yeah, props to Daysha!

  3. All I know is I'm a mixture of Sweden and Finland, and like a looong time ago my Family came to Sweden from Belgium..

  4. I'm Malaysian. But my grandparents on my father's side are Indonesian. Well, it doesn't change much.We're neighbouring countries and we look the same.I have never taken a DNA test before though

  5. a basic White Guy? do these guys know what big deal it is to be lets say eastern and northern European?

  6. I really want to do this, but both sides of my family are from the same region of Punjab, so I'll probably end up underwhelmed like Maycie and Shane. BUT there's a possibility of there being something cool!

  7. I'm from Poland but I for some reason have body and face features of a Mexican/Brazilian, or at least that's what I've been told by many (dark brown eyes, dark brown, curly hair, thick lips, round nose, guitar shaped body, big butt (big, not fat)) so this is very interesting especially because my great grandad came from Ukraina and I have the same surname as a Russian dancer which obviously doesn't mean I'm part Russian but it would be interesting.

  8. I kind of disagree on the "sometimes Goofus does this by running his own code twice" part (somewhere around 30:20, when talking about image comparison). As funny as it was said (no question about that) it goes too far.

    The approach is unjustly ridiculed. You can run your own code to generate results that you then check otherwise to be correct. In this particular case you might perhaps check by looking at the image whether it is OK. Or by comparing it (with your own eye or some other method) to one generated by some other software.

    And once you are sure this particular run gave correct results now you can use them as an expected result in future test runs. Which still protects you against bugs introduced by future changes. So it is useful.

    Now, having said that, it is clear that if you are too exact at comparing you suffer mentioned issues. But that is not what I'm about here. What I mean is that "running his own code twice" part doesn't necessarily have to be a bad thing. In fact it seems that sometimes you just don't have anything better than that!

    Beside all this I really liked the lecture. It didn't seem to introduce new things (for me at least) but it seems that refreshing such topics every now and then is a good thing. While the lecture itself is easy to follow and a pleasure to listen to.

  9. “All Your Tests are Terrible…" — finally, I thought, somebody's taking the words of Dijkstra seriously: "testing can be a very effective way to show the presence of bugs, but is hopelessly inadequate for showing their absence."

    What a disappointment. The only "terrible" thing here is this goofy presentation — a complete waste of time.

  10. In it's not clear, the reason for avoiding Deep Dependence is that even minor refactors could break the membership chain. The shorter you keep the chain, the less likely refactors will break the test.

  11. I believe Deep Dependence simply refers to not writing tests which depend on nested class members, i.e. Foo.bar().goo.snar(). So don't test a member of a member of a member of a object. Instead, test at most one level down in the member hierarchy, so goo.snar().

Leave a Reply to nshit 1 Cancel reply

Your email address will not be published. Required fields are marked *