Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Paradoxes and theorems every developer should know
Search
Joshua Thijssen
October 09, 2016
Technology
810
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Paradoxes and theorems every developer should know
Joshua Thijssen
October 09, 2016
More Decks by Joshua Thijssen
See All by Joshua Thijssen
RAFT: A story on how clusters of computers keep your data in sync
jaytaph
0
86
The first few milliseconds of HTTPS
jaytaph
0
320
Paradoxes and theorems every developer should know
jaytaph
0
380
The first few milliseconds of HTTPS - PHPNW16
jaytaph
1
310
compiler_-_php010.pdf
jaytaph
0
180
Paradoxes and theorems every developer should know
jaytaph
0
320
Introduction into interpreters, compilers and JIT
jaytaph
1
390
Paradoxes and theorems every developer should know
jaytaph
1
1k
Are you out of memory, or have plenty to spare?
jaytaph
0
290
Other Decks in Technology
See All in Technology
その Valkey 使いこなしていますか?
onk
PRO
5
1.6k
実践! SRE × AI - ABEMA における AIOps -
tetsuya28
8
3.1k
WasmをRustにする
sansantech
PRO
0
290
AIにシークレットを見せない、WSL2で安全な開発環境
yazm
0
310
ブラウザとサーバーから考えるAI時代のフロントエンド監視
shogo4131
3
1k
PagerDuty Tech Hub-鳴らすけれど、人は動かない
ezaki
0
180
アウトプット初心者、半年間のふりかえり
4o1sobblue
0
450
『SAR衛星データ解析入門』のご紹介とその応用
syuchimu
0
120
Webの常識が通じないHTMLメールのダークモード
teamlab
PRO
0
140
QA4AI 2026-Oct 生成AI時代の品質保証
tokuty
1
900
V8のArray.prototype.flatを最大約20倍速くするまでと、巨大OSSへの大規模コミットの道のり
riyaamemiya
0
310
10年後、Engineering 行為を剥奪されるとして、わたしたちは、どう、何を創ればいいだろうか。 / If Engineering Is Taken Away in 10 Years, How and What Should We Create?
bitkey
PRO
1
210
Featured
See All Featured
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
37
6.6k
Organizational Design Perspectives: An Ontology of Organizational Design Elements
kimpetersen
PRO
1
850
How Software Deployment tools have changed in the past 20 years
geshan
2
35k
Ruling the World: When Life Gets Gamed
codingconduct
0
400
The Director’s Chair: Orchestrating AI for Truly Effective Learning
tmiket
1
330
Designing Experiences People Love
moore
143
24k
JAMstack: Web Apps at Ludicrous Speed - All Things Open 2022
reverentgeek
1
640
Practical Orchestrator
shlominoach
192
12k
svc-hook: hooking system calls on ARM64 by binary rewriting
retrage
2
630
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
6.1k
Fantastic passwords and where to find them - at NoRuKo
philnash
53
4k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
50
10k
Transcript
@jaytaph 1 Joshua Thijssen jaytaph Paradoxes and theorems every developer
should know
@jaytaph Disclaimer: I'm not a (mad) scientist nor a mathematician.
2
@jaytaph German Tank Problem 3
@jaytaph 4 15
@jaytaph 5
@jaytaph 5 53 72 8 15
@jaytaph 6 k = number of elements m = largest
number
@jaytaph 72 + (72 / 4) - 1 = 89
7
@jaytaph 8 Intelligence Statistics Actual June 1940 1000 169 June
1941 1550 244 August 1942 1550 327 https://en.wikipedia.org/wiki/German_tank_problem
@jaytaph 8 Intelligence Statistics Actual June 1940 1000 169 June
1941 1550 244 August 1942 1550 327 https://en.wikipedia.org/wiki/German_tank_problem 122
@jaytaph 8 Intelligence Statistics Actual June 1940 1000 169 June
1941 1550 244 August 1942 1550 327 https://en.wikipedia.org/wiki/German_tank_problem 122 271
@jaytaph 8 Intelligence Statistics Actual June 1940 1000 169 June
1941 1550 244 August 1942 1550 327 https://en.wikipedia.org/wiki/German_tank_problem 122 271 342
@jaytaph 9
@jaytaph 9 ➡ Data leakage.
@jaytaph 9 ➡ Data leakage. ➡ User-id's, invoice-id's, etc
@jaytaph 9 ➡ Data leakage. ➡ User-id's, invoice-id's, etc ➡
Used to approximate the number of iPhones sold in 2008.
@jaytaph 10 Monthly Invoice IDs Monthly Invoice IDs Monthly Invoice
IDs Monthly Invoice IDs Jan 2476 2303 Feb 10718 14891 Mar 19413 27858 Apr 28833 41458 May 38644 55429 Jun 48633 55429 Jul 102606 59027 84961 Aug 109331 69715 100308 Sep 116388 80684 116020 Oct 123721 91935 132004 Nov 131241 103455 148341 Dec 139236 115276 164976
@jaytaph 11 Monthly Invoice IDs Monthly Invoice IDs Monthly Invoice
IDs Monthly Invoice IDs Jan 2476 2303 Feb 10718 14891 Mar 19413 27858 Apr 28833 41458 May 38644 55429 Jun 48633 55429 Jul 102606 59027 84961 Aug 109331 69715 100308 Sep 116388 80684 116020 Oct 123721 91935 132004 Nov 131241 103455 148341 Dec 139236 115276 164976 Estimated subscriptions Estimated subscriptions Estimated subscriptions Estimated subscriptions Jan Feb 8242 12588 Mar 8695 12967 Apr 9420 13600 May 9811 13971 Jun 9989 14525 Jul 10394 15007 Aug 6725 10688 15347 Sep 7057 10969 15712 Oct 7333 11251 15984 Nov 7520 11520 16337 Dec 7995 11821 16635
@jaytaph 12 Monthly Invoice IDs Monthly Invoice IDs Monthly Invoice
IDs Monthly Invoice IDs Jan 2476 2303 Feb 10718 14891 Mar 19413 27858 Apr 28833 41458 May 38644 55429 Jun 48633 55429 Jul 102606 59027 84961 Aug 109331 69715 100308 Sep 116388 80684 116020 Oct 123721 91935 132004 Nov 131241 103455 148341 Dec 139236 115276 164976 Estimated growth / size Estimated growth / size Estimated growth / size Estimated growth / size Jan Feb Mar 105% 103% Apr 108% 105% May 104% 103% Jun 102% 104% Jul 104% 103% Aug 103% 102% Sep 105% 103% 102% Oct 104% 103% 102% Nov 103% 102% 102% Dec 106% 103% 102%
@jaytaph ➡ Avoid (semi) sequential data to be leaked. ➡
Adding randomness and offsets will NOT solve the issue. ➡ Use UUIDs (better: timebased short IDs, you don't need UUIDs) 13
@jaytaph Confirmation Bias 14
@jaytaph 15 Hypothesis....
@jaytaph 16 Evidence!
@jaytaph 17 Hypothesis confirmed!
@jaytaph 18
@jaytaph 2 4 6 19 Z={…,−2,−1,0,1,2,…}
@jaytaph 21% 20
@jaytaph 21 5 8 ? ? If a card shows
an even number on one face, then its opposite face must be blue.
@jaytaph < 10% 22
@jaytaph 23 coke beer 35 17 If you drink beer
then you must be 18 yrs or older.
@jaytaph 23 coke beer 35 17 If you drink beer
then you must be 18 yrs or older.
@jaytaph 23 coke beer 35 17 If you drink beer
then you must be 18 yrs or older.
@jaytaph Cognitive Adaption for social exchange 24
@jaytaph hint: Try and place your "technical problem" in a
more social context. 25
@jaytaph 26 5 8 ? ? If a card shows
an even number on one face, then its opposite face must be blue.
@jaytaph 26 5 8 ? ? If a card shows
an even number on one face, then its opposite face must be blue.
@jaytaph 26 5 8 ? ? If a card shows
an even number on one face, then its opposite face must be blue.
@jaytaph Birthday paradox 27
@jaytaph Question: 28 > 50% chance 4 march 18 september
5 december 25 juli 2 februari 9 october
@jaytaph 23 people 29
@jaytaph 366* persons = 100% 30
@jaytaph Collisions occur more often than you realize 31
@jaytaph Hash collisions 32
@jaytaph 16 bit value 300 elements 33
@jaytaph rand(1,100000) 117 elements 34
@jaytaph Watch out for: 35 ➡ Too small hashes. ➡
Unique data. ➡ Your data might be less "protected" as you might think.
@jaytaph Heisenberg uncertainty principle 36
@jaytaph 37
@jaytaph 38
@jaytaph 39 x position p momentum (mass x velocity) ħ
0.0000000000000000000000000000000001054571800 (1.054571800E-34)
@jaytaph The more precise you know one property, the less
you know the other. 40
@jaytaph This is NOT about observing! 41
@jaytaph Observer effect 42 heisenbug
@jaytaph It's about trade-offs 43
@jaytaph Benford's law 44
@jaytaph Numbers beginning with 1 are more common than numbers
beginning with 9. 45
@jaytaph Default behavior for natural numbers. 46
@jaytaph 47
@jaytaph find . -name \*.php -exec wc -l {} \;
| sort | cut -b 1 | uniq -c 48
@jaytaph find . -name \*.php -exec wc -l {} \;
| sort | cut -b 1 | uniq -c 48 1073 1 886 2 636 3 372 4 352 5 350 6 307 7 247 8 222 9
@jaytaph 49
@jaytaph Bayesian filtering 50
@jaytaph What's the probability of an event, based on conditions
that might be related to the event. 51
@jaytaph What is the chance that a message is spam
when it contains certain words? 52
@jaytaph 53 P(A|B) P(A) P(B) P(B|A) Probability event A, if
event B (conditional) Probability event A Probability event B Probability event B, if event A
@jaytaph 54 ➡ Figure out the probability a {mail, tweet,
comment, review} is {spam, negative} etc.
@jaytaph ➡ 10 out of 50 comments are "negative". ➡
25 out of 50 comments uses the word "horrible". ➡ 8 comments with the word "horrible" are marked as "negative". 55
@jaytaph 56
@jaytaph 57
@jaytaph 58 "Your product is horrible and does not work
properly. Also, you suck." "I had a horrible experience with another product. But yours really worked well. Thank you!" Negative: Positive:
@jaytaph 59
@jaytaph 60 Find me on twitter: @jaytaph Find me for
development and training: www.noxlogic.nl / www.techademy.nl Find me on email:
[email protected]
Find me for blogs: www.adayinthelifeof.nl