skysight-inc/HackerNews huggingface dataset:
I was laid off at a large electronics box store as a business systems admin after they closed 26 stores in Canada (guess who!) in 2013. I got another job for nearly double the salary afterwards so it was really good for me.

I started as a junior web dev at the new place so I learned web dev on the job instead of using the C# applications skills I had learned at my previous position and after a year have moved up to web developer with my new skills. Luckily the SQL, version control and OOP skills don't really change and after dealing with a multinational's database system I could rock the SQL pretty hard.

The drop in title was a bit of a kick in the pants but that's just superficial anyway. Everything else about the job was awesome -- and still is.

I took a week for myself to gather my thoughts and really think about what I wanted in life because I wasn't happy. Once I knew what I wanted it was easy as long as I didn't stop trying. This I think was the most important part of making the lay-off a success in the grand scheme of things.

Before getting the new job I had to go through a few months of EI and waiting patiently for the right fit. I got laid off at the same time as hundreds of EA and Microsoft workers with far more experience than I had at the time so finding a job was hard. I only had 1 year of industry exp before being laid off.
I'm more interested in starting a business that has a 90% chance of being worth $10M than a business that has a 1% chance of being worth $1B.

A business that has a 90% chance of being worth $10M isn't suitable for VC.
My hosts file still won't work. Domains like dev.app never work.
10 Questions to Consider When Using an API
Great article, I'd just like to point out that URLs by no means only work on the web. Android has deep, native support for URLs in apps, and are frequently used for inter-app communications that have nothing to do with the web. Another OS could easily add such support for URLs.
The worst case isn't just for Google and Android, it would mean that API's are no longer in fair use. No more IBM PC compatible BIOS or any such industry advances.
This paper: http://kam.mff.cuni.cz/~fiala/tw.pdf gives a deeper (but still very comprehensible) overview look at corollary 2.5 and for more specifics.
The thing most enjoyable about Roboto is how it's changes are a near perfect reflection of Google's design capability.
I've been learning Ruby on Rails, Python, Javascript, and now am considering focusing on learning Java.

As you would guess, there is quite a bit of difference.

Appreciate the feedback.
Amtrak does not qualify as a proper rail system . . . besides, the comment was clearly referring to municipal transit. For Seattle to LA, I can't imagine any rail system ever beating flying.
Great, now we can have a monospace version for the terminal/editor.
If this were a company, the headline would have been "IRS hacked; tax information stolen from 100,000." Instead the IRS was able to spin it to The Washington Post. The headline is "thieves stole tax info." Thieves!

The real headline is that the IRS is hackable.
i was not talking about linguistics, i am searching for a word that refers to a third sex or gender. can you name one?
Look at Android, the most popular computing platform in the world, and you will see how native has won. Even Facebook and YouTube are native apps on Android.
I am wrong, no random primes.
Ask HN: How do you develop API Driven Applications?
1. Do you start building off the API first entirely?

2. Do you build the front-end along side?

3. Is it sane to use Postman for the entire process?

4. Is it challenging to build API-driven apps?
Apple drops discoveryd in latest OS X beta following months of network issues
Yes indeed. However, for us to be able to scientifically verify those theories, something about them must be invariant in space, time and rotation. That's pretty much the definition of a scientifically verifiable theory.

My point isn't that there can't be theories without those properties nor that the universe necessarily has them (or not). Just that, if it doesn't, we couldn't verify it scientifically.
There's also the reality that repairs and replacement can be very difficult or impossible. Similarly, my iPhone fundamentally expects me to have access to a highish-speed, lowish-cost internet connection for tons of its functionality, and that still isn't necessarily available in much of Africa. In Zambia last year, in a large second-teir city, my _household_ internet cost about $8/gb, so things like automated backups and downloading software updates isn't especially attractive.
This sounds like the journey from "realization of the cost of hacking" to its "cure", the grand solution.

I had the same epiphany in my 14th year of software development when I realized that programmers Must Be Given Solid Platforms of Well Architected Object Oriented Code or they will Make A Mess.

However, now in my 34th year, my view is more "Plans are useless, but planning is indispensable".

I have "grand" architectures, but my architectures and their implementations are designed with the assumption that they will be wrong in a week's time.

And my advice to anyone reading this is YAGNI. More practice helps. But practice the right thing.

I.e. its war, not craft.
Lots of 404 errors when trying to access links (like the tutorial).
If you find how to get one of these phones, let me know. I'd like to do a teardown.
> Instead the IRS was able to spin it to The Washington Post. The headline is "thieves stole tax info." Thieves!

They spun it even better than that. The headline is "thieves stole tax info from 100,000 people" (i.e. not from the IRS, but from the people themselves)
It's kind of late to ask questions like this after spending 12 months of work.

Regardless of my other feedback, you should launch and see what happens. No one can predict the future.

That being said, I don't see who would be a target for your app. Vimeo Plus costs $10/month, Vimeo Pro $20/month. Youtube is free and allows embedding of videos in your own website.

Who are the people that would have a need for your app and wouldn't be served by Vimeo or Youtube?

At $500/mo you're in "enterprise sales" category. There's no way an individual or hobbyist will spend $6k/year just to upload the videos. Enterprise sales usually require enterprise sales tactics (picking up the phone, trying to convince real people about the value of the product) which pretty much means you need a (very good) sales team.

Also, at that price people will want to know you're a stable business.
Indeed, but they share the same power system, battery, several CPUs, heat management etc. and will likely have similar problems.
Thanks for sharing Presentious. It sounds trivial, but producing lightweight presentations synced with audio is quite hard. I like how you can go ahead on audio or slides and then sync them back together.
It's a good thing we banished that curl | bash antipattern.
The even more corrosive case in dating is that there's no "happy path". For a SAAS product, you might have incredibly churn for users who join just to kick the tires and leave quickly afterwards but you can sustain yourself on a core of extremely long terms customers who will almost never leave and keep paying reliably month after month.

With dating, there's no equivalent case. Even hookup apps, your users eventually get tired of the hookup lifestyle or they age out or they get enough casual partners to satisfy themselves.

Dating is one of the few services where your customers get unhappier the more money they spend on you.
comscore is notorious for being off by 50% or more.
Maybe. But a few scandal stories will kill that idea.

Everyone wants a cab. No one wants a geriatric care home - not even when they're living in one.

Having said that, I recently discussed some possibilities with a couple of local care home owners. Currently there isn't enough smartphone take up to make some obvious ideas viable, but that will start changing soon, and then there may be some very rich pickings to be had.

This is the real reason Apple etc are piling into health apps. The biggest buyers won't be marathon-running twenty year olds, but scared-of-death >fifty year olds.
You're still making some pretty strange assumptions here. An imperfect prediction of the future does not render the prediction meaningless, and making architectural decisions to support expectations of the future does not necessarily mean a significant increase in complexity, it often merely means some upfront "critical thinking" time. In fact, this upfront time may very well speed up the rest of the implementation, even if the predicted future requirements never come to pass, because it produces a more well-thought-out and well-understood architecture, that may be cleaner and more powerful without making the actual implementation any harder.

But again, there is a large continuum of possible approaches here, and insisting on reducing it all down to either "do everything" or "YAGNI" is really kind of bewildering.
I haven't seen anyone mention it here, so a little off topic, but if you have to make lots of presentations with slides Emacs's org mode pdf export [1] (via LaTeX beamer) is a godsend. Easily the fastest way to put together slides I've used, and you get pretty good math and source code support.

An example pdf (not great content, but...): http://gray.clhn.org/dl/macros_etc.pdf

edit: and the .org source file, which is probably more relevant: https://github.com/heike/stat590f/blob/master/macros/macros_...

[1]: http://orgmode.org/manual/Beamer-export.html
Very interesting analysis.

It seems that as a general rule leveraging sexuality and power to promote something is effective as long as that association remains covert.
I've been told that they BlueJ IDE is great for beginners.

http://www.bluej.org/

When I started learning Java in 1995 I used Windows Notepad because there was nothing else I could find. There was no Hacker News to get good advice from, and paper based Java book to read from instead of free ebooks on the Internet and Github repositories for example code. Sometimes I had to pay money to get a floppy disk postal mailed to me with example code on it.
So I guess it depends a lot on the kind of steel that you're using and what you're designing to. Do you need the full 100F range? Can you get a lower expanding steel for a nominal price increase if you're going to buy many mill run's worth? Are you going to have to build to bridge standards, or can you get away with something else? It's sort-of a bridge, but sort-of not. From a technical perspective you don't need as much safety factor since you've in total control of the vehicle load which isn't true on bridges. I don't know what the regulatory considerations on safety factor are especially since it would probably qualify for its own category since it bears little resemblance to anything that's man-rated like bridges or buildings.

You might also be able to get some nice double-whammy effects from using something like a514 since it's corrosion resistant, has a higher elastic yield, and may well have a reduced thermal expansion coefficient. If you increase the strength and decrease the expansion at the same time then instead of blowing 40% of your "budget" on thermal it might only be 10%. And since you're covering such a large range of climates you might be able to rate every 10 or 20 miles of loop based on the climatic averages in that region instead of looking at the absolute min and absolute max for the whole thing. It might add a few extra weeks of design but make things a lot more feasible.
i use viper mode but with different keybindings (the most commonly used movement keys are under or near the home row, layed out geometrically): https://github.com/bshanks/viperre
Android is open, Google is not at all. Google is actually pulling source code off AOSP (the actual open-source Android) to put more of it into their custom, closed-source applications. As a result, a base install of Android without all Google's services is very poor and pretty outdated. [0]

Most of the work Microsoft does on Android (and iOS) would easily be replicable by Google on Windows Phone: Office, Skype, OneDrive... are all apps that Google has competitors for on Android and iOS. Instead of playing the same game, Google chooses to be the evil one. [1]

0: http://www.infoworld.com/article/2610371/android/meet-aosp--...

1: https://blogs.microsoft.com/on-the-issues/2013/08/15/the-lim...
While choosing a kernel bandwidth may be arbitrary for certain situations, it does have some nice properties. The bandwidth informally defines how "close" points need to be to be considered similar, which can work well for certain problem domains where this can be easily determined.

Like most clustering problems, if you can't choose a reasonable set of parameter values based on some domain specific information, it is largely trial and error. Of course, there are several metrics that can be used to score certain clusterings (e.g., parameter values) over others, as described in your wikipedia link.

The other nice advantage that mean shift has over k-means is that it does not make any assumptions about the cluster shape. K-means assumes spherical clusters. Mean shift allows for clusters of any shape, since it is driven by density.
The #1 use for Excel is actually lists, you know. Ask Joel Spolsky, who used to be the project lead for the Excel team. http://www.joelonsoftware.com/items/2012/01/06.html
Deutsche Bank Ignored Its CDS Problems Until They Went Away
wonder if that explains some of the absolute cf's I have been having with my osx server randomly changing the diradmin password and the final straw losing my networked home directory I have given up and am switching to i5 windows 8 and buy new proper workstation class pc's in preference to the shoddy apple kit
It's much faster to run multithreaded code in java than your other languages. Here's why:
http://en.wikipedia.org/wiki/Global_Interpreter_Lock
Mitch Mcconnell will do just about anything not to vindicate Edward Snowden
Unfortunately, she was not American.
While this may be instinctive to you, it is not necessarily instinctive to an artist, or someone with no socio-normal intuition.
> I can't install apps from third-party sources
> http://www.windowsphone.com/en-us/how-to/wp8/apps/how-do-i-i....

That's a sleight of hand you're trying to do... the link explains how to load an app from an SD card, not how to load a 3rd party app (that is, an app someone else made and gave or sold to you independent of Microsoft). According to Microsoft[1]:

"To enable sideloading on a Windows 8.1 Enterprise and Windows 8 Enterprise computer that is not domain-joined or on any Windows 8.1 Pro or Windows 8 Pro computer or on a Windows RT device, you must use a sideloading product activation key. For more information about acquiring sideloading product activation keys, see Microsoft Volume Licensing"

So, true third party sideloading is limited to enterprises. Microsoft is just as bad as Apple in terms of controlling what the consumers do with their phones.

[1] http://blogs.technet.com/b/privatecloud/archive/2014/02/28/i...
At least they let you in to grab your laptops and whatnot.

A bummer your landlord didn't pay the building with your rent money and you both got evicted. Good things people were able to work at home until finding the new office.
That's how I figured it out.
The K's with the flat middle were horrible. Interesting that they were the only characters poached from Ronnia and now replaced with something more familar.
Sorry. We have no plan with older versions of Photoshop (CS). We use function of Photoshop CC (2014)
Gigaom.com Acquired by Knowingly Corp
Very good analyst.
Marketers will say "you can market based on sex, fear or greed - and sex sell the best."
This is an ad-based business, and it's the standard metric for comparison by ad folks, so it's appropriate to cite here.
I believe it's similar to the Windows 8 sideloading process, which is that it has to be created by a developer and using a marketplace ID, but the app does not necessarily need to be published on the marketplace. Otherwise, you wouldn't be able to test your apps on real devices prior to releasing them in the wild.

I'm sure if you have a paid app and try to sideload it, you'll need to own it on the marketplace (otherwise piracy, etc), but for a free or unpublished app, I believe it should work fine.
...isn't that 75 year thing incorrect?

http://www.cnbc.com/id/45018432
Or they could merge into (or absorb) the KDE flavor of Linux Mint (which - IMO - is more-or-less redundant given Kubuntu's continued existence), taking over the development of the Mint+KDE and LMDE+KDE projects (thus leaving the main Mint folks to focus on Mint/LMDE with Cinnamon and MATE (and Xfce, but I personally think that Xubuntu should follow Kubuntu's footsteps and absorb Mint/LMDE+Xfce).

To me, this particular Canonikerfluffle is just yet another straw on a camel's already-broken back.
I'm interested in what this means for the tech ReCode uses. ReCode staff have deep expertise in WordPress and at least historically employed top WordPress development talent.

Matt Mullenweg, Automattic CEO, wrote about AllThingsD when it first launched, "All Things D is a fantastic new WordPress MU powered site that I think is a really good example of what the platform can do." http://ma.tt/2007/04/allthingsd-on-wp/
Yes - if you're interested in Android development, it's definitely the best language to use to get started.

Java can be a little clunky, but once you learn Java you can pretty easily learn the basics of C#, for instance.
What's hot with DevOps?
Agile and powerpoint aren't the same thing.

I guess we'll just have to agree to agree.
If you busy poll, getting to 50 ns latency from producer to consumer is easy, 20 ns is possible. The best I've gotten with a bare bones optimized test was about 16 ns. You tend to get best results with high frequency dual core CPUs with hyper-threading disabled.

Bigger issue is that the reader needs to busy poll, consuming 100% CPU time on one CPU core. Maybe energy consumption could be reduced by using monitor/mwait - not sure if it's possible from user mode or only in kernel.

Another issues in this implementation is use of compare-and-swap. For this purpose, fetch-and-add (LOCK XADD on x86) would be more efficient. Multiple writer contention is much worse with CAS.

Record size is also fixed, you can't have multiple different message sizes.

Overhead per message is 12 bytes, two ints that can be either 0 or 1 and an int called Metadata. Seeing there's commit and rollback fields, both 1 byte, 2 byte overhead for commit and rollback should have been enough. You're going to get false sharing whether it's an int or a byte.
Well, Vox certainly isn't limiting itself to tech. It owns vox.com (politics, with a liberal bias), SB Nation (sports), and Polygon (gaming), among other sites.
You can copy the link into google and access it through there
It's possible you have worked in a world where there really is requirements-level (which means business-process level) stability over a year. I never have, and I don't think that describes most businesses out there.

Given that, writing software that is responsive to the needs of the business must accept that change in unknown directions is a certainty.

Now, does that mean that you literally never know anything at all about what will come up? No, of course not. Sometimes you'll see a thing coming for nine months, and it'll actually land just like everyone thought.

But the point of YAGNI -- and the point Fowler made so well in his essay -- is that you still don't need to do your chin-stroking calculations and elaborate plannings on whether you should build for that now. Because building for it now has a real guaranteed cost (the direct cost of building it, the opportunity cost of the value you didn't deliver by building something more immediately necessary, the technical debt of maintaining it in the face of other evolution until you get to the time when it actually is needed) that strongly argues against building it even if it will happen.

In any other field, this is really obvious. If a contractor is building a house, and they say "you know, we've already got the cement-pouring team here, we know we're going to build a dozen houses this year, why don't we just build all twelve basements right now" they're going to be slapped down quickly -- that's absurd, don't tie-down all those resources speculatively, and anyway if you do that, the house you're building is going to be late, let's focus on what's needed. And that's true even if the contractor was totally right about needing those dozen houses (and exactly which dozen, and exactly what they should look like).

That you're probably going to be wrong to one degree or another (even features that end up happening often look significantly different when they happen than they did in prospect, months out) makes the YAGNI equation that much more compelling; but even without that, the numbers rarely are going to come down in favor of speculative construction for hypotheticals.

So, yes, you need to weigh the benefits against the costs. It just turns out that this is nearly always a calculation that leads inexorably to one result: Don't do it until you actually need to do it.
In startups, almost everything is punished by company failure.

Another example is failing to plan ahead far enough that you can maintain your first mover advantage when a competitor comes along and already has the benefit of learning from your mistakes so far.
It's true that it's a tradeoff, I just don't understand why people put up with this, why it's apparently still more desirable to shave 0.5mm of the thickness rather than have more reliable power. Or my pet peeve - reviewers who compare 2 phones with high density screens and clearly state that you can't see pixels with the naked eye on either one... then proceed to mark down the one with fewer pixels, even though it would be more power efficient.

If this is how reviews go, it's not surprising we see impractical tradeoffs.
Ask HN: What is the ideal contract worker agreement?
I am moving from being a full-time employee doing web dev to a remote contractor with my former employer. My hourly wage will be about twice what it was previously, so I feel like that part is sorted out. I was wondering what other stipulations I should add, though. My goal is to only work maybe 10-15 hours a week, and to have as much schedule flexibility as possible (to work on my own projects).

Should I require 24 hours between receiving tasks and completing them (so that I'm not expected to be "on call")?

Should I specify that I'm only available to do work certain days of the week?

Should I try to tell them I won't do external client phone meetings (since this ruins my schedule flexibility)?

Are these unreasonable stipulations for me to add? Are there other conditions I should try to negotiate in that I'm not thinking of?
You are talking about sideloading in Windows 8/RT, not Windows Phone 8.

You can also sideload third party apps without a sideloading activation key in Win8, it's how testing on devices is done. You get a developer certificate for yourself (completely free and one button press when you first try to sideload) and essentially self-sign the apps. It's not as simple as double clicking, but it's one Powershell command (Add-AppXPackage IIRC). It's much easier to sideload with the sideload activation key, yes, because sideloading as a whole seems to have been created for Enterprise App deployments, but it's fully possible without it. I believe the only restriction is you need to renew the developer certificate every few months.
3. Do plan ahead. Only implement what you need right at this moment.
>It will be interesting to see which one wins out this time. So far it's clearly Apple, but time will tell.

If you want to compare apples to apples (no pun intended) you should take a look at software sales. So far, neither seems to be doing that well on mobile platforms. I have never bought a Microsoft nor an Apple app on my mobile devices.
Discoveryd has been axed in 10.10.4 for mDNSResponder