Great talk and great tips on how to deal with software changes! Practical agility tips on changing data, code and system architecture are exemplified starting at minute 20:40.
Interesting talk on the paradigm shift in dealing with big data.
My partial time annotations in mmss (MinutesSeconds) format are:
315 some big data stats
410 amount of data will increase by a factor of 35 to 40 by 2020
450 the data deluge, G20 interest into big data
504 why the sudden explosion of interest in big data?
650 data is not thrown anymore + trend to analyse social network sentiment data
730 cost of data storage is down
755 managing "big data": parallel DB vs NoSQL system
845 Bing statistics
900 NoSQL discussion
957 why NoSQL (Not only SQL)?
1140 NoSQL is driven by developers
1220 Reducing time to insight explains interest into NoSQL
1315 NoSQL vs. SQL approach = agile vs. not
1325 NoSQL approach
1405 2 types of NoSQL systems:
1. key/value: Mongo DB, Couch DB, Cassandra, Azure tables
2. 1525 Hadoop = distributed execution framework & file system
1625 Two universes of data: structured and not
1705 paradigm shift from SQL
1840 what is Hadoop?
Great, insightful, thought-provoking and entertaining talk!
Notable ideas at minutes: 4:00, 10:00, 15:40, 18:00, 19:50, 22:37, 26:25, 28:22, 30:20, 37:20, 39:10, 41:50, 43:45, 45:50, 48:35, 50:30, 53:20, 54:05, 56:40.
Great interview and insights!
Jan 11, 2012 at 1:30 PM
Thank you @Richard.Hein for the link of the exciting Damian's older talk and thank you @Charles for this interview that reveals great insights into programming languages and physics!
My time bookmark notes in "minute:second" format follows:
0:24 the reason behind Damian's talk
2:15 comments on the positronic variable and multiverses simulation in Perl
3:15 bad habits & 2 diff types of programmers
6:50 language specialization issue
8:50 analogy with natural languages
10:45 current state of PERL
14:00 question on the push towards the "The general purpose language"
16:20 programming languages design tradeoffs
17:20 comments about Damian's keynote address and developers feedback to it
18:50 programming == manipulating reality with language == kind of same what physicists do
21:10 math as a language and analogy as a means for communicating it
Very interesting discussion on software development agile practices and tools. My time bookmarks in minute:seconds format follow:
0:37 elements in SPRINT cadence are defined for good reason. Check the "what" (Sprint review) & "how" (retrospective)
2:07 smell = what went wrong on how team works (Team Foundation Server (TFS) dashboard can help)
2:47 bug reactivations is a smell indicator
3:50 other indicators of smell are shown on TFS dashboard
5:00 question on team roles and responsibilities in the face of new technology
7:00 team perception in an agile project (cohesive team size: 6 +/- 3)
7:30 more than 9 team members ==> too many communication paths for a cohesive team
8:15 use scrum of scrums for multi-team collaboration
8:57 Convey law: organizations are doomed to ship software that reflect their structure
9:55 bring work to teams rather than shuffle people
10:43 team cohesion works in your favor
11:00 agile approach in adopting new technology: build golden thread, create prototype
12:20 @jrozenblit question on agile adoption shift in mentality
12:55 Ford assembly line philosophy compared with Toyota
15:40 what tooling can be used in an agile project?
16:15 TFS as collaboration hub
17:07 descriptive vs prescriptive metrics collected without overhead
18:30 TFS helps collection of metrics
19:30 question on user stories not perceived (valued) by customers
22:20 not everything can fit as user story
24:20 multifunctional, self-managing teams idea... eliminating the waste between developers & testers specific for traditional organizations
25:25 "no more no repro" game ("it works on my machine" paradigm)
26:25 reference to VS2010 15 scenarios used to eliminate waste in collaboration between developers & testers
27:20 tester - developer collaboration scenario facilitated by TFS
29:10 reference to resources