1,024 karma · joined May 29, 2013
https://www.sharelatex.com/project/534230c0234f079f3ce526fa?...
Theorem 1.10 states "If S andT are countable sets, the set S ×T ={(s,t) : s∈S,t∈T} is countable." and is proven using a diagonal argument.
Suppose a submarine is moving in a straight line at a constant speed in the plane such that at each hour the submarine is at a lattice point. Suppose at each hour you can explode one depth charge at a lattice point that will kill the submarine if it is there. You do not know where the submarine is nor do you know where or when it started. Prove that you can explode depth charges in such a way that you will be guaranteed to eventually kill the submarine.
If there's interest, I'll post my solution. My proof actually gives an overview of what order to bomb points in, but I have no idea what it would look like if you plotted out, say, the first 100 or 1000 points. I'd be curious to see someone implement it.
http://ycombinator.com/newsguidelines.html
I think the sheer number of comments indicates that the community certainly finds this "interesting." It's just a matter of keeping the comments civil and high-quality.
-@notch on twitter.
Right now the functionality is pretty basic. It works very well for compiling includes in a flat file structure, but doesn't copy your stylesheets or JS into the build folder (and flattens your structure if you have nested files). These are things I plan to implement soon (or you can now!). I also plan to implement support for the Listen gem so that it'll automatically compile on detecting file changes, rather than requiring manually running it.
[0] https://en.wikipedia.org/wiki/Cockpit_voice_recorder
[1] https://en.wikipedia.org/wiki/Flight_Data_Recorder
edit: just about everyone's beat me to it!
edit: ignore the below, just got to this explanation in the book!
> The entire Crypto 101 project is publicly developed on Github under the crypto101 organization, including this book. https://github.com/crypto101/book
----
Excuse me if this info's on the website (I can't get to it right now, HN "hug of death" it appears), will you be open sourcing contribution to the book? I'm not saying it's necessary or that I even recommend it, just curious about your authorship model (and noticed the CC license at the beginning).
Also, did you make the book in LaTeX (or some TeX variant)? If so, will you be sharing the source? I always love looking at other people's TeX documents.
(Speaking, naturally, only my own opinions here:) I'm excited for the possibilities of growth that it'll offer the company, but also a little nervous about how it'll affect the Nest's ability to serve their other (previous?) clients. I personally signed on with Rdio because I loved the deep Echo Nest integration—I hope that's not going anywhere.
Looking hopefully, but anxiously, towards the future.
edit: available only to members, unfortunately