skysight-inc/HackerNews huggingface dataset:
Agreed. On the front-end, module loaders eventually come in handy but their utility isn't immediately useful. If an "anti-pattern" is something that seems useful but eventually isn't, and a "pattern" is something that seems useful and immediately is, we need a phrase for this third state, where it's a pain in the ass to start with and only becomes useful later.
How to Fix 100% CPU Usage While Idle in XBMC
You need all of the senior folks to manage the two engineers and tell them what to do and subtly deflect criticism towards them when things go wrong. Is it not the case that the business folks are entitled to and have the right to the fruits of the engineers' hard work?
I also don't know what any of it means, but it certainly looks impressive with all these uppercase letters.
Kinda fun to watch on a sunday morning.
I'll second the suggestion to read Starting Strength if you're going to lift weights. Starting Strength has excellent descriptions of how to perform the lifts correctly. If you're not lifting with correct form you could hurt yourself. If you're not meeting the lifting standards then it's impossible to quantify your progress.
Ask HN: Best SaaS splash pages?
> What's the chance of somebody losing their phone and their watch at the same time?

This question is loaded with the assumption that somebody has to lose them. No, it's enough for them to place them unsupervised in the same place, at the same time, regardless of how that's done. Examples:

* Four dudes rob you in a shady alley
* Someone breaks into your home while you're sleeping
* Someone goes through your things while you're changing at the gym, or even at the doctor's.
* Someone grabs your phone while you're sleeping in a train
* Someone steals your phone and spoofs the Pebble

The "what's the chance" route is ok for small-scale, low-sensibility deployment. If there's one chance in a million per year and there are 5,000 units deployed, 99% of which contain nothing but boring contacts lists, it's a reasonable route. Not ok from an engineering perspective, but ok from the point of view of a company that sells consumer devices, for whom product quality is nice to have, but not important.
What does that have to do with serializable transactions?

"The Serializable isolation level provides the strictest transaction isolation. This level emulates serial transaction execution for all committed transactions; as if transactions had been executed one after another, serially, rather than concurrently."

If you don't get the right behavior with serializable transactions, as you seem to be claiming, it seems to me that serializable transactions should be considered buggy. In this case they do not provide the guarantees they are claimed to provide.
When you write the articles, do you SEO on questions that people may ask in their searches or just write general articles not necessarily pushing your product?
When talking about people who have their breaks in later 30's etc., chances are high they've had kids already.
New Fractal Art Tool
It uses kisrhombille-based shape-grammars. In it's present form you can create grammars, export raster images, run a pretty art-streamer
My Short Affair with Microsoft Surface Pro and the Retail User Experience
The actual article recommends more than 7 minutes.

http://journals.lww.com/acsm-healthfitness/Fulltext/2013/050...

A problem for any routine is that people might not have a reasonable baseline for what intense activity actual is.
I have always had issues that are consistent with low-to-moderate ADD (never bothered getting diagnosed) and caffeine provides a noticeable, but not drastic, improvement for me. I've never tried any other drugs.

It is probably safe to say the effectiveness of caffeine/modafinil/adderall depends on your unique personality, brain chemistry, etc.
Thats the holy grail of marketing, and you will not get the answer here.
The problem of engineers designing UIs is the topic of one of my favorite books: http://www.amazon.com/The-Inmates-Are-Running-Asylum/dp/0672...

The problem is that engineers are not very good at UI design. Both from UX and aesthetic standpoints designers are capable of making a better product. A good designer will give a consistently better result than a good engineer in terms of usability, UX, aesthetics and modularity.
Large ISPs like Comcast are offering services over a variety of different systems -- some may not be upgraded or otherwise do not have the capacity available to support the 105Mbit/sec package. This $250 fee is probably to cover the instances where they do need to make backend changes to support faster speeds for the customer. They charge every customer the fee to spread the costs associated with that out.
Me too. I tried hard here, but I dare not to attaché the URL with every post. I got 0 conversations too, even though part of my target users/customers are here.
I fell off the wagon after tearing my calf doing the 7 minute workout, don't ask, but ramp up a little and take it easy.

My GF on the other hand used the 7 minute workout as her only exercise during our extended trip and gained strength and mobility. It definitely works.
Correlation != causation

To me, a lot of these folks are artificially limited by slow and encumbered education methodologies. The data seems to confirm that, as a physicist can more easily begin independent work, while the others need to wait until they have accreditation/equipment/funding/etc.

I think this delay of productivity would be especially avoidable in high school and undergrad programs.

If you could begin advanced fields in your early 20s, instead of your 30s, I speculate the distribution would shift left quite a bit.
Yeah, to me some evidence that the person has attempted to understand what I do and why this product would actually help me (considered honestly) is what distinguishes interesting contacts from spam. I'm in academia rather than industry, but I think some at least vaguely similar principles apply.

I get some cold emails that, while slightly disguised, boil down to: "a paper you wrote came up in a Google scholar search for 'Prolog', and we also have a logic and/or rule system that's great, pls see this website and let me know if you want any details on licensing". Those are not usually that interesting, since of course I know there are such systems out there, and can Google for them myself...

On the other hand, if you read in the Future Work section of a paper I wrote something along the lines of, "it'd be great if X existed, but it doesn't seem to", and you think you really have built something meeting the description of X, then emailing me saying so is usually quite interesting and non-generic.
Thanks for asking first, we'll get back to you.
I've read this sentence 5 times and still have no idea what your argument is.
He is incorrect about isolation levels, at least in PostgreSQL. Serializable with DELETE + INSERT will make a concurrent serialiable update fail with serialization error. I just tested this.

1=# CREATE TABLE my_table (key text primary key, value text not null);
1=# INSERT INTO my_table VALUES ('key', 'foo');
1=# BEGIN ISOLATION LEVEL SERIALIZABLE;
1=# DELETE FROM my_table WHERE key = 'key';
2=# BEGIN ISOLATION LEVEL SERIALIZABLE;
2=# UPDATE my_table SET value = 'bar';
1=# INSERT INTO my_table (key, value) VALUES ('key', 'value');
1=# COMMIT;
2 ERROR: could not serialize access due to concurrent update
> So it’s not enough to say “it looks better this way”. Designers need to make a case for why the team should spend time on fit and finish.

That point is central to the post and yet not really followed IMO. Costly changes to the UX should be justified in objective terms, e.g. consistency, color or style matching, differenciation, focus improvement, branding, readability... Not a "it feels better", or "it's delightful" or "I'm a creative person, I know what's right" (<- if it's his/her personnal project this one is OK)
I'm confused. Are we designing accounting software or high concurrency? Upsert is not magic, there are always trade offs.

If this is accounting software then use transactions.

If you're doing a research paper on accounting software then have fun, there are lots of trade offs to play with.

If you are designing for concurrency then drop your constraints and transactions and just make everything an insert. Then when you want to select just look for the first record from the bottom of the table.

No feature, be it upsert or whatever, can ever beat proper design. The best it can ever aspire to do is equal it.
Gwern has a great write-up on this: http://www.gwern.net/Nootropics#adderall
Of course it's only one data point, but a high quality one imo.

edit: Just saw him linked below, should've read first -_-
I hate this pattern.

People hear, "PostgreSQL is like MySQL except that it is done right." They then go to PostgreSQL and say, "PostgreSQL does not implement my favorite MySQL feature in my favorite MySQL way."

Part of what makes PostgreSQL what it is is that they care so much about getting features right, and making them standards compliant. (Because if you do things differently than the standard, there is a chance that you will find yourself forever maintaining both the way that you did it and the way the standard said to do it.)

I like upserts. I understand the value and the functionality. But please don't add it until you can do it right. And please, please, please make it work like the standard says to. The standard is explicit, flexible, and a standard. Plus if you haven't impressed on the MySQL solution, it really isn't very hard to figure out how to do what you want to do. (I certainly didn't find it hard when I had to do it.)
They missed the chance to get a good deal on Tesla. It's too late Apple. Move on.
My friend and I just started a site to help do this: http://leaklist.org/

It's super early, but we've already gotten 500 users who are looking to beta test software and we've already started sending out codes.

Our goal is to make it the best platform for developers to get their first 100 users and the best place for users to get early & free access to awesome apps.

If you're interested please sign up either as a user or a developer—we're sending out stuff weekly!
Putting your URL at the bottom of every comment is actually against the HN guidelines: http://ycombinator.com/newsguidelines.html

But yeah, I would think few startups would find the HN community a bullseye.
I would never do a large JS project with out modules. But I also never use "module loaders".
If we're talking about barriers to entry, then think about one-man shops - for a non-EU programmer, registering a legal entity in Luxembourg is neither simple nor affordable.
Advertising on social media and lots of instrumentation.
To be fair, all of their team except one come from technical backgrounds. There are three other engineers (Michael Jeffords - CTO's relative?, Vincent King and Richard Soczewinski) listed as employees on LinkedIn. That puts the split at 10:6, which looks healthy. I'd be more worried about the lack of information and the fairy tales on the product's website.
Getting the design right is important. But it's poorly communicated. For better or worse, programmers tend to be primadonnas who don't respond well to being told to move a button 3px (see seivan, et. al) for no reason.

Furthermore, the exact pixel dimensions you create in photoshop rarely translate to the browser due to screen size differences, resolutions, etc. It's much, much more useful for designers to tell me something that describes the relationship they have to each other than the exact dimensions (e.g, "these elements should line up on the right" rather than "make divs 253px"). Obviously for things like spacing there's some element of eyeballing until it feels "right", but you can and should be working with design before stuff goes out to get those right.

So yeah, it's frustrating as a programmer to go through these nitpicky details. But keep in mind it's frustrating because you didn't do your job of implementing what was specified. So maybe don't complain about it in a way that sounds like you refuse to do your job.
W3C JavaScript and HTML5 courses
"No, I don't know it. The GNU's license absolutism is what got them into this mess in the first place. It's inherent in their aims."

Dismantling of copyright and a replacement with a requirement ensuring the freedoms the FSF cares about would thrill them, and not produce this license-incompatibility mess. It is plain, therefore, that it is not at all inherent to their aims. It may be inherent to this particular strategy - but again, license compatibility is something they've been looking at explicitly since making the mistake with GPLv2.

"Imagine that it's a piece of software with a new UX direction not everyone agrees with."

If the criticism was "They did not use GPLv3", that might be a more reasonable analogy than mine. The criticism was they used GPLv2 when they could have used GPLv2+. It's like using the buggy version specifically because others can't use the new UX with it (even though I can still use my old UX with the fixed version). Characterizing that as a move in opposition to those that like the new UX is the only reasonable characterization, absent other overriding factors (back out of metaphor, the only possible reason I could see is a need to use a lot of GPLv2 code in Git - someone else would have to speak to whether that is reality).
Video tag autoplays on any site where you have control over HTML. For example on Blogger. Can't say anything about Tumblr - never used it.

You don't need any special containers. Just use video tag properly, it covers all that functionality since the beginning:

https://developer.mozilla.org/docs/Web/HTML/Element/video

Something like
<video src="..." loop="true" autoplay="true" muted="true".../>

Muting can also be simply achieved by making audio empty in the video if you need to.
>> "Tesla is a product company, and any interference with the product will kill them instantly."

And Apple is one of the most successful product companies of the last decade.

One big thing they would get from Apple is international experience/operations experience. From Apple's perspective I read today that Tesla is working on a facility to double the worlds lithium ion battery production - that would benefit Apple.

>> "Furthermore, Tesla's entire software ecosystem is already mature, so there'd be no gain from Apple on that front."

Integration. Integrating peoples smartphones, tablets, computers, cars, TV's. Tesla doesn't have the best designed software either - something critically important if you're accessing it while driving. I'm sure Apple's expertise would be useful there.
This is almost the exact same question as this front page post from an hour earlier: https://news.ycombinator.com/item?id=7248460

In essence: Go where your users hang out. With few exceptions, this is probably NOT the same place as where startup geeks hang out.

One example: my startup has a website for the Energy & Utilities industry. We got a bunch of early users by forming a partnership with a trade organization for energy providers.
I'm not sure how familiar you are with the zoom functions on web browsers, but zooming in on many web pages can easily destroy the design. This is especially true when using a lot of media queries in your CSS and when using absolute units to position and size elements in your CSS (e.g. using px's for your base font size instead of em's or %).
Reminds me of these:

https://hsivonen.fi/script-execution/

http://ln.hixie.ch/?start=1296711456&count=1
Does everyone on your team write the whole stack from front to back? Advanced teams have specialists. Design is no exception.
Yeah, a lot of motivation comes from recognizing that you've got a finite amount of time left to work with. Plus I think when you're older you may better understand the need for patience and for strategy (and have the experience needed to effectively strategize).
7 minutes is better than nothing, but you really need 30 minutes minimum to get your metabolism up to the point where it stays elevated throughout the day. Less than that, and you don't get the lasting, day long benefits of a workout.

The concept of "you don't need a gym membership or weights to get results" is very sound. My girlfriend is essentially a full-time acrobat (extremely fit, trains for 25+ hours a week), and she started me on a simple workout that takes 30-60 minutes, and goes in five week cycles of building up in reps. It's produce more results in a shorter period of time than any traditional gym workout.
He wanted something better in 7 minutes.

Also keep in mind that sooner or later you'll get bored with a workout that doesn't even prevent your shape from worsening. 100 lbs of weight takes up a square foot of space. Most people who come to the gym not knowing what to do with themselves gravitate towards a few light weights they could have at home.
No download. No trial. No install doc. No example doc. No tutorial. Just lots and lots of assertions of greatness. That's not so deep.
Found this because because hnsearch.com is migrating to it. It's very fast. http://hn.algolia.com
Primitive versions of IEs can be ignored. Worrying about support for old IE is counterproductive.
Forget the gym. If you have the time, do p90x. I swear, if you do that, you'll be in the best shape of your life. The biggest problem is maintaining once your done. I can't seem to keep the routine indefinitely.

I stopped about 5 months ago and haven't done much besides surf a couple times a month and I'm still in pretty good shape. I'll start again in March to get ripped for the summer.

I probably should have been doing these 7 minute workouts to maintain...
I'm most interested in the medical stuff Apple is reportedly pursuing with the iWatch. The M7 in the iPhone is the one thing holding me back from a Nexus 5. I use the Runkeeper app and it can track my activities automatically now and is quite accurate (e.g. I set it to record any walk/run longer than 15 mins). I also use the Moves app to track my steps throughout the day. It's quite accurate and with the M7 I haven't noticed any battery drain. If Apple can add sensors to measure several more data points that I can improve upon over time (as I have been trying to do with steps taken daily) it could impact my health quite significantly.
Greg is being modest by not mentioning his [AMDClean](https://github.com/gfranko/amdclean) library more prominently - it's a superb example of what he's talking about in this presentation.

It makes it possible to use AMD modules while building a library or web app (which is utter bliss when it comes to testing and debugging - no build lag or source map nonsense), but to convert it to non-AMD JavaScript in the final step. I use it on a fairly large (~10,000 LOC) library, [Ractive.js](https://github.com/RactiveJS/Ractive), and it's transformed the way I work.
There are lots of pictures of naked people online. Millions probably. A visual effect that makes it look like someone is naked isn't that impressive, because there are naked people all over the place. The nudity aspect isn't the most precise description of what makes the bubbles effect interesting, it is the undressing aspect that makes it a interesting psychological/visual effect.
I haven't done any promotion for http://asoftmurmur.com besides posting to reddit and HN, and it now has 400-500 regular daily users. It depends entirely on what type of product or service you're offering.

Another key thing is to understand the community. There is radical cultural diversity between subreddits which manifests in very different reactions to self-promotion. It's essential to engage appropriately and respectfully.

Something I've used for other projects is searching for coverage of competitors in the same space, then pitching to people who have already featured them. Again, very important to hand-tailor each pitch and offer value to the person you're contacting.
- Mom, it's not that I'm a slacker, it's just that I'm only 34!
This is Cool! Actually it was my plan to find local businesses with bad/outdated websites and offer them a "renovation" but I didn't think to do this pragmatically. Thanks for the cool idea :) If I am going to look for some freelance work, I may actually try to imitate your approach.
To keep your users engaged, search results need to show up instantly and be relevant to them, even when they do typos.

To try this out, I went to the demo page for searching TV episodes (http://www.algolia.com/demo) and searched for "The Wire Season 2". Here are the four results given, with the highlighted portions bracketed:

[The Wire] Gag Reel [Season 2]

[The] Simple Life [Season 2] - Special - The Stuff We [Were]n't Allowed To Show You

[The] Farmer Wants a [Wife] (Australia)
[Season] 6, Episode [2]

[The] Cosby Show [Season 2] DVD Extra: New Interview with [Dire]ctor Jay Sandrich

Rather than seeking "engagement", I'd put more emphasis on having high quality search results. Having 3 of the 4 results ignore the properly typed title of the show is a terrible interface. Correcting "Wire" to match "Director" is absurd.

The sad part is that these results might make you think that the episodes for season 2 of the "The Wire" aren't in the database, but they are. But they are, just not indexed in a way that they are found using the exact phrase "Season 2".

Trying to be more constructive, there is a typo in the first sentence of your Intro, where the name of your company is spelled wrong. Also, "Real-Time Search" usually means search against a database that is being constantly updated. Anyway, I need to get back to screaming at the kids on my lawn.
To the developer, every decision is a trade off, a tension between the demands of the now (features and time) and the demands of the future (elegance, maintainability).

Designers are not in a good position to appreciate the trade offs. It's very easy for a designer to think 'this infelicity decreases delight, and fixing it involves just moving this thing to there'. This is probably an excellent spot of a real design issue, but that isn't the only thing that determines whether the work should get done or not.

I have no solutions, but problems like this are generally because of an insufficient appreciation of the other professions challenges, and if you're working in an environment with skilled practitioners of both disciplines, more communication is likely to fix it.

Here are some suggestions that might help designers talk to developers: Never use the word 'just' when talking to developers, frequently apparently simple things have huge ramifications and just as a designers specialty is understanding how the little things create a full experience, a developers specialty is understanding how little changes affect other things in the full system. Talk to them about the effect you're aiming for, rather than just the change itself - if the change is trivial, the worry is that you're not respecting their time, but if you convey that the trivial change will have a large specific effect then they will understand and may be able to do other things proactively to help you achieve your effect. Show that you care about more abstract values such as 'maintainability'; the ability to add features quickly in the future and having a low bug count are both massively beneficial to the user experience. Where you can, show that your fixes are not merely matters of opinion but are based on empirical evidence, good developers respect evidence. Get involved early in the process and talk regularly to the people implementing the design - show that you care about their opinion, but educate them in seeing things from another viewpoint too.

As a developer, you are probably used to having a discussion with the person who reported a bug for technical issues. Do the same for design issues - even if it's just 'move this button three pixels', talk to them about it, find out why it's important, find out if they really mean that it needs to align with some other element. If you have a legitimate reason to not want to do it, explain the problem - you might be able to work out a better solution together.