ef4

38 ms·

331.
by ef4 12y ago
That's a misleading way of comparing them because the doctor has radically higher startup costs in both time and money. Once that's factored in, the doctor still has higher lifetime earnings, but not nearly the 4x you're poin
332.
by ef4 12y ago
Here's something equivalent for even less money. I have one, and it works great. I actually used a tabletop from Ikea for the desk surface: http://www.amazon.com/gp/product/B005NJUQVG/ref=wms_ohs_prod...
333.
by ef4 12y ago
I had some relatively steady long-term clients. Sometimes they were slow to pay, but they always paid eventually. I had enough cushion from the previous job not to worry too much about short term cashflow. Otherwise it can be a problem.
334.
by ef4 12y ago
I don't think it's too difficult to find such opportunities if you're willing to be a freelancer/consultant. I've gone for periods at as little as 5 hours a week. In that case I was mentoring more junior programmers
335.
by ef4 12y ago
But they're already paying for these underground transit options. So there's clearly some combination of pricing and shared routes at which customers can afford it and the providers can still make a living.
336.
by ef4 12y ago
No, you price more difficult routes higher , so that they can still be served at all.
337.
by ef4 12y ago
>That's not racism, that's just the reality of how you make money as a cab driver. ... under a bureaucratically-controlled pricing structure that ignores reality by forcing you to price all those routes the same.
338.
by ef4 12y ago
Far more commonly, well-organized criminals use the info to fraudulently bill medicare or an HMO.
339.
by ef4 12y ago
http://econweb.tamu.edu/common/files/workshops/PERC%20Applie... http://www.sciencedirect.com/science/article/pii/S0304387813...
340.
by ef4 12y ago
> having such features in the standard library makes a big difference for a newcomer. And not just for the newcomer. The biggest benefit is that your dependencies and your dependencies dependencies can all compose better when they'r
341.
by ef4 12y ago
Thank you for responding before I could and saving me the link gathering effort.
342.
by ef4 12y ago
I'll grant your premise, for the sake of argument. So where's the big negative fallout? If the set of unemployable people has been growing for centuries, where is the mass starvation and misery? How can it be possible that the 20t
343.
by ef4 12y ago
This same argument has been repeated for literally centuries now, and it always turns out wrong in the long run. Imagine if we could run the entire world economy with only 5% of the workers. Pandemonium? No, it has already happened before.
344.
by ef4 12y ago
Ah, the classic paternalistic argument. It's deeply appealing to many people's preconceptions. But a growing body of experimental results call it into question. When you actually conduct the experiment -- a randomized controlled t
345.
by ef4 12y ago
It's the government's own term, used by nonpartisan entities like the CBO. If anything, "welfare" is now used as a more politically loaded term. It's almost never used anymore without attaching a negative connotatio
346.
by ef4 12y ago
It's also critically wrong in understanding technology: "one run of a time machine, with a printout of Wikipedia, would be pretty much all the real 1950 needed. Send the technology back to 1945, and you'll have iPads by &#x2
347.
by ef4 12y ago
That particular problem has an easy technical solution. Just serve a redirect from the one you don't want to use to the one you do. Users can still type whatever the heck they want. You still have a canonical single version for SEO pur
348.
by ef4 12y ago
Sure, but unless you're going to keep falling into the "not invented here" trap, you're going to encounter code that comes from outside your organizational boundaries.
349.
by ef4 12y ago
One does not always have the luxury of sticking to the good parts. Code is communication, and you often have no control over who is trying to communicate with you.
350.
by ef4 12y ago
This service is essentially what you describe. It's entering beta in Boston right about now: http://www.bridj.com/
351.
by ef4 12y ago
> The principal disadvantage of B2B is that the long sales cycle greatly increases the time until you get feedback that your product sucks Waiting to sell until after you've built something is just as foolhardy in B2B as in B2C. The
352.
by ef4 12y ago
Let's rewrite this: "The point is that public VCS doesn't benefit Wietse, and by extension Postfix, so why should he have one? A public VCS only benefits other people, most of whom aren't even contributing to Postfix dev
353.
by ef4 12y ago
>The inter-release diffs aren't very large, typically. But they're much bigger than the individual commits, and so if something breaks in release X, I can ponder the whole diff or I can bisect the history and ponder a handful o
354.
by ef4 12y ago
I search through other people's commit histories all the time. Commit logs are by far the most thorough documentation you'll find in the typical codebase. Not for the big things that appear in changelogs, but for the little things
355.
by ef4 12y ago
> What is the use case for knowing what intermediate things may have been available to some small group prior to release? It's a use case that actually comes up a lot. "This line looks funny, why does it do that?" Go read
356.
by ef4 12y ago
Doesn't follow at all. There are open source projects that expose read-only VCS and still only accept patches via email . Postgres, for example.
357.
by ef4 12y ago
Because that history is way too coarse to answer the kind of questions that a VCS can answer. And because they already have a VCS , and are just stubbornly unwilling to share all that useful information with the wider community.
358.
by ef4 12y ago
Again, none of that is precluded by a read-only public VCS. The process of discussing changes and patches on the mailing list can still be identical if that's what they like. People seem to be equating "expose some VCS" wit
359.
by ef4 12y ago
People can run their own projects how they want. But this is not just a question of preference -- an open source project developed this way is strictly less useful than one that exposes its true fine-grained history. They quite literally th
360.
by ef4 12y ago
> Knowing what not to put in is sometimes the best way to keep good code. What does that have to do with exposing a read only versioned history? Nobody is asking him to give the whole world commit privileges.

More ›