HN user

semmons

806 karma

[ my public key: https://keybase.io/semmons99; my proof: https://keybase.io/semmons99/sigs/Gqu_a1vr_DVCcEhaDd-g5lK-EEsMt5w7ki-q6o0fb58 ]

Posts73
Comments21
View on HN
robots.thoughtbot.com 16y ago

How To: Take Notes Like a Champ

semmons
3pts3
blog.heroku.com 16y ago

NoSQL, Heroku, and You

semmons
6pts0
blog.heroku.com 16y ago

Teambox on Heroku

semmons
2pts0
www.pragprog.com 16y ago

PragPub #13 (2010/07)

semmons
4pts0
lovehateubuntu.blogspot.com 16y ago

If Cantor Were A Programmer...

semmons
4pts0
lovehateubuntu.blogspot.com 16y ago

Statistical vs. Practical Significance

semmons
1pts0
www.pragprog.com 16y ago

PragPub #12 (06/2010)

semmons
2pts1
blogs.discovermagazine.com 16y ago

Crazy violent explosion shoots out two cosmic bullets

semmons
3pts0
sheddingbikes.com 16y ago

Announcing MulletDB (Formerly NoNoSQL)

semmons
40pts13
www.smbc-comics.com 16y ago

There Once Was an Ugly Duckling

semmons
1pts0
www.engineyard.com 16y ago

Everything You Need to Know About Unicorn

semmons
1pts0
www.rubyinside.com 16y ago

The Why, What, and How of Rubinius 1.0’s Release

semmons
2pts0
bugsplat.info 16y ago

Building Battle Bots with Clojure

semmons
5pts0
blogs.discovermagazine.com 16y ago

Why does the Moon look so huge on the horizon?

semmons
36pts11
blogs.discovermagazine.com 16y ago

How will Jupiter hold up his pants?

semmons
2pts0
www.universetoday.com 16y ago

Things that Saved Apollo 13

semmons
46pts2
lovehateubuntu.blogspot.com 16y ago

Computing P-values

semmons
4pts0
lovehateubuntu.blogspot.com 16y ago

Introducing MinMVC

semmons
2pts0
lovehateubuntu.blogspot.com 16y ago

A Little Intro to Time Series

semmons
23pts2
adam.blog.heroku.com 16y ago

Startup Lessons Learned

semmons
35pts5
axian.tumblr.com 16y ago

Thoughts on Horses

semmons
28pts9
tbaggery.com 16y ago

A Note About Git Commit Messages

semmons
4pts0
blog.heroku.com 16y ago

Heroku (YC W08) Update & Roadmap

semmons
5pts1
lovehateubuntu.blogspot.com 16y ago

Discovering Fractals: Brownian Trees

semmons
1pts0
skepticblog.org 16y ago

Why Are Nerds Unpopular, An Alternative To PG's Essay

semmons
58pts77
lovehateubuntu.blogspot.com 16y ago

Discovering Fractals: The Lorenz Attractor

semmons
17pts2
adam.blog.heroku.com 16y ago

Beanstalk, a Simple and Fast Queueing Backend

semmons
11pts1
github.com 16y ago

Smart HTTP Support - GitHub

semmons
35pts7
blog.heroku.com 16y ago

Heroku (YC W08) Supporting Big Data: Part 1

semmons
1pts0
lovehateubuntu.blogspot.com 16y ago

Testing Random Numbers

semmons
3pts0

Amazon is not the publisher, Betascript Publishing is. Looking at their site, it seems that what they do is gather articles and bind them together (with or without permission, I don't know). Here is the text from their About page:

Annually, millions of works are written worldwide in the research industry. Enterprises and scientists would be especially interested in these ideas; nevertheless, up to today, most of this work is shelved as a result of high costs. Betascript Publishing specializes in the publication of such works and uses commitment and the latest technology in order to make the invaluable work of such researchers available worldwide, quickly and efficiently.

No you're not. That's why every time I see one of their interviews, I grab the transcript and dump it to google docs for everyone to use.

I would pick the Kindle. It hits all four of your points and will have the greatest battery life, especially if you don't use the wireless connectivity.

[dead] 17 years ago

I often times feel like this when I am told by upper management to try and push a change on a vendor that will mitigate a problem specific to our architecture. Most of the time the support person is gracious, saying they will take it to their product development team. But, deep down, I know that as soon as the team hears the request/suggestion it goes straight to the waste bin.

Lisp is sin 17 years ago

> But I'm willing to bet that a lot more developers will be able to understand this since this is in a programming language they understand well.

This is one argument I don't buy. He talks about the Mort programmers never being able to understand Lisp. I am willing to bet, any Mort programmer who looked at this C# would not be able to understand it. I'm sure they could take advantage of it, but write it themselves, I don't think so. And anyone who could write this, can grasp Lisp themselves.