skysight-inc/HackerNews huggingface dataset:
As a alleged kernel engineer I wonder what this means for me.

For now, I see it means that one person out of a dozen gets to write the device driver -- if that --and the rest of us get to do patch slavery. heh. :)

as far as linux, it is kind of sucked the air out of the room for embedded development, but I think in kind of a good way. I'm sort of out of an interesting systems job, and people who think they can write an app in user space for their device and be done with it are in for a shock when it doesn't go quite right, but with embedded linux people can just write an app in user space for their device and be done with it. Yes, you read that right.
Man and a Van Barnet Chipping High EN5
Future impact: Predicting scientific success
For anyone looking for a fully-featured notes app, Catch, mentioned in TFA, is the way to go. It does sync, has a web interface, and probably a 100 other features I haven't used.
I'm wondering if it might be easier for a language like Chinese or Japanese, perhaps, where the symbols and words are a bit more visually distinct.

That being said: doesn't Rosetta Stone use a technique that basically relates pictures to common words? I've never tried that program, and only looked at demos briefly, but I've heard great things about it.
The 1st thing I was thinking about the $45 China quoted market price (which is probably lower since it doesn't include either volume or haggling) was the cost of shipping from China to the other markets. At the end of the article we see the price after shipping translate to $79, which adds approx 100% to the cost in-stores. I guess the next wave will involve ways of either making shipping and the process of importing cheaper, or just circumvent it all together with say 3d printing.
Yes! Show up at a few local users groups, attend some conferences, actually understand the technology you're recruiting for.
Moving on with the analysis, Agile with an uppercase A is an anti-pattern to how humans live and work in the first place. The idea of sprinting makes sense when you're within reach of the goal

1) Agile != Scrum. Sprints are just a Scrum term not a general term in the agile community.

2) Many Scrum folk I talk to think sprint was a poor word choice (it wasn't intended to be taken as "as fast as possible" but "something with a defined end" - many short sprints rather than one long marathon). Many use the more neutral "iteration".

3) Not going as fast as possible and having a long term sustainable pace is what agile projects are all about. That's why you saw practices like "Sustainable Pace" in XP http://www.extremeprogramming.org/rules/overtime.html
It's already known that since ICS Android is prettier and more functional than iOS.
Awesome! But I think I like the old layout better due to the darker contrast between the information header/footer and the thumbnail- stands out more, easier to distinguish. Infinite scroll is a nice addition :)
I keep both an electronic diary and an engineering notebook in a physical lab notebook. I find both helpful to getting organized and developing my thoughts. I would never publish any of these. They are for my use only.

I format my diary very simply. The key for me is to not get distracted while I'm writing. I use two formats: a dated journal: a date and entries that follow. This works in any kind of editor. The other format I use is more subject based, with org-mode, and headings to split up topics.

org-mode has a tag feature, where you can add lists of tags to a header. I might try that for categorizing my entries for future sorting.
> did I tell you about the time that: the mat cat sat upon?

I'm not getting it. What was the bad English speaker trying to say?
Yes and also don't miss hovering over areas and waiting for a second to isolate only the overlapping colors.
I think map data is from Nokia[1]. API interface may be same as Google API's.

[1]http://thenextweb.com/mobile/2012/09/17/nokia-confirms-amazo...
I've never used Ruby on the application layer, but I'd be wary of using an ODM with MongoDB. The single most shocking issue seems to be at the application / ODM level. Using the official 10gen-supported drivers gives you more control and a better understanding of what's going on every step of the way.

Also, a thorough understanding of MongoDB indexing, advanced queries and schema design would have squashed all of these issues. Has anybody had a more pleasant experience with a MongoDB ODM?
Would be cool to be able to navigate through the keyboard arrows!
Sorry, no. I have no desire to make G+ look good or bad.

Also, if I installed the G+ app 6 months ago, and then take a picture of my kid today, there is no explicit intent to engage with G+. Claiming that I "engaged" with G+ is ridiculous. You have to recognize this. This certainly is not the type of "engagement" that they are trying to sell to advertisers or the press.
Watchdogs say tons of issues remain before unmanned aircraft can fly free in US
I like google +, I really do, but look at your google + feed, then look at your facebook feed. They are both vying for the time. Its clear as to who is winning that war.
The low end of every successful product category ever created eventually becomes a commodity. The author has equated the commoditization of low end tablets with the death of one of the worlds largest industries.

This would be like saying; margins are slim on spreadsheet software, the software industry is dead.

This article exudes a failure to grasp basic economics.
No, Scobleizer is a name for Robert Scoble, a well known Google+ power user.
I'm really curious how they measure "active". For example, recently I've noticed that when I initiate a video chat in gchat it forces me to use a hangout on Google+. Does this make me an active Google+ user?
The long release cycle for new versions of IE is irrelevant. Internet Explorer security patches get pushed regularly through Windows Update, which Microsoft encourages users to set up for automatic installation. So this problem will get fixed for the average user as soon as Microsoft sends out the patch. It requires no more knowledge than updating Chrome does.

Note that I'm not recommending that anybody use IE. I'm just pointing out that it does get automatic updates, just like other browsers.
Can you explain your reasoning? Isn't high scalability one of MongoDB's key features?
Those are good questions, and ones we're also working through at the moment!
You used to be a professional recruiter, but you can't think of any way to get introduced to developers besides cold-calling them? Seriously?
Stanford, I work on software for big physics experiments.
I wonder if a script request to plus.google.com (say, to load the +1 widget) would count? It has to piggyback on your Google login (or else it wouldn't know who to attribute any +1's to), and so would simply loading a page that has a +1 button count as an "active user"? I don't think it's too far outside the realm of possibility.
Wait, who's actually making money off Social TV?
its about the opportunity cost for me. An hour of my time spent doing actual research versus prettifying my slides is a no-brainer.
Of course Android can be beautiful if you showcase a few screen shots created by some very talented designers. After spending the last 4 years as an Android developer, its clear that the platform falls short in two places at the intersection of UX and UI. I've worked with some of the best designers and they always produced beautiful assets and screens, but we were always left making important UX decisions that caused inconsistency with other apps. The "beauty" that many users come to appreciate with iOS and Metro, is the cross app consistency, experience and cohesion with the operating system itself. Even apps produced by Google have a tremendously wide gap in consistency. The other major problem is development decisions made (and allowed by the platform) by software engineers. More than a few of the apps in this list do unthinkable things like processing data on the UI thread or having terrible offline experiences. This can turn a beautifully designed app into a terrible app very quickly.

It's important to distinguish "looks pretty" and "beautiful".
Innovative Ideas for Fixing The Patent System
You were fortunate to recognize that MongoDB was the wrong tool for your job, and lucky to be able to move to Postgres instead of continuing to throw your time and effort away. I see the ad hominem "you're an ignorant idiot" attacks already started, along with advice like using regexes to do case-insensitive searches. Watching the NoSQL "movement" encounter the problems RDBMSs fixed 20 years ago and then hand-wave and kludge them away is frustrating. I wrote about some of this in http://typicalprogrammer.com/?p=14.

Look at the bright side: programmers who are writing NoSQL-backed apps are creating the fossil fuel that will keep programmers who know RDBMs working into our retirement years. I already have more work than I can do fixing web apps that were built around crap data management tools that failed to scale beyond a few thousand users. Your Postgres expertise will still be a money-making skill long after MongoDB is forgotten.
Zero-Day Season Is Really Not Over Yet
I too, am interested in this.

From what I gather reading the synopsis and the relevant discussion here: I'm not so sure how useful it would be for me. At the very least: I think it'd be a challenging technique for me to pick up.

It sounds like it relies on having a good spatial memory, e.g: being able to hold "maps" in your head. I've always been terrible at that, just ask anyone from my D&D campaigns.

However I think I'll pick up a copy of the book; even if I can't apply the techniques it really piqued my interest.
Agreed. I'd actually thought of that, but didn't have the time to implement it before my hacking time was over.
It's not (only) about the consistency of visual style. It's about the the consistency of interaction.
I could see people wanting to use this to add simple chat rooms to existing products. I would probably think about going through the XEP-0045 standard to verify that you are satisfying all the requirements for XMPP Chatrooms (if you aren't, you're probably pretty close), and adding that to the documentation. If someone at an actual company were to try to use this, it would be helpful if they could say that hermes supports the proper XMPP standard.
Quite interesting, but it seems they used the old Mono gc, when testing F# on linux

I tried to replicate their results (it wasn't really easy to setup, so I only ran few tests) to show the difference when using the SGEN gc, these are my results on my corei7 860 (4 cores + hyperthreading)

F# on Windows8 64bit (it should be .net 4.5)

.\fsharpbench.exe 80000 1 bharr 3

6.94s

F# on Linux (Mono 2.10.8)

mono-sgen Main.exe 80000 1 bharr 3

13.69s

mono Main.exe 80000 1 bharr 3

20.54s

and, by changing the gc's write barrier, you can shave off an half second more:

env MONO_GC_PARAMS="wbarrier=remset" mono-sgen Main.exe 80000 1 bharr 3

13.02s

Linux Scala 2.10M7

scalac-2.10 bh-impure.scala

scala-2.10 Simulation 80000 True 1

5.641 s

Scala 2.9

scalac bh-impure.scala

scala Simulation 80000 True 1

7.676 s

so, F# on Linux is still slower than Scala and F# on Windows, but the situation is not as bad as in the paper (4/5 times slower, or worse): it's in the same ballpark (a little more than 0.5 the speed on Windows) imho: definitely usable (on single core loads it is also much more competitive, from the few lines of F# that I've written)

btw: it seems also that Scala2.10 is quite faster than Scala2.9 :D
What clothes washer are you talking about? Do you have a top-load washer? Those are notorious water wasters that probably can't wash well without huge amounts of water.

As a counter point, I have a front-load 2011 Samsung washer and dryer. I even got some money from the Big Evil Government water district for the washer and IIRC from the Big Evil Power Company for the dryer.

I am 200% satisfied with the wash and drying quality. It will take quite a bit to convince me that energy efficiency requirements are causing problems.
Oh for the love of God, we still need convincing of this? Anyone with an ICS/JB phone knows that Android is perfectly capable of looking good. My "least-good" looking application that I use on a regular basis is the Flashlight app, and even then, it's just a big round glossy button.
Why in the world is this named after a feminine hygiene product?
Toamna se fac pregatirile de iarna la masinile personale
He mentioned Insteon, so I'm assuming http://www.insteon.net/.

I've been wanting to get into home automation too. My biggest fear is vendor lock-in. I'd like to hear more about how he gave his garage door a REST API, because that's something I could build my own interface for.
This Is the Oldest Record In History—Scanned and Recreated From a Photo
...Or a "file system from hell" that wreaks havoc with your file I/O. Fuzzing a program in such a way would likely uncover countless bugs....

Though you are probably familiar with them, there are I/O fuzzers like zzuf[0]. I bet it'd be relatively straightforward to write a similar tool that uses LD_PRELOAD to intercept and randomly delay various library calls. Sometimes I'll test my own network software by piping /dev/urandom over netcat:

dd if=/dev/urandom bs=1K count=1K | nc [hostname] [port]

[0] http://caca.zoy.org/wiki/zzuf
Very happy to see the Bump 3.0 on there (I worked on it). ICS and all of it's native apps were a great statement by Google to show how they'd like their apps to look and feel. We followed their queue and used the action bar and view pager to great success. Also having a great visual designer doesn't hurt either.
$56
http://www.frys.com/product/6905837?site=sr:SEARCH:MAIN_RSLT...
Monkey Boy? Ballmer: "Screaming loudly doesn’t work very well in our industry"
Intel's Game Changer: One Size Fits All Haswell
it's best just to start with a SQL database and go from there.

This is bad advice. It's best to understand your problem domain and use the tools that are most appropriate. You see a lot of two types of posts on HN:

* "I picked a NoSQL database for a problem domain with a better relational fit." Those posts look like this one.

* "I picked an RDBMS for a problem domain with a better NoSQL fit." Those posts are usually titled something like "How I scaled Postgres to XYZ qps" and describe an insane amount of re-engineering and operational hell. Oddly, these posts are usually proud of the accomplishment rather than embarrassed that they picked the wrong tools in the first place.

There are upsides and downsides to RDBMSes. From my experience, you should be leaning towards NoSQL systems (of which there are many, each suited to different use cases) when you have very large scaling needs (in terms of dataset and qps), heavily polymorphic data, or data that has ambiguous structure.

It's been stated many times already: Use the right tool for the right job.
The generic cheapness that may portend the death of hardware is the same force that is causing a renaissance of hardware hacking.

Most major cities have hackerspaces or techshops (http://www.techshop.ws/) where you can 3D print and use CNC mills. It's not uncommon to take apart cheap hardware and hack something into it (failure is much easier to stomach on a sub-$100 device).

Arduino has been the main driver in this area for years, but mark my words: Go on Raspberry Pi is the hardware platform of the future. Go is close to the metal and has great concurrency, which make it ideal for interfacing with sensors. No more dealing with Arduino's lack of real threads and the weird sketch format.

My Pis arrive tomorrow; long live hardware!
...but only if you skip regular UI conventions
There is nothing illegal about poaching talent from your competitors, either directly or through a recruiter. I've had clients (recruiter here) tell me what companies have the talent they are seeking. I wouldn't say it is even unethical to try and get talent from other companies directly - it's just business, the same way you want to attract your competitor's customers.
Odd Things Happen When You Chop Up Cities and Stack Them Sideways
I have written iOS apps (although never public published) and taken classes in iOS development. I am much more of a novice at Android development, but have written a complete (albeit simple, un-networked appliance) app. I've focused more on Android recently because that platform is evolving quickly.

So let's just pretent this isn't a shitty genetic fallacy post and address your challenge head on, "Back up your example and prove to me Android's APIs give more guidance than Android's in how to do ______." I specifically mentioned the Loader pattern.

Compare:
Google's Loader pattern: http://developer.android.com/reference/android/content/Loade...

A concrete and common example, doing an async task: http://developer.android.com/reference/android/content/Async...

Compare this to the equivalent API for doing async task usage in iOS: http://developer.apple.com/library/ios/#documentation/Perfor...

In iOS There is no concept of a "Loader", so the community has come up with stuff like AsyncUIImageView and friends (code here: https://github.com/nicklockwood/AsyncImageView) which still doesn't entirely solve the problem, because solving the problem takes a lot of framework support.

Sadly, fragmentation is at play again in this; and many Android developers don't use Loaders because they're intimidated or confused or can't use them for their entire panoply of supported devices; so there are a fair share of Android apps that do not use them. You can usually catch this if you change orientation and see things reload from scratch.

Given the rapidly increasing velocity of deployment of 4.0 devices, I think this issue with framework fragmentation is transient.
Hollywood ponders a path from app to hit show
Ask HN:Is there good marketplace for selling software beside phone marketplaces
i like to be able to get income beside the freelance jobs , something that can generate revenue , i was wandering is there any good market niche that i can build software and sell l it ? plugs-ins or desktop apps
Wow that's sad, aside from casual flings I've been living alone 7 years longer than this whale has been known to.
Failure is a feature: how Google stays sharp gobbling up startups
Thanks! The original darker theme was intended to make the thumbnails stand out, but I didn't know if people found it useful. Once I get some more feedback for this version, I may tone down the brightness for the next update.
How is the recruiter deliberately blocking access to public info? By having candidates remove the info from their resumes or something?
What is really exciting about this is the impact on emerging markets. I live in Ghana and tablets and phones are how people access the internet, and will for the foreseeable future. If tools get good enough there might never be PCs as a tablet seems to be a much more accessible interface to get started with.

It is an interesting market to think about trying to monetize but the potential is huge as tablets drop to a price point where average urban dwellers (who are currently barely computer literate) can afford them. I already see iPads in the hands of the richer crowd and expect to see cheaper Androids flooding the market very soon. The need for custom software to make it easy for a population that can only hunt-and-peck is going to be huge.
With regard to sticking to rules, it depends on the game. With D&D you're explicitly told to break them as necessary ("Rule Zero").

In Burning Wheel, on the other hand, the designer intends you to follow the rules precisely as written, and the result is a system where players have much more freedom to do unexpected things and even drive the story themselves. Because there are well-defined, mechanical ways to attempt just about anything you can think of.

Video games don't come close to replicating either of those experiences.
But this is not a problem Android has when apps target 4.0. The ActionBar has been a huge stabilizing influence on the Android interaction pattern; strongly enforcing backpaning, swipe-to-navigate, and consistent locations for navigation.

I'm not sure why you'd say this. Android actually hasn't suffered from tactile UI fragmentation much more than iOS has.
I agree that Android can look gorgeous, but that can only go so far. Android's problem is consistency. I've used every alternate android build I could find, and the custom (and default) themes and UI menu system lacked consistency. My favorite was MiUi and even that had terrible consistency issues.

iOS, on the other hand, is supremely superior in this department. The cohesiveness of the experience is second to none. I value that over custom configurations any day. My android phones have been wonderful hack-fests, but at the end of the day, the one thing I can't hack into them is a consistent experience.
This really is a terrible name. And putting "tampon means buffer in French" at the bottom while having a logo that looks like a tampon with a string isn't fooling anyone. I like the app idea, but am not going to use something called Tampon.
Wrong. SQL databases (except for SQLite) are almost completely interchangeable because they are all based on the same relational model and they all implement the ANSI SQL standard with only minor deviations. If you have a lot of stored procedures and triggers -- executable code embedded in the database -- you will have to rewrite that.

Oracle is in a world of its own in a lot of ways, but if you are moving to or from Oracle you should have the required resources and expertise in your budget.

If you are referring to the well-known cost of COUNT(*) in PostgreSQL (or MySQL with InnoDB, for that matter), or different ways to handle full-text searching, I agree that there are differences you have to deal with, but they are not usually a big deal.

Contrast the fairly easy and routine process of migrating between MySQL, PostgreSQL, or SQL Server with the huge amount of work involved changing your application code from MongoDB to anything else.
Correction.

A/B testing does not need to assume that it is testing over a small window in time that has stationary conversion rates. In fact in practice tests run for a long window of time over which you have good evidence that the distribution is not stationary. For example in the middle of running a long test that eventually found a small lift, I've often run and rolled out a second test that generated a much stronger lift.

The weaker assumption that you need is that the preference between versions is stable across your fluctuations. Then because the mix of versions is time independent, that non-stationary fluctuation is not statistically different between the slice that was put into A and the slice that was put into B. And therefore the variation between different samples becomes just another unknown random factor that does not interfere with your statistical analysis of whether there is a difference.

This is an advantage between A/B testing and the current state of the art in MAB algorithms. When this came up before, Noel (at Myna) and I privately did an admittedly brief search of the literature for discussion of this point with regards to MAB algorithms. We turned up a number of things that would work in the long run, but none that directly addressed the problem.

But in discussion we did manage to come up with effective MAB algorithms, whose regret is only a constant factor worse than standard MAB algorithms, that accurately will identify stable preferences in the face of constantly fluctuating conversion rates. To the best of my knowledge nobody, including Noel, has yet implemented such algorithms in practice. But in principle it can be done.

However even if you do it, several of my other points still apply as real differences.
I, for one, revel in diversity of looks, function, and interface. It keeps things fresh and interesting. Especially in an internet that seems to be more and more conformed to the same styles (all of googles products, twitter bootstrap, etc)