CppCon 2015: Sean Parent 'Better Code: Data Structures'

preview_player
Показать описание
--
The standard library containers are often both misused and underused. Instead of creating new containers, applications are often structured with incidental data structures composed of objects referencing other object. This talk looks at some of the ways the standard containers can be better utilized and how creating (or using non-standard library) containers can greatly simplify code. The goal is no incidental data structures.
--
Sean Parent is a principal scientist and software architect for Adobe’s mobile digital imaging group. Sean has been at Adobe since 1993 when he joined as a senior engineer working on Photoshop and later managed Adobe’s Software Technology Lab. In 2009 Sean spent a year at Google working on Chrome OS before returning to Adobe. From 1988 through 1993 Sean worked at Apple, where he was part of the system software team that developed the technologies allowing Apple’s successful transition to PowerPC.
--

*-----*
*-----*
Рекомендации по теме
Комментарии
Автор

Sean Parent speaks so much like a professor/teacher. I love his tone and pace!

brainplot
Автор

This is a really good talk; no idea what everybody below is complaining about. It's not even particularly slow compared to other talks.

DavidVaughan
Автор

This is one of the best talks I've heard in a while. you can put 1.5x or 1.25x if you think he speaks a pace that's too low for you.
Love the statement at 20:50 . It's been something I've been arguing with big O notation puritans a while back.

bboysil
Автор

In the windows hierarchy example if a unique pointer was used instead of a shared that would make it a composite object no?

This then makes class hierarchies perfectly fine. Am I missing something?

danielhawkins
Автор

Great talk! The tree representation outlined in 44:25 looks like an Euler Tour Tree, introduced in 1984.

AllothTian
Автор

Very well done. I really enjoyed this talk.

denzillong
Автор

When the moon hits your eye like a big pizza pie, that's a rotate

scottmueller
Автор

Just chiming in against the "too slow" complaints. I prefer the considered approach; better than _some_ talks where they haave death by powerpoint (too many slides) and so much to say that they say, "Comments and questions at the end, please". Often, they never get to the end. Just compare this talk to any Lakos talk. Heaven!

rocknroooollllll
Автор

'Let us form some happy little algorithms, okay?'

Skyganli
Автор

11:17 What if I told you 4 is actually greater than 3?

leonhrad
Автор

when are we going to have more chapters, can't wait lol : )

victornoagbodji
Автор

How about he uses some of these good data structures on Photoshop so that it doesn't take forever to load when it doesn't do any work that's useful to the user on startup?

warrenhenning
Автор

What is the trailing_of_begin() 51:05? Hm. Apple's UIKit has Window 'Hierarchy' and detect a tap by pass the tap down through the hierarchy

alexandersedykh
Автор

Great insights shared by Sean Parent. Must watch

nelsondavenapalli
Автор

So I feel a bit dumb after watching this. I did understand most of his ideas but up to a point in each case. Something gives up in my brain and i lose the feeling of comprehensive understanding.

batner
Автор

At 21:00 log 1'000'000'000'000 = 40 tests (in search) each of these is 200 times slower than cache-friendly linear test. So 8'000 is faster then 500'000'000'000 (average number of tests in linear search). Big O notation does make sense or I didn't get the idea of the example.

Radrik
Автор

Are there transcripts of CppCon videos somewhere?

EvgeniyZheltonozhskiy
Автор

Digital Imaging.
+Evgeniy Zheltonozhskiy Transcripts are under ". . . More".

QuentinUK
Автор

I liked this talk, but apparently this goes against many well stablished and useful Design Patterns. Self-referential classes are really nice sometimes and I think we should not make an explicit effort to not use it when the abstract model of the problems is clearly self referential.

VictorChavesVVBC
Автор

Would have been clearer with more code examples. Like the do's and don't's. But perhaps I'm just too tired for my brain to work properly.