Peter Keše pkese

Quick notes on a rant

In project programming this hit me this week with a bug:

People (usually no F# exposure) always want to understand what &&& is ex:
- "Some test" &&& fun _ -> url "http://www.google.com"
- To explain this I teach them about infix operators which also helps with them understand why you can do "#name" == "Bob" and with |>
Its good to point out that canopy uses selenium and does not hide it at all. If you need to do something that canopy does not support, you can google for it and take the example and convert it to f#. browser is the instance of ISeleniumWebDriver
UI Automation works really well but is a pain because its sometimes more precise that people care about. It will uncover subtle bugs that people often time don't want to research and fix =(
A great property of F# is that the most recent definition of a function is the one that is used. This lets you 'override' core functionality with some that is better for you. ex if you dont like how displayed works, you can create your own version and put it in a module and open it after op

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

	See my DASH-IF presentation from October, 2014:
	https://s3.amazonaws.com/misc.meltymedia/dash-if-reveal/index.html#/

	1. encode multiple bitrates with keyframe alignment:
	ffmpeg -i ~/Movies/5D2_Portrait.MOV -s 1280x720 -c:v libx264 -b:v 1450k -bf 2 \
	-g 90 -sc_threshold 0 -c:a aac -strict experimental -b:a 96k -ar 32000 out.mp4

	My input was 30 fps = 3000 ms. If it were 29.97, then a GOP size of 90 frames will yield a base segment
	size of 3003 milliseconds. You can make the segment size some multiple of this, e.g.: 6006, 9009, 12012.