Staying Ahead of the Curve
summary
Shows real experiments on a 46,000-item MongoDB dataset and reports measured effects: converting code to lambdified code grows one example from 31 to 51 lines, while switching stream().anyMatch from serial (≈30 ms) to parallel stream increases latency to ≈118 ms because of thread splitting overhead. Describes adopting Spock for tests to reduce repetition, using spikes, prototypes and quarterly skunk works days to validate tech before changing production, and warns against ripping out stacks without measured benefit.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:50Welcome
- 4:03Aim of this talk
- 4:50Lambdas
- 9:10Collections in Parallel
- 15:30The Business
- 16:03China
- 17:18Business Problems
- 22:18Team Pain
- 22:54Release Pain
- 28:32Whats missing
- 30:02For yourself
- 30:35Reasons to learn
- 32:39My first Java applet
- 36:04Where to learn
- 40:58Pick something you care about
- 42:14Things you can do
- 44:05The benefits
- 45:51Slides
- 47:19Summary
- 49:04Why
related talks
26mStaying ahead of the curve
24mLightning Talks Part Three
45mFrom Zero to Live with Functional JavaScript Applications (Part 1)
38mMy first year in Scala
58mFrom Zero to Live with Functional JavaScript Applications (Part 2)
37mRefactoring the Technical Interview
46mCode is not important... or is it?
51mWe're Doing It All Wrong