skysight-inc/HackerNews huggingface dataset:
Following your passion does not mean: "take a job doing it". It may mean that, but it could also mean: "take a job that gets in the minimal amount of way of you doing your your passion". It could mean "get a part time job doing your passion, and a part time job doing something else". It could mean "Don't take that consuming job that takes a bunch of energy and time just because it brings in the good money" (unless it means, do it for a short time and retire to persue your passion full time...). It could mean 100 different things. The goal is to maximize the amount of time and energy you spend on the things you care about and which energize you, and which make your life full.

And a note on passion itself: As a human, expect the things you are passionate about to change with time. When I was a kid I was passionate about history and archaeology, then I discovered computers. Now I'm on and off passionate about programming, gardening, art and a million other things. Largely the computer thing is constant, but it waxes and wanes. No big deal. I am not a robot, I am not programmed to like one thing consistently forever, if this changes, I can go with it, or descend a spiral to unhappiness.

It sounds like the author's passions changed. Sounds like he changed with them. Good on him, but it shouldn't be seen as a condemnation of the idea of following passion.
It's easier than general relativity, is that good enough?
There's a similar service for that - but with cats!
http://placekitten.com/
Did you sign a non-compete? (If so, are you based in California?)

If those still at the company really don't like you and think that you screwed them, there are some shady things they can do to dilute you down to next to nothing. (They can sell the company you in-part own to a new company that you don't for a trivial amount. It happened to Eduardo Saverin and I've heard even Y Combinator in the early days. It sounds like the lawyer maybe wasn't good enough to prohibit this sort of thing.)

If I were you, I'd try and come to some agreement with them -- give back the laptop and split the difference in the shares. I'd also make sure not to re-use any code at the new company, as that would be unethical and would open you up to legal issues.
I'm confused as to why you would want to capture. My understanding is that pro players try to avoid having to actually capture unless necessary. (I.e. if they are winning a capturing race then the right move is always to tenuki unless the other player does something that demands a response.)
I think that this is just a generator driving a standard de-humidifier. The compressor is compressing -refrigerant-, not the air. The refrigerant expands into a cooling coil, which chills the air and condenses out any moisture.

This is just like the dehumidifier that you use in your basement, only out in the desert somewhere and attached to a wind turbine. I'm not sure why you would do this instead of just capturing the power. Perhaps because if you're installing this in the desert, power transmission could be difficult, whereas the water could be collected in a holding tank at the base and used locally?

The author got this TOTALLY wrong.
I did not say that at all. I challenged the idea that a person who is not passionate about their job is not working on something they are passionate about, by pointing out that you can have a job that you're not passionate about but still be passionate about working on your family—on raising your children well, on having a happy life with your spouse, on maintaining a strong relationship with your parents and siblings and nephews and nieces, etc. There are always some things we have to do in life that we're not necessarily passionate about.
How are you using Anki with emacs? Or are you using Anki to learn Emacs?
Episode 1 of AngelCube TV - Pitch Day [video]
100 years sounds reasonable. Old APIs simply get frozen and new ones take their place. Apps written to .NET, for example, aren't bound by compatibility concerns with the early win32 GDI implementations. Cocoa apps aren't impacted by Carbon's compatibility concerns.

What's the option? Throw whole platforms out and start over every 15 years? Does that scale? It has so far only because the industry has been growing (more smartphones than PCs, more PCs than workstations, more workstations than minicomputers, etc...). But it won't grow forever.
I think you're taking this discussion far past the literal meaning of my words.

In fact, you're actually taking my words to have the opposite meaning of what they were.

Example:

> if was genetics that explains how "men are smarter than women and hence that's why men earn more than women

What I said:

> we see women routinely trouncing their male counter parts

Lastly, trying to boil this down into a simplistic "women are smarter than men" or "men are smarter than women" argument is a fallacy in the making.

A difference in variance and mean does not mean one population body is 'better' than the other.
This is a false dilemma. Just because you set up some opposing conditions: backwards compatibility or unsuccessful api doesn't actually make it true. Just an assertion.

Having a reasonable end of life on support never hurt apple. There are lots of things that I can no longer run on the latest version of OSX. This happens every time the OS upgrades. Except of course they don't use versioned APIs, so it is much less planned for and not really as easy to deal with for devs.

I'm not saying make a shitty API, I'm saying, if you have the people who depend on your product know that changes happen, they can prepare for it. If you release a new version of the API every 6 months, and only support them for 18 months, you can make the api migrate slowly enough that it isn't a serious change for each version.

In native code: anything compiled to old APIs can link to old versions of your library, and just work the same way. In web apis: the world changes faster than the 18 month thing anyway, so whatever.

If people want to depend on your bugs, you told them not to, they can deal with the changes.
Cheat PB 19 April 2012
Cheat PB 19 April 2012 - Kamis tgl 19 april 2012 Cheat PB Point Blank / Cheat Point Blank PB. Cheat PB 19 April 2012 kali ini dengan fitur 1 Hit Auto HS. brikut kutipan Cheat PB 19 April 2012:
Yes! This wasn't what the OP was referring to, though: he had shipping shrink wrap software with APIs in mind. But still, you're totally right and this occurred to me as I was reading the post, for Web APIs: keep versioning the URL for every shipped revision of your API. You'll have to document like crazy, of course. You can even detect stragglers on old versions and help them get on the new version.
TL;DR: Freakonomics applied to restaurants. Easy-to-remember rules to impress your friends when choosing dinner places -- might even be helpful.
Good Example of a Niche Saas Product: DiveCentreHQ
There's a great book called 'Founders At Work' that tells Max Levchin's account of PayPal's early days. Apparently they stopped considering PayPal a payments company very early on. They moved on to being a fraud prevention company. In reality, they no longer have to do anything to promote growth or even sustainability in money moving through the system, so they can just ignore that part. Almost their entire focus is on preventing fraud. I'm not saying it's right, I'm just saying.
The pricing model seems to be slightly different than both epio and heroku and it seems free apps can't have custom domains - also, you only get one free app + db, as opposed to heroku where you can start for free as a developer and then scale (and pay for) the apps that goes live.

On top of that, epio seemed to be much easier to get started with for a basic django project, than both dot cloud and heroku, possibly because of the multiple platform issue.
I posted this but I am not affiliated. I saw it in the Stripe gallery.
The key problem here is that "backwards compatibility" means "backwards compatibility for people abusing the API in undocumented ways".

Don't do that. That way lays insanity. Be very, very clear up front that you will break backwards compatibility for those folks. Don't sweep it under the table, be very vocal about having done it. There will be short term pain as important customers (eg Adobe) learn the hard way that you really mean it. And long term relief as you don't have that legacy headache growing so quickly.

One estimate is that a 25% increase in requirements results in a 100% increase in software complexity. (See Facts and Fallacies of Software Engineering for a source.) That means that the complexity grows as the number of requirements cubed. Therefore the key to a good API is that it be short and simple. When you start to add implicit requirements on top of explicit ones, it quickly becomes long and complex, and the necessary software to support it and make future modifications becomes much worse.

This does not mean that designing APIs is not hard. But don't let your API become what is published and quirks that are not. Just don't.
Just backed and looking forward to trying this out!

I just have one question/suggestion just in case it makes sense. My main hesitation with using a browser-based IDE is that with native apps, I can use standard quick-keys to navigate documents very quickly using just the keyboard, such as flipping between documents, jumping my cursor to the beginning or end of a line/document and shift-arrowing/tabbing to make a selection. These are very basic and simple things, but without them, I would have to painfully use my trackpad/mouse to make selections, navigate the cursor around, or switch between documents. Just wondering if you're considering this type of functionality that will let me perform quick and simple actions through keyboard commands.
Did you hit any issues deploying?
I would say that the FP people (and yes, this includes you) are solving the wrong problem. Mathematical formalism is not a substitute for understandability. Where is the mathematical proof that your doorknob turns?

No interesting property of a computer system (vs. a single algorithm) can ever be provable in the mathematical sense - because said proof, if true, can be construed as a program in its own right - and where is the proof of its correctness - which is to say, its consistency and correspondence to actual human wants? A. Perlis put this concisely: "You cannot transition from the informal to the formal by formal means."

Switching between alternate mathematical models of computation will not give us better intelligence amplifiers (what the personal computer is really meant to become.) Instead, we need systems which cut the operator's OODA loop delay as close to zero as possible: http://www.loper-os.org/?p=202

Any idiot can use modelling clay. Or a child's set of blocks. These objects have no hidden state, allow for no inconsistent states, posses no "compile" switch. One can build a computer which behaves in the same way. And no mathematical wankery need be involved.

Lustrate the squiggly crowd! Half a century of stagnation in computing is enough:

“Throughout my life I have known people who were born with silver spoons in their mouths. You know the ones: grew up in a strong community, went to good public or private schools, were able to attend a top undergraduate school like Harvard or Caltech, and then were admitted to the best graduate schools. Their success was assured, and it seemed to come easy for them. These are the people— in many, but certainly not in all cases—who end up telling the rest of us how to go about our business in computing. They figure out the theories of computation and the semantics of our languages; they define the software methodologies we must use. It’s good to have their perspective, but it’s only a perspective, not one necessarily gained by working in the trenches or watching the struggles of people grappling with strange concepts. Worse, watching their careers can discourage the rest of us, because things don’t come easy for us, and we lose as often or more often than we win. And discouragement is the beginning of failure. Sometimes people who have not had to struggle are smug and infuriating. This is my attempt to fight back. Theirs is a proud story of privilege and success. Mine is a story of disappointment and failure; I ought to be ashamed of it, and I should try to hide it. But I learned from it, and maybe you can, too.”

- Richard P. Gabriel, “A Personal Narrative: Journey to Stanford (Patterns of Software)
I'm actually quite fond of the way Microsoft historically bent over backwards for backward compatibility, but OTOH Facebook is also very successful and has a very successful ecosystem of third-party users of their APIs. Facebook is like the anti-Microsoft in that they randomly change and break their APIs at such an alarming rate that you have to wonder if they are intentionally fucking with you if you code against their APIs.

Obviously the needs for a web API and the needs for an API with a specific binary ABI on a local OS are quite different but I think for either environment, most API developers can comfortably fit somewhere between those two extremes where they don't continue to support inherently unsupported API usage, but they don't break something randomly every week.
Strategies have evolved massively over time and with technology.
True. But the argument I hear most often is that they can't run as many processes because of the SSL overhead. But, that aside, even if the latency is the problem, that's certainly not going to be solved by XP supporting SNI.
SOA Bits and Ramblings: RESTful resources are not typed
Tumblr To Launch Ads Starting May 2
I think Louis CK said it best, "Everything is amazing and nobody's happy."

http://www.youtube.com/watch?v=8r1CZTLk-Gk

Sorry but Social mobile local (or as people cooler than me are calling it, SoMoLo) is still pretty new. You're just going to have to "suffer" through a little more.

I get the author's point that it seems like the same things are getting made and funded over and over. But with only about 1/2 the U.S. pop. owning smartphones, you can't blame people too much for trying to stake their claim. Anything more innovative might be too early anyways.
Employees are often a sign of growth, though not always. A large employee count often means the company has experienced significant growth and is relatively stable. Even a small company, hiring your first employee means you're probably experiencing growth or see the opportunity for it.

Of course judging a company based only on it's headcount is silly, just like judging that the government must be wasteful and inefficient because of it's headcount.
For the love of all that's holy, please add issue sorting back, as requested hundreds of times on the blog post on that topic...
He clearly said, "I have no idea how dotCloud is doing.", making his comment simple speculation.

interesting situation, the whole thing (i'm saying this as someone standing completely outside, looking in)
Ebay tried building a Paypal killer and was not successful even though they owned the network. They ended up buying Paypal and killing their own offering because no one was using it. It has been said many times now that buying Paypal was one of the best decision by Ebay management.
An inovation incentive from consumers would probably work better then the current system.
That's because a corporation does not have to commit to a certain level of production. On the other hand, the government does so all the time at the request of the people. And when you guarantee output X for whatever good/service, the notion of full employment makes sense. As a representative example, it takes about 5,000 police officers to keep the peace for 1,000,000 people in an urban environment (rough estimate, just an example).

Of course, what goods/services should be guaranteed and what the value of X should be for each one is and will remain an open problem.
No tracking down of dependencies necessary, they are all submodules. You just need to git submodule init, git submodule update.
When we get technology for cheap 3d printing viruses, everybody will be able to destroy humanity as a weekend project.

That hadn't happened in human history, and I think it's inevitable we will get such technology in this century. And this is much scarier than swapping president for CEO.
The English language lacks an appropriate word for this situation (singular personal pronoun that could apply to either gender). Many people feel using "he" to refer to both genders is sexist and will instead rephrase the sentence or use "they" as a singular (which is controversial). Using "she" is just another option. See http://en.wikipedia.org/wiki/Singular_they#Gender-neutral_la...
I'm a huge vim guy, and killed me to use the mouse as much as I did in the video. The real thing will be shortcuttable to your heart's content :) And all the standard things you would expect to work (like the ones you describe) will definitely be there before the end.
This post addresses many of the issues we've dealt with at RadioReference.com. We version our primary APIs which has worked very well, but occasionally we have to abstract and write translations for backwards compatibility. We also need at times to deprecate versions and features.

But, this quote in the post is important: "When exposing APIs be absolutely certain the value you get from doing so is worth it."

In our case, our APIs are a significant revenue driver and are worth it. Don't let OP discourage you from exposing your platform's data via APIs. Instead, let this post warn you what to look out for when exposing APIs.
I think this is the problem with the current startup paradigm.

Give cool stuff away for free + ? = $$$

That isn't really a plan for a business. Most startups end up filling in that question mark with advertising. What's wrong with just selling your product?
>At least at an amateur level, it's harder to make a critical, near-irrecoverable mistake in Go -- there's not as much of a snowball effect making an advantage into a bigger advantage. That makes it feel less stressful for me when playing long games.

I think you mean, at an amateur level, it's hard to see the critical, irrecoverable mistakes that you and your opponent make ;)
Facebook Targets May 17th For IPO Date
Who’s next on Zynga’s acquisition list?
Does anyone else think that this is an awesome page to view a bunch of great landing pages?
I'm a Ep.io user, hosting a bunch of apps about half on the free plan and a half on a paid plan. Note that my apps on Ep.io are all pretty low traffic apps in general but traffic comes in bursts. On Ep.io I'm paying around $15 a month for the paid apps (when there's low traffic). Your pricing plans seem very ill suited for my needs. As I understand your pricing table, you would charge me $99 per each two apps (they all use databases), both those I get free and the paid apps on Ep.io. This is obviously way too much, is there anything that I'm misinterpreting?
Space may not be the best place to get raw materials (being, after all, mostly empty space) but you are mistaken about falling demand for materials. Commodity prices alone should tell you that demand is hitting the limits of current production. One smart phone may replace N others gadgets, but only 500 million people had the other gadgets, and _everyone_ wants a smartphone.
Search on Google: Tilt or Askew
Good post, and I agree: it is a little sad to see the game cracked in a way that sheds so little light on human cognition.
My biggest issue with web APIs is the speed at which they change means you often get a lack of maintenance of documentation. The speed of change compounds the effects, the discussions you find on the API usage only months old have lost relevance in non obvious ways.

Facebook and Paypal are or have been guilty of this in the past though Facebook is a lot better than it was.
My post implied that the system is broken, so I do agree with you.

As cumbersome as it is, the solution to 3 would be to have everyone in a circle create the exact same circle.
My understanding was that Amazon kept their Kindle sales closely guarded. The type of person that purchases a Kindle off of craigslist must be completely different than one that buys it off Amazon.

I might be wrong, but Amazon already sells cheaper refurbished Kindles where as Apple does not do the same for iPads.
OP here.

I think this is very naive/utopian.

Yes, be super focused in your design.

Yes, only expose APIs you have clear use cases for.

Yes, keep the surface area as small as possible.

Yes, have very focused requirements.

Yes, document the hell out of things.

Yes, implement strong parameter validation and other things to try to reduce the chance people do bad things.

Do all these things and more (these are all part of what makes exposing APIs hard work, that many people don't do).

But do not, for one second, believe that someone still won't do it wrong or abuse your perfectly designed API eventually... especially if it is successful.
Relatedly, there are powers in the pharmaceutical industry that would love to be able to carry out syntheses in space. The lack of an effective gravity force allows crystals to grow larger and this would be a useful property.
Sure, but the same is equally true the tech industry: bright developers make smart products.
Right. One thing is certain: Google did whatever it could to find a legal loophole in Sun's licensing to let it basically steal Java (I mean, come-on, legal or not, that's exactly what they did. After all, Dalvik has no technical merit over Sun's JVMs - in fact, it's inferior. Its only value to Google was as a means for legal maneuvering). So Google was certainly not acting in good faith, and I think that when someone is not acting in good faith, there's usually a way to nail them, especially if you can afford good lawyers.
Seems very true in my opinion. I've always excelled at math, essentially have a bachelors in mathematics, etc etc. My weakness has always been getting the details of the "basic" math correct.

Higher math is about logic, abstractions and applying them to solve problems. Basic math is about holding bits of information in your head and manipulating them accurately. I absolutely believe that basic math taxes your working memory system more than advanced math does.
As a (sad to see you go) ep.io user thanks for providing the migration tips.
Well, there's at least one pretty major difference: you have persisted data. That might not be ideal for test, although in production you will already have persisted data so test with an empty store might not make sense either. But for a local development or a staging server, being able to recall the data you've stored across processes can be quite handy.
> If we compare the set of people cognitively able to use PHP, to the set cognitively able to use Haskell...

These may be very different meanings of "use."

Using PHP, Java, etc. involves a fair bit of purely mechanical (think "human compiler") labor - cranking out boilerplate, and solving the same idiotic non-problems (all "patterns" spoken of by programmer types) again and again and again. Both of these are things that the average programmer can get quite good at. He will think of himself as a master craftsman. But what he really is: is a valve turner on a Newcomen steam engine. (http://www.loper-os.org/?p=388)

If Haskell were to be rid of all of the shortcomings you have described, the masses would still avoid it for the above reason. Most programming work - particularly paid work, that an ordinary person can reliably get hired to do - is of the idiotic makework variety. So a language which does not supply a steady stream of such makework (e.g. Common Lisp) will stay obscure.

If we were to banish the automatable makework, only the intrinsic complexity of intrinsically-complex problems would remain. And we would need about the same number of computer programmers as we need neurosurgeons. (Fewer, because there are many meat bags and they are always diseased. But engineering problems, once solved, stay solved - or they would, in a sane world.)