skysight-inc/HackerNews huggingface dataset:
"Kids who grew up with touch devices" may not necessarily make better programmers, but there's such factor as being comfortable with tools, I guess.

It's like the language. You spend a lot of time observing and using the system (writing, speaking)—even without full understanding—and you get comfortable: you easily distinguish between characters, recognize speech, can quickly and legibly write. It takes much less effort to apply this knowledge to do successfully things that may require it.

Likewise, if you spend a lot of time around computers, it takes much less effort then to use them for many things, including programming, since computers (or, maybe in future, touch devices) are tools we use for programming.
A few extra Vimium shortcuts I use every day that weren't mentioned in the article:

F - open a link in a new tab
T - search all tabs for a keyword (including minimised windows)
x - close the tab
X - restore the last closed tab

You can also see a help sheet with all of the available shortcuts by typing ?.
It's not only legal, it's standard business practice. One of the recent examples of this was when Google bid against itself during an auction for spectrum that it didn't want, solely to drive up the price. As long as you are not colluding with the selling party to drive up the price (in which case, this is illegal, known as shill bidding) - all is fair in an auction.
I approach this slightly differently when contracting in order to get a spec everyone can agree on.

1. I ask the client for a brief (an outline of what they want, not a detailed spec, the general what rather than how, when or why).

2. I give them a spec which satisfies the brief, highlights any areas they might not have thought of, and outlines exactly how the work will be done and what it will entail (and what it won't), and how long it will take in days of work (not days on the calendar), broken down into small subunits of several days each.

3. We sign off on the spec (with any revisions they want), agree on a schedule (based on the time estimates with plenty of padding added for feedback, approval stages etc), and I start work.

The padding for the schedule (perhaps 3 x work days) won't cost them extra, and is there to cover the inevitable friction that working in groups produces, but if you're contracting you can spend that time waiting for feedback doing other work, so it comes at no cost to both parties. Probably the padding increases as the size of the company you're working for does.

I've never received a spec from a client that I was completely happy with, so it's easier to turn it around and accept a brief describing their goals in general terms, then give them a detailed description of how, when and why I would produce what they want. Asking them for the detailed specification, or even accepting one from them without lots of discussion, usually leads to problems as you're relying on the client to specify things they may not fully understand, you're asking them to tell you exactly how to do all the work, and by starting with their spec and mangling it or forcing lots of compromises, you make them feel they're not getting what they want. Whereas turning this around and giving them a spec lets you explain the cost/benefit of all decisions up front, and still gives them room to add/remove things as they wish as they approve the spec.

I do this even for design work as well as programming work, as there are a surprising number of constraints which a client may not consider, but will wish by the end of a project they had. All that said, most of my best ideas come from clients half way through a project, so you can't expect things not to remain fluid - that's just the nature of creation - as long as changes improve the end result and don't have knock-on effects I welcome them.

I'm not really convinced the article is correct in estimating 1 day as the horizon over which most developers can't see - in my experience that's too low, and it'd be more like several days, and as long as you split tasks up when estimating, it's not hard to estimate the actual hours worked - far harder is to estimate the friction introduced by bureaucracy and politics in larger organisations. I suspect that's where most inaccuracies in scheduling creep in.
The Pentadactyl nightly works fine in Firefox 15
The cost of random seeks is still going to be lower than on hard drives, which is what most current filesystems were optimized for.
Cannot emphasis that enough. I would even argue the opposite: people who are now older than 30 did have the possibility to hack much nearer to the hardware of the devices, and could understand how they work. Now, because the tech is both so well packaged and more complex than before, no one tinker with devices really anymore. Sure, there is stuff like Arduino, but this is really reserved to a couple hackers. You don't have a Arduino hacker in every classroom. So maybe the digital natives are more comfortable with SMS and social media, but that doesn't mean they do better software or hardware developers.
It's the recognition that we humans are tedious creatures.
The article sounds like a linkbait.

The title says "more feasible than thought" and the ending paragraph says that in order for it to work we should first find dark energy.

So how come something we don't know if it exists makes a theory more feasible?
But the iPad was released 30 months ago.
CouchDB retrospective
The problem with most recruiting sites is the lack of (competent) candidates.

And this is because highly competent candidates are never deliberately looking for a job. They get recruited to a pretty good job before they have even started thinking of jobs from college, and then get recruited to other companies by an old friend. It's extremely rare that they are ever considering themselves to be a "job seeker" at all.

These people don't bother reading recruitment-only sites in their free time. And they certainly don't want to create a job-seeking profile, and get in trouble with their boss who thinks they may be leaving.

But what they are very interested in is reading about their field of speciality. When I was sourcing candidates, the only online places where I found qualified engineers were the StackOverflow and 37signals job boards. These two are successful because they built the community and content that competent candidates want to visit daily first, and added a job board second. I have no expertise in mechanical engineering, but GrabCad seems to be doing it well in that area.

So my theory for running a successful recruiting site is:

1. Choose a single profession, skill, or field.
2. Create seed content yourself to attract initial experts in that field.
3. Add community features to let these initial experts contribute more content.
4. When you have become a well-known site for most experts in the field, add job boards.
> why do most successful entrepreneurs end up working very long hours to make their companies succeed?

There's a mistake in your reasoning in this sentence. An entrepreneur who has to work long hours for years on end is by definition not successful. At least using my definition of success.

I consider myself a very successful entrepreneur, even though my 'preneuring only brings in the equivalent of a modest developer salary. The important part is that it only takes up a few hours of my time each month, leaving the rest open to do what I want.

And, of course, being able to do whatever you want is the core reason to become an entrepreneur.

With that in mind, if you've set off to be your own boss, and you somehow find that you're working longer hours than ever, regardless of the payback, you've failed.
Apple gives previous MobileMe users increased iCloud storage
When Apple announced iCloud last year, it told MobileMe users that they could keep their current storage in addition to the free 5GB they’d get with the new service for 12 months to help with the transition.
On the other hand you can also measure things like whether the written code is maintainable, well documented, portable, ...

It's a bit like measuring lines of code or similar things. I kinda wished everybody could be his own boss and be actually be responsible.
I think he means when it is used like "coffee or tea?"
Opera - vimoperate

covers some (your mentioned) basic functionality. However the Opera API is not as diverse, or wasn't at time of dev, afaik.
A simple rule I have for dealing with this sort of situation: I'm either a freelancer or a cofounder.

Strangely enough, saying that one line has changed a conversation from "Hey, wanna work for my startup?" to "Hey, wanna be CTO/cofounder at my startup?"
The discovery that made warp drives more feasible had nothing to do with dark energy, but with the shape of the warp bubble.

So yes, we don't know whether or not warp drives are realistic, but since it would apparently not require as much energy as previously thought they are therefore in theory more feasible.
It is not possible that we can know to whom they once belonged nor to whom they currently belong.
"And in either case ..." We are now several levels deep in this thread. Even if I agree with your point - and I do - the point is almost entirely lost already. Most would have stopped reading at the grandparent of my first post. Notwithstanding the special case of the hackernews domain. In the wider world, just a little shit that sticks - smells. So how do we manage the perception - not just the fact - of this problem? Because it WILL be necessary if bitcoin is to flourish.
Bingo! An absolutely wonderful blog entry on the decline effect is http://thelastpsychiatrist.com/2011/02/the_decline_effect_is...
Fighting an N-headed monster with recursion
Samsung-LSI is part of Samsung's semiconductor division, it has little to do with the their consumer electronics section.
وظائف خالية فى مصر
وظائف خالية فى مصر
LFS recudes seeks on writes but requires more seeks on reads. This was bad for general purpouse use so they didn't become popular with rotating media.

It's a perfect fit for flash, because there read seeks are (almost) free, and the overwrite-less, sequential writes are a perfect fit. Flash only supports read, erase, and write-on-erased operations, the exact set that LFS uses.
"No food or drink" is a good one, so many possible misinterpretations between or vs. XOR, and how you scope the "not".
How would the hours I spend on a remote desktop session count in your office?

I'm a teacher, its outcomes all the way for us, and being there when the class meets.
Misleading headline, this is about CouchDB and only tangentially ASF.
That's not copyright infringement, that's arbitrage.
This is a quite arrogant post. I do not make APIs but I can understand some needs of the API providers.
First of all you are being arrogant because you if you just want an URL and nothing more means that for you every API must be free and this is totally bullshit. Also giving you a URL and nothing more gives me no control on what you do. You could harm my service by doing too many request or god knows what and I could do (almost)nothing without hurting maybe other developers. Conclusion: think of the others before ranting.

P.S.
the code samples are there help all the people that are not great developers as you.
[video] Projucer demo.
The video on the home page is surprisingly polished and professionally produced but the script is an obvious piss-take. The home page on the other side is a quick & dirty job - looks like it's been thrown together in a couple of hours using some free website template.

I vote for an end-of-year project by media students made for fun.
Blog spam.

http://www.ifixit.com/Teardown/Apple-A6-Teardown/10528/2
It's funny you should mention avionics. Because I remember writing test scripts for one such system merely because I had "basic" on my resume. I had no idea what a FADEC was. Granted, we ended up doing these many thousand line copy-paste jobs (i.e. figure out which of a few test functions to call for each of about 10,000 inputs)

I ended up learning VBScript for that job, automating some of the testing, and turning the scripting tool they gave us into a music player.
So how many times were you a cofounder to date?
Brackets is fully extensible -- here's a getting started guide for writing extensions: https://github.com/adobe/brackets/wiki/How-to-write-extensio...

The powerful thing about Brackets is that extensions (and the rest of Brackets in fact) are written in JavaScript, so basically every Brackets user has all the skills necessary to write an extension and customize their development environment.

We don't have an easy way to customize key bindings yet, but it's on our backlog:
https://trello.com/card/keyboard-shortcuts-stored-in-json-fo...
https://trello.com/card/keyboard-shortcut-customization-inte...
It is an interesting point: startups are a market target. Providing services for startups can be an excellent source of income.

My company was selling primarly to startups until the 2007 crisis, it was no intentional but very profitable: we were benefited by companies which changed their products a million times without any profit. After the crisis,in 2009/2010 we ended up having established companies as cutsomers. One of the reason is that less outsourcing and less investments are made by startups.
We already have cars that drive themselves and are getting sci-fi glasses with really primitive Augmented Reality. We're getting there, I just don't think we'll ever consciously realize it as we experience it.
Well that was nice.

... um.

Now what?
Wait, this sounded familiar: http://danshipper.com/b2b-is-unsexy-and-i-know-it
I love CouchDB, but I love the CouchDB community even more. I think we made the important decision to cultivate community right from the start. One of the key components in getting that right turns out to be the concept of a community gatekeeper, or steward. Someone to guide things back in the right direction when they get off-track. Someone to set an example. On the very few occasions someone has threatened the atmosphere on the lists and in the IRC channel, it has been nice to see people defend it with passion and with humility. When those people see how things work here, and how committed we are to keeping the grass green and not letting the project become mired by useless arguments and petty aggression, they either adjust or they leave.

Perhaps rather than producing wisdom, crowds encourage demagogy, regurgitation of home truths, and petty agression/pedantry unless they are encouraged to channel their energy in other directions. The contention is that they are never self-regulating (even if you give them the tools to do so), but require intervention and moderation to remain cohesive, productive communities.

Some interesting lessons in here for communities like HN/SO/Reddit/SD etc. which rely on crowd moderation and technical measures to try to guide a community. When dealing with a large enough community, that can break down as enough new members arrive to subsume the older culture completely in a small amount of time, and any technical measure you think of can be subverted by those willing to put in the time to do so. I think reddit's approach here of splitting the community up into smaller niche groups is really interesting, but IMO they arrived at it too late to save their community overall.
Just once actually. And "founded" a few web projects ... and right now I'm starting up a small business.

There aren't a lot of cofounding opportunities when most of your time is spent doing classes at uni.
I apologise for the 20/20 hindsight, but even for a salaried position, don't make a move without getting it in writing.

This was a breach of contract - just not an easy one to enforce
Just the other day I went to use the good old fashioned twitter API to find that it had been deprecated in favor of a new one that requires that I do everything differently in order to get the same results. Really irked me. I can empathize with this guy.
Most people I know learned Eclipse/Visual Studio first.
Nowhere in the post he writes that the APIs must be free. Maybe he just wants to pay with money instead of time and attention.
The main problem of enterprise startups isn't to find the right problem-domain but rather the sheer amount of work power it needs to find and solve the edge cases. Big Co uses a lot of Custom Software for a reason... The bigger it gets, the more custom solutions they use.
SAP and Oracle employ a boatload of people just for that reason.

If you're interested in enterprise startups you should start looking for a really specialised piece of workflow that is common among huge company's and try to solve that in its entirety better than the existing solution.
I think it's getting progressively easier. I think that back in the day before the Internet, perhaps in the mainframe days, you had to be a true wizard and know your domain extremely well to make anything happen. Think K&R kind of attitude and skill level.

Nowadays anybody with sufficiently good Googling skills can put something together by stitching pieces of Stack Overflow code. You don't need a specialist to make it happen, just about anybody will do. Perhaps you shouldn't leave mission-critical aspects of development to those people, but you can get away with most of the other work.

Was it Mark Suster who said that most companies out there do not fail because of bad technology?
That would imply the need for an API key though, and he mentions that he doesn't want those.
3D hardcore hentai - Pornhub.com
Agreed. You can do a lot in programming without much knowledge, but a lot of the really good opportunities and interesting work are reserved to those who have superior domain expertise.
Pittsburgh Steelers vs Philadelphia Eagles live stream watch NFL online
Philadelphia vs Pittsburgh live stream watch here NFL online football
Regular season 2012 Week 5 and also enjoy full season Match scheduled:
Date: SUN, OCT 7 2012 Time: 1:00 PM (ET) NFL Regular season 2012 Week
5 venu: Heinz Field
Pittsburgh Steelers vs Philadelphia Eagles live stream watch NFL
online,Pittsburgh Steelers vs Philadelphia Eagles live stream watch
NFL online,Pittsburgh Steelers vs Philadelphia Eagles live stream
watch NFL online.
I found it very limited (just movement keys) even compared to Chrome vimium. You can remap vimperator (or pentadactyl) keys anyway. The only difference I remember was d (close tab) instead of x.
I need to ask, what HN app are you using?
Interesting question - to me, the distinction is that 'evidence' of the validity of something is expected output(s) given known input(s), whereas 'proof' (at least in the mathematical sense) is a logical transformation that is applied to make it obvious that the theorem must be true. I'm not sure you could call a proof 'evidence' because it's not an output of the theorem - it is the theorem.

I'm less certain than I was before I read your post, though - so I stand to be corrected :-)
Counterpoint - http://api.dribbble.com
I would be very interested in knowing more about what exactly his problems were. What APIs what he trying to use? I work on backend systems and build APIs or related systems everyday so getting a rant is not of much help. :(
* Auth Tokens - needed.
* Code samples - good place to get started.
* Documentation - really, I am yet to see a good API without documentation.
* Blog - Okay not always helpful but other times its a way to tell users about new features, downtimes, changes.
* business development/relationship/ecosystem - not important but can be nice to have in case you get stuck or are building something that is more than just a crappy weekend hack.
Yeah. I wanted to read some tweets, but apparently I now need a stupid API token and have to do OAuth! What happened to the good old days of session-less read only-mode APIs?! :(
Ha. I've had the same thoughts many times. Never thought anyone else felt this way.

At some stage, people started to get weird ideas about URL schemes (aka "API's") like it's some sort of marketing thing. API keys. WTF? Imagine if early Google was required to get an "API key" for every site they crawled. Who came up with this silly idea of "API keys"?

In the 90's, I remember decipering URL schemes in order to do crawling long before anyone used the term "API's" to describe URL's. They are usually quite predictable, since almost every website used the same software. And they're even more predictable today. Crwaling got easier. Hmmm, I wonder why.

I also remember how most URL's used to be non-descriptive. Not true anyomre. Google has changed everything. Sites _want_ to be crawled now. But funnily enough they think they can make money from it. Heh, good luck with that.

If you want to charge money, then put the data behind a password and a paywall. And watch traffic plummet.
I just noticed the "Sign in" link on the top left. Clicking that opens up a windows popup with Mozilla's new Persona login feature. I didn't enter my email address but instead closed the popup. Yet the site refreshed and shows: "You are signed in as ". Is this normal behavior?

I'm not very familiar with Mozilla's Persona. Been meaning to try it but I've got to find the time and a suitable project.
There's a few things I'll push back on:

I could harm your service by making too many API-key signed, OAuth-signed requests too. I could harm your service by hitting your website a lot too. We have ways of dealing with people who intentionally or unintentionally launch the equivalent of denial of service attacks: you block their IPs and move on. There's no need to have a special magical way of doing it with an API.

The point is the whole concept of an API should be unnecessary. We have a way of saying where data is: URLs. We have a way of specifying what format the client wants it in: content negotiation (Accept headers). We have a way of retrieving that data: HTTP GET. There's a reason why BugMeNot exists for websites. API keys are basically pointless registration pages for access to the same data that is being published on the web.

As for the code samples: if there's little more needed than "here's the URL of our data", I don't need a code sample. I only need a code sample when it's been made ridiculously over-complicated.

(My favourite API recently: clockworksms.com - all of the other SMS providers I've looked at want me to talk to some salesman and/or read complicated docs. Clockwork just let me send an HTTPS POST message. They have an API key, sure, but they required only an email address to get it. And I can pay for credits with PayPal. Ridiculously simple. I like.)

As for arrogancy? Guilty as charged. I'll say in my defence that it's more that the data I wanted to retrieve from the service in question (which I won't name) was exceptionally simple, had no commercial value in itself, but would send referrals to the site that they could monetise (and there's no affiliate scheme, I wasn't gonna profit off this). There literally is no business reason to lock that kind of API down. It's just cargo-cult API design: everyone else has API keys, they must have a reason, so I better have that too.
Paid APIs should have the minimum amount of bullshit to determine who pays what. Free APIs should have no bullshit. Request throttling doesn't require API keys.
Nope, it isn't. I'm just trying it out. If you did sign in, you wouldn't get much. It's just for writing posts. ;-)

It's a case of building my site from scratch, and I wanted a super-light-weight authentication system. So I picked Persona. (Incidentally, I picked it because unlike Twitter or Facebook or whatever, I didn't need any API keys to get started.) There are a few bugs with my implementation. But as it's just to authenticate me to access the admin panel, it's no biggie.
Which is a fantastic API, I must say.
Well, in the case of Twitter: Justin Bieber happened.
Am I the only one who hates the new youtube.com/Google+ layout?
I just recently saw that when I'm logged into youtube.com I get a very google+ looking youtube.com website which looks nothing like the youtube.com website when you are in incognito mode, the one which I actually find useful to use. What are your thoughts on the new website? Image: http://i.imgur.com/mkGkT.png