jeffdavis

312 ms·

2551.
by jeffdavis 16y ago
"It's certainly a common Erlang deployment pattern where no one Erlang process needs more than even a handful of megabytes necessarily, but the system as a whole runs past several gigabytes by sheer scale of accumulated processes that thems
2552.
by jeffdavis 16y ago
"Not that this isn't amazing, but is it really toughness and bravery to do what's necessary to save your own life?" Yes.
2553.
by jeffdavis 16y ago
Well, some amount of self-promotion is necessary for success almost anywhere. Sure, if you come up with something miraculous, then it markets itself. But otherwise you have to make sure that the right group of people knows about it or your
2554.
by jeffdavis 16y ago
Can you point to a specific message?
2555.
by jeffdavis 16y ago
"selling what you believe you can do" People buy from startups knowing that you're a startup, usually. There are always ethical issues when it comes to selling, but I don't think that "ability to execute" is the biggest one, as long as you
2556.
by jeffdavis 16y ago
"the different engines provided are for different tasks" You should think of them more like separate DBMSs that are tied together in one system. The semantics change depending on the storage engine, so they aren't just drop-in replacements.
2557.
by jeffdavis 16y ago
DBMSs are complex things. Any DBA proficient in both systems can show you a query (and table layout) in PostgreSQL that outperforms InnoDB and vice versa.
2558.
by jeffdavis 16y ago
"How many people believe otherwise?" That's kind of the point, I think. Stating an obvious fact is often used to suggest some kind of action. And it sounds like that happened here. I feel bad for the guy, surely. He made a small mistake and
2559.
by jeffdavis 16y ago
It's not as much about clarity of communication as it is clarity of thought. Also, a program is not a single message being sent to the computer. A program is revised over time, and testing helps ensure the integrity of the program through r
2560.
by jeffdavis 16y ago
To build a culture of quality, the best way to start is a mandatory code review system. Code doesn't go in until it's peer-reviewed by at least one person. Code review is critically important: it instills a different attitude in the program
2561.
by jeffdavis 16y ago
Languages with powerful type systems do allow the programmer to ensure consistency without duplicating code, to a degree. And I suspect that it does reduce the testing burden substantially when used correctly. There will always be some need
2562.
by jeffdavis 16y ago
Interestingly, the same thing could be said about using a powerful type system or not. It's easy to assume that the compiler errors you are getting are just wasting your time, forcing you to put arcane type declarations, annotations, and co
2563.
by jeffdavis 16y ago
I am having trouble reconciling the following two quotations: "[MongoDB is] so simple and natural to use from dynamic languages" and: "In my test code, I had an 'async' remove() call (ie. I didn’t wait for it to finish) and was then inserti
2564.
by jeffdavis 16y ago
Honest question: does that really include all of your data? All the messages, comments, friends, any friend ID or contact info (email addresses, IM names, phone numbers, addresses, etc.)? In other words, is it enough data that you can just
2565.
by jeffdavis 16y ago
"something like [Facebook] is practically required for most women to communicate over the internet." Can you please elaborate? I honestly don't know what you mean. Do you mean that women prefer to communicate in this particular medium?
2566.
by jeffdavis 16y ago
I don't think there is any common ground between the FSF and Facebook. The FSF might use a different presentation for greater effect; but ultimately, the message is: the FSF doesn't want Facebook around any more. Period.
2567.
Exclusion Constraints are generalized SQL UNIQUE(thoughts.j-davis.com)
2 points by jeffdavis 16y ago|0 comments