News for hackers. Stuff that matters.

WCC

There are so many other factors involved that the number of words barely means anything.

Culture, audience, complexity... These things all dwarf understanding when it comes to expressing an idea.

Re:Ask HN: How much data can a 5MB database store? on Tuesday August 17, 2010 @08:04PM (#1612839)
That was going to my answer, too, so I'll elaborate a bit.

It depends on the format of the database and the contents as well. If all you store is a single 4.9MB image, then there's not much overhead. If you store thousands of short text records, then each one can only have a little data, and will have a lot of overhead.

Re:Proof That Game Theory Isn't Fully True on Sunday August 15, 2010 @02:12AM (#1604692)
Not everyone acts according to their best interests. That doesn't mean game theory is wrong.
Re:Practical Ways to Become a Great Designer | UX Movement on Saturday August 14, 2010 @11:56PM (#1604556)
That's a really long video to say something so simple:

You need to practice your craft away from work if you want to be great at it.

He lists a bunch of reasons why, and spends a lot of time driving them home... But I think the time is wasted.

Good designers/creators/developers/etc already do their craft away from work. Bad ones have a million excuses why they can't or won't. I can't see him changing anyone's mind as to whether they hone their craft in their free time or not.

Re:ASK HN: How to be a better programmer? on Sunday August 08, 2010 @05:41PM (#1586244)
- Practice. Yeah, other people said it. It's that important.

- Find a mentor. You'll improve slowly just from practice, but finding a mentor will force you to get up to their level at a much quicker pace.

- Read things. Books, blogs, whatever. If you have an active interest in it, read it.

- Use new technologies. Never heard of Node.js before? Stop and figure out what it is. Try it. Even if you hate it, you will have been better for learning about it. (Node.js is just an example I pulled out of thin air. This applies to ANY new programming thing you read about and is new.)

- Get a job. Even if it's a crappy programming job, nothing makes you learn faster than having a boss telling you to do things faster and better.