jmorton

Also also: http://geekhack.org/

I use a Happy Hacking Pro 2. I think the tactile feel of switches are a mater of taste, and I'm not inclined to hard sell you on my preference.

Aside from a pleasant feel and sound, the keyboard's compact size makes it an ideal travel companion. It also has a control key where a caps lock key is found traditionally.

The HHK uses a Topre switch which is a hybrid between a rubber dome and a spring. http://deskthority.net/wiki/Topre_switch

* https://en.wikipedia.org/wiki/Happy_Hacking_Keyboard

* http://elitekeyboards.com/products.php?sub=pfu_keyboards,hhk...

* http://geekhack.org/ -- quite informative about various keyboards and key mods.

[edit: formatting, and more HHK details]

Availability. It is easy to get a short, memorable name with a technical connotation for relatively little cash.

"If we are hiring you because you are awesome, then you have 30 days to do something awesome"

I'm curious about how much autonomy and latitude people need to do something that breaks the awesome threshold. It seems to me that the more guided or directed someone is, the less likely the work they do will be considered awesome.

I tend to prefer more quantifiable terms. For example, having a clear million dollar improvement to the top or bottom line in one year. However, I very much agree that everyone should add something to the team.

[edit, format quote]

most garages are ill-equipped barns

To abstract and paraphrase (wildly): there are 10x work environments, and 1/10x work environments.

It seems to me that the least productive environments let "now" trump "great" – so attracting (and retaining) the top 0.1% of talent becomes necessary for a company to survive. I wonder which costs more in the long run.

When I make technical decisions, I think hard about how to keep things simple so that a reasonably smart and attentive person can use or extend whatever system down the road.

Oh, well here's the original paper that describes the system in detail:

http://bitcoin.org/bitcoin.pdf

If you'd like to mine Bitcoin, this is a pretty good guide:

https://docs.google.com/document/d/1Gw7YPYgMgNNU42skibULbJJU...

There is a coin worth $1 USD that doesn't require mining and can be exchanged anonymously. Is the cryptographic aspect a hard requirement?

http://en.wikipedia.org/wiki/Dollar_coin_(United_States)

How did it go? I'm curious to hear what did (and didn't) work.

Maybe, maybe not. This essay was published almost ten years ago...

"Wealth is what you want, not money. But if wealth is the important thing, why does everyone talk about making money? It is a kind of shorthand: money is a way of moving wealth, and in practice they are usually interchangeable. But they are not the same thing, and unless you plan to get rich by counterfeiting, talking about making money can make it harder to understand how to make money." http://www.paulgraham.com/wealth.html

But wait, how else would you make the automated tests pass?

I'm not sure how micro you mean, but Dwolla comes to mind.

https://www.dwolla.com/

Read this, or if you already have, read it again. http://www.paulgraham.com/relres.html

Done? Good.

Start coding today. Seriously. Today.

You need to find and talk to people one-on-one about what you want to accomplish. Go crash an upper division computer science class tomorrow morning, and look for students that "get it" – the kind that engage the professor, ask and answer questions. After class, pick one of them and talk to them about what you're building.

Search for new posts like "Show HN: ..." these are generally technical people that can deliver. Figure out if they have technical chops or just do launch pages.

Bonus: Get a t-shirt made that says, "Co-Founder Seeking Co-Founder" and walk around campus. Or stand somewhere.

Repeat this every day between now and Friday. If it doesn't work, I'll give you a full refund.

This looks interesting, any chance you will add Twitter or Google+ authentication soon? It's mostly just API key configuration, otherwise I would submit a pull request.

Bungie's Marathon trilogy, although not a novel, explored the inevitable digression of AI into rampancy. The terminal transcripts can still be found over here: http://marathon.bungie.org/story/contents.html

Err... WTF?

Are these tweets from people on HN, tweets with certain tags, both, neither?

...and submit things you think ought to be on HN too!

At first, that quote made me shake my head. However, it took me a minute to realize that the advice isn't "Google all the things!"

Certainly, having to search for an answer is inevitable. But it is also orders of magnitude more slow than recalling something from memory, at least for me. I think the key here is having the wisdom to know what is important enough to recall immediately versus referencing as needed.

As an analogy, and acknowledging the differences, being proficient with an editor isn't about the speed with which you look up how to do something: it's about what you can do without having to stop and think.

I would be unlikely to pay $8 per month, but I would pay commission for selling it or sharing advertising revenue. Using a TXT record to indicate a domain is for sale seems interesting too.

(edit: yes, I do have a handful of "unused" side-project domains)

For what it's worth... "PATCH is going to be the primary method for updates in Rails 4.0." http://weblog.rubyonrails.org/2012/2/25/edge-rails-patch-is-...

That's not intended to be a counterpoint. In the wild, many companies don't use Rails. :)

After reading The Handshake Deal Protocol http://ycombinator.com/hdp.html I decided to make a simple site. Keep in mind, I started working on this Friday evening so there is plenty of room for feedback.

You don't have to sign up to use this for the time being. If you want to test it out with someone else, feel free to send me something jon@agree.io

I think this could probably be handled using crowd sourcing approach within a company. The problem that I see with typical job postings is the tendency for people to over-tailor resumés (as is mentioned in the article).

I mentioned it in another comment already, but this problem is what I'm tackling with They Meet You (http://theymeetyou.com). At a minimum, I'll be using it where I work, but check it out if you want.

How it works is really simple: You can send a message to anyone that proves they work for a company, if you interest them then they can share their contact information with you.

I think it is strange to rely on HR and recruiters as a filter. I would prefer someone to introduce themselves to the entire company: tell me what you can do and what you want to do, send me a reference to any relevant portfolio, and I'll take it from there. Hopefully this approach will discourage overly tailored cover letters, who knows. The article talks about this specifically, "the trick is parroting all the words in the job description but not just copying and pasting the text"

This is pretty much why I started building They Meet You (theymeetyou.com) during my spare time. The way the site works right now is pretty simple. You can write a message that is meant for anyone at a company (@customink.com), anyone that proves they have an email address there can read it and exchange their contact info.