skysight-inc/HackerNews huggingface dataset:
1. I realized that a product is not built in a vacuum. Meaning that I had to go out and figure out what products where needed. This led me to reach a simple understanding: I would focus on building products that made people money. Selling such products seems to be simpler (I am still testing this at the moment).

2. With #1 in mind, I focused on what businesses need to make money: clients. Thus, I set out to learn how business generated new leads, or followed up on clients.

3. Now that I had focused on solving a type of problem (lead generation and client follow up), I set out to research markets. Every business out there needs leads. But some can be easily automated. Using patio11's appointment reminder app as inspiration, I started to ask people how such app would help their business. Turns out there is a big demand for such a simple application. Who knew that sending text messages and making automated phone calls would be such a life saver?

4. Who did I talk to? Well, who needs to keep constant contact with their client list? Dentists, insurance agents, private schools, auto mechanics, etc.

5. Once I knew the who, finding the where was as simple as looking in my cellphone. I called my dentist, and insurance agent to talk about the application (before writing any code). They gave their feedback and I set out to write it.
Pen: live editing with markdown
I don't look at money as a score. I look at my salary as the value of my labor. I sell my labor to maximize the value of my effort. I.e. I am looking to maximize my compensation and minimize my effort. It's pretty much how everything on the market works.

To answer your second question is impossible - we don't know the shape of supply and demand curves nor do we know the initial rate of taxes. E.g. if the original taxes had been 1% then it's just going to bump the price a little bit. If the original taxes had been 50% then it ceased to be produced.

But if you want to know the general relation of taxes and supply and demand consider how things are going to progress as you keep raising taxes. Do you seriously believe prices are going to fall as the taxes raise?
SGX is a very interesting development. I agree with Johanna Rutkowska that "SGX might profoundly change the architecture of the future operating systems".

Enhanced Privacy IDs are particularly interesting, since it will allow you to anonymously or pseudonymously authenticate a particular CPU:
http://csrc.nist.gov/groups/ST/PEC2011/presentations2011/bri...

It's also very powerful to be able to attest secure enclaves with a root of trust within the CPU, rather than a TPM. It removes TPMs and the LPC bus as an attestation attack vector.
Well done. Just signed up for personal account, I've been looking for a system to let me track this.
(that is the joke you see)
The problem with Netscape 4 was that it introduced a database that was (in theory) human readable, but poorly specified, buggy and inconsistent. If you are going to change then things should be better on at least one axis, and preferably no regressions on the others. https://en.wikipedia.org/wiki/Mork_(file_format)

It is also worth pointing out this era predated SQLite.
Noticed some console.log statements in the .html source. Isn't this invalid for internet explorer? It would probably stop execution once the error is triggered
The event is keep us abreast of the new products, as it were.
--- Institutions try to understand why this person isn't paying

How does a city like NY or LA scale this, when 1 or 2 out of hundreds or thousands is this type of situation. This situation only happens because a city doesn't have the manpower to do a social viability check on every tax lien.

I agree on principle, but the monitoring of elderly is not the role of government, but of community, neighbors, and family.
And his blog post is just as relevant now as it was then; what's your point?
You could use Dovecot's "thread references" to produce an appropriate data structure from a variety of mail stores.

See "Write a decent mailing list Web archive system" on http://suckless.org/project_ideas for an example.
If you are relying on teleconference hardware made by other companies, I suspect that you will have those companies cloning your software for their hardware.

I mean, I assume Cisco Telepresence stuff doesn't already record/transcribe meetings... If your idea starts to take off, I would bet that it will for sure in the near future. That seems like exactly the sort of functionality you would expect from that sort of hardware.
MediaCrush Post Mortem
you have the aforementioned domain expertise shortcoming

This seems a little harsh or judgemental.

Big Co's don't care about your 10pc better product, because it may be 10% of a cost center that is maybe 15% of revenues. That makes it a 1.5% margin business for them, which is literally not material. Given the politics of BigCos, the top guys have limited bandwidth. They typically don't want the brain damage associated with taking on operational risk for non-material benefits on the upside. Its a distraction, and a fundamental conflict of interest for them. The quality of your sales guy, is only so good as he helps develope a product with lowe operationa implementation risk and has the already-in-place-relationships with a BigCo to de-risk their adoption. even in the best case, its a tough sell. The better bet is to show up with a 10x solution. That turns a 15% cost into a 1.5% cost, and creates a 13.5% increase in profitability. Now that you are moving the needle, you will get people's attention. Even at sr. levels...Just some things worth thinking about. As petet thiel rightly notes, there are varying abstractions of 'sales' skills that come into play, not all are of the door-to-door "sales guy" variety.
I don't really understand why you bring up machine learning and computer science, since this is a completely different field. Classes in neuroscience would apply, but that's not all that impressive.

What I find to be idiotic is how trivial you make your contradiction, without any facts to back it up, adding computerish language to pander to the HN crowd ("metadata", really?), when it's extremely well established that people, with disturbing frequency, remember things that simply did not happen.

It's fine to disagree, but this sort of straightforward contradiction adds little to the conversation. It's the internet equivalent of Monty Python's argument clinic.
This project is actually for sale.

https://www.sideprojectors.com/project/project/144/code-conq...

or the owner is seeking a co-founder.
Perhaps "you lose your job and decide that your WoW bill is a non-essential expense, and make the one-time, non-trivial-to-reverse decision to cut it, which is much easier than every fifteen minutes crushing the urge to start playing."
This is the way I usually end up doing things as well. I originally tested out the text grammar for later.js using a parser generator. Then once I worked out the kinks and played around with it a bit, I rewrote the parser so that it was specific to the grammar I needed with some additional flexibility that wasn't available from the generator.
1. >It's not the tax that's the problem. It's a law which lets them seize the land for a few dollars in unpaid tax.

What happens if they refuse to pay the tax, then? As an agent of the state, how do you make them pay? You might send them some letters with warnings. Of course then they might continue to shirk the law. You can ratchet up the tax, by charging interest. Ok, but that's a number. They still refuse to pay. How do you make them pay?

2. your logic is questionable:

>Property is a huge investment, driven by unsophisticated retail investors (who may be putting most of their life's savings into a single home), prone to stupid fluctuations, which can destroy the lives of normal people when it does something funny. Taxing it helps keep it a little rational (as the taxes will encourage people to avoid it when it starts heating up).

Having children is a huge investment, driven by unsophisticated people, prone to stupid fluctuations, which can destroy the lives of normal people when it does something funny. Taxing childbirth helps keep it a little rational (as the taxes will encourage people to avoid sex when it starts heating up)

Does that sound like reasonable public policy?

And aside from the policy ethics I strongly doubt your model that property taxation is a significant 'tempering agent'. If you're going to call the buyer an 'unsophisticated retail investor', it's unlikely to presume that they will have a 'sophisticated' concept of property taxation, either, especially when the government can change its parameters at will.

Finally, if you're going to argue that property taxation is supposed to be a detterent for people who you are codedly calling 'unsophisticated' (whether or accurate or not, that reads to me as 'poor people') to 'rash' purchases, well, thank you for demonstrating my point that it's tax with regressive outcomes.

If you can show me a citation indicating that property tax keeps housing prices 'rational', I'd give it a second thought.
Hear hear, re. open offices. Sometimes, one just wants quiet - not music, not chatter, not white noise. Not to mention the long-term hearing damage that comes as a result of being forced to listen to loud music to drown out the irrelevant chatter when you are just trying to write some code. Sad days.
How We Found All Of Optimizely’s Clients
Same setup used to circumvent US encryption exportation laws. Tens of thousands of pages of code, printed and scanned from books.
An exchange rate will tell you absolutely zero about one currencies relative worth to another. By your logic, someone in Japan, whose currency trades about 100 to 1 USD, would have about the same buying power as you per USD, when in fact, assuming you're both earning the same in USD, you would almost certainly have much, much more purchasing power.

To accurately compare purchasing power among currencies, you need to use a metric like Purchase Power Parity (PPP):
http://en.wikipedia.org/wiki/Purchasing_power_parity
For the past 5 years or so, we've managed to take good advantage of the fact that we had a diversity of ciphersuites, even though each of the pre-1.1 ciphersuites had problems. Trying to lock down a single known good ciphersuite would be drawing exactly the wrong lesson from recent history.
Coincidentally, I recently built a similar service as a week-long project to solve the same problem for a client.

I tried idonethis, but found the interface confusing and the pricing prohibitive.

http://simplestatus.io
In fairness to the US intelligence agencies, this might have been a verification of their claims since they are looking fairly aggressively for oil sources outside of the middle east. The President or higher ups in the DoD would seek this information for a lot of reasons. Unfortunately people are distrustful because our country has taken so much unscrupulous action for energy in the past.
Hahaha wow whatever you need to tell yourself to feel better.
The hypothesis that depression comes from a deficiency of serotonin is, from what I understand, no longer considered viable among research psychiatrists[0], although it's still widely believed by practitioners and the general public. Which isn't to say that serotonin-dousing couldn't still be a viable treatment, but your brain doesn't have an ibuprofen deficiency just because Advil takes care of your headaches.

[0] http://www.npr.org/blogs/health/2012/01/23/145525853/when-it...
The summary paragraph sums up the only thing I was thinking of while reading this:

"Finally, we should discuss the important issue of whether this whole SGX, while providing many great benefits for system architects, should really be blindly trusted? What are the chances of Intel building in backdoors there and exposing those to the NSA? Is there any difference in trusting Intel processors today vs. trusting the SGX as a basis of security model of all software in the future?"

There is no full trust of any modern hardware or commercial software or even complex OSS software anymore. None. I made poked fun at some of my paranoid technical buddies in the '90s, but so far have apologized recently. Their customized systems don't seem so silly anymore.
Thanks! That's an interesting read. We were actually wondering what was the maximum number of items in References field but couldn't find any. This RFC does give an answer[1]!

[1] http://tools.ietf.org/html/rfc5322#page-25

EDIT: fixed typo
It sounds to me like he wants a PEG parser - PEG is a formalization of a recursive descent parsers that operates in a single pass and can quite easily handle the "parse different things in different contexts" problem (like the inline assembly the author mentions).

It's not terribly mature yet, but I've been poking away at building a PEG parser generator myself (mostly as an exercise to learn C++11): https://github.com/bruceiv/egg
Holmes has a set of lectures on Udemy about building a team, if you want to learn how to put together a board like that:

https://www.udemy.com/the-essentials-of-team-building/
Well you did a much better job describing how you define retrospective vs. prospective trial design. I still think the way you are defining it is not accurate, since retrospective trial designs have nothing to do with self-selection. That is a separate matter. All retrospective means is "looks back in time" at data that has already been collected.

However, you argument stills doesn't hold much water. How can a psychiatric drug be used retrospectively unless it has already been approved for use? If you're complaining about trial data on off-label use, then I won't argue, but the FDA does not accept retrospective trials to support drug approval.
Improve Your Open Source Project Adoption by Catering to Integrators
Hey Adam, what was it about the interface particularly that you found confusing? We're working on improving it and I'd love your feedback on this.
I too had an Economist subscription (thankfully due to airline points) which I did not renew. Sometimes, it felt like Fox News with an English accent. It was always a good read but the monolithic "insight" started to rankle after a while. Also, I sometimes read a given magazine many months after I received it - it was fun to compare reality vs. what was predicted in the magazine.
I actually have been learning Rust, and since I'm also interested in bare metal programming, I immediately looked into this project when it was on the #rustlang tag on Twitter.

Please let me know if you try to use it for your project, I'm eager to hear if it works for you. llvm is a fascinating project -- if you get it working on your STM32, you also may eventually be able to also use it on Arduino since an avr target for llvm is in the works.
I think by attempting to patch the system, you are merely shifting the corner cases which are unfair. And the more byzantine the rules system is, the fundamentally unfair it is to the politically and economically disposessed, because their ability to deal with the bureaucracy (and the rules system) is diminished. To wit: the more rules you have, the more difficult internal consistency becomes, and the government will naturally tend to bin individual citizens into whichever category they can extract the most revenue from, instead of doing due research into the highest efficiency for the taxpayer. The responsibility to identify the deductions falls on the taxed. This becomes regressive, as the ability of the wealthy to argue for and appeal their binning category to the one that is 'rightful' in your byzantine system, is greater than that of the poor.

And the unfairness will always over time become skewed towards the wealthy and powerful (municipal authority:'well obviously we are authorized to make exceptions like X as precedented by our rules system in code ZZZ, subparagraph Q; if we give an advantage to corporation Y by implementing change T, it may not necessarily be in the spirit of total fairness - but we will create jobs! and thus it will be in the public interest'). If fairness is your dominant value, the only perfectly fair and sustainable solution is zero. If progressive redistribution is your dominant value, you will wind up with a lot of difficulty over the 'how much is enough' question, and the implementation will almost always find a way to be anti-progressive.
Would you mind sharing some screenshots or provide a demo account to tour the interface?

It wouldn't hurt to add a signup button at the top of the page either.
<rant>
Something being missed by this discussion (and many offshoring discussions) is that many consulting firms design maintenance costs into their business model. They undercut everyone with low prices for a poorly engineered product, knowing they can churn additional hours/sales in "upgrades", "maintenance" etc.

When you pay me $60 an hour (or more) to design you a component of your system, it will be SOLID OO designs, quite reusable, DRY, tested (unit tested) and better in many other ways. Where as most of the code I've seen come from bad agencies basically do "class Main { function doItAll() { /* Here is the entire program */ } };"

Which is why it will cost more in the long run. If you want something added or made similar, they'll copy and paste instead of inheriting or using traits or other language constructs to keep it DRY. If you want to know if the system has regression, they'll shrug, because they either do not test, or they just write the tests to pass the way the code currently works, not testing the component in general. If you're planning on closing business in 12 months, then maybe its not worth it to invest in a scalable, changeable infrastructure. If you're planning on being in business for a long time, then invest the capital to develop your business :D .

ok </rant>
My personal experience is that, I like how mutt looks and the fact that I'm able to deal with emails in CLI. The reason I'm not using it as my main email client (yet) is that I can't remember all shortcuts and I don't know enough what exactly each keystroke does to my emails and email server. These can all be fixed by reading docs and more practice though. I guess it's the same thing as vim. Once you are used to it, it becomes the favorite.
I even heard mathematicians say that the distinction between pure and applied mathematics is mostly for historical reasons.

It must have been applied mathematician, for I cannot even imagine pure mathematician uttering anything like this.

I mean, seriously, I know quite a lot of modern pure mathematics, and for most of it I cannot picture even far-fetched connection with anything existing in real world, not to mention an actual application in solving some problem that wasn't created only for this application.

Most of the time, for almost every field of mathematics, the way it works is that for an enormous amount of knowledge, and enormous amount of research happening and results and papers being published, only very, very small amount will actually get applied any time soon (soon as in next 200 years). For some fields, like calculus, or probability, or partial differential equations, amount of applicable stuff is larger (mostly it's just old, one or two centuries old stuff anyway), and for other fields, like say homological algebra, or algebraic topology, or descriptive set theory, the applicable stuff is almost nonexistent - I'll buy a beer to anyone who'll point me to an application of descriptive set theory to any real life problem.

Almost all of the mathematics existing is purely abstract, and not applicable to real world, and I find it hard to even imagine anyone trying to argue otherwise. One can argue that what now is considered abstract and not applicable can become very useful in real life problems in future, and indeed, it happens quite often, but I think it will not be much, since we're applying to real life problems only a small fraction of 200 years old mathematics today anyway.
Much appreciated, Allen. That means a lot, especially because I'm a big fan of what you're doing with CircleCI.
First, you should absolutely write couple of parsers by hand first and then repeat this exercise now and then.

I understand the reasons why author does not use parser generators. However, if you are writing a parser for serious production use I urge you to seriously consider parser generator instead of going manual route. Here is why/

Parser generators are akin to compilers. They require certain constraints to be met but in return they generate extremely efficient parsing code. For classes of languages for which parser generators exist, you cannot beat generator with handwritten code neither in terms of parsing nor in terms of maintainability.

Citing shift-reduce conflicts as one of the reasons to write parser by hand is akin to resorting to assembly being frustrated with C compiler errors.

Yes, there are cases when hand-written parsers are preferred. gcc switched for parsing of C/C++ from flex/bison to handwritten parser during 3.x and clang also has handwritten parser.

But this is because C and C++ are languages with context-dependent grammar and C++ syntax became increasingly arcane over the years. You constantly have to resort to tricks during C++ parsing. For example, to properly parse C++ class definition, you need to pass it two times, first reading declarations and only then both declaration and method bodies. You also need to resort to tricks and heuristics if you want to parse '>>' as part of nested template instead of right shift operator etc etc.

Almost always that kind of complicated, context-dependent grammar makes it possible (and in case of Perl, even very easy) to write WTF code.
that's my startup! boom
Yikes, is it really invalid in IE? I left those in cause I was constantly debugging that progress bar, but I'll definitely take them out if they're causing problems for anyone.
Open letter to Glenn Greenwald asking for names to be named
As a long time freelancer with a few purchased gigs as well:

Quality of the workers or the turned in work is directly linked to the budget of a project. I've had many conversations on both sides of the table, where there was a miss-match and an eventual agreement to either bump up the budget or to lower the expectation. There's still risk in eventually receiving lame work, but
I don't think that is the status quo.

There is a larger than obvious amount of bot or automatic submitters tainting and lowering the overall quality of the pool. It is very easy to sort them out, but it is noise nevertheless. Quality filters and machine taught spam detection would deal a great boost to overall usability of all of these sites.

Now, communication and missed deadlines will deviate wildly because most of the developers are not able to sustain a living doing just elance, odesk or whichever. Honesty and setting expectations at the beginning usually solves this problem. Now, there has been a steady build up of downward pressure from contract owners to expect full availability or a similar version there of. Most of them don't have the budget to back it up. Shit happens.

I found and worked with talented folks through 3 of the 4 mentioned sites and I would have to say that it is not an issue. The issue is actually finding them in short time, and that's where buck stops in my point of view.

I think there is a large opportunity to impress the market by shaving off the amount of time to find quality devs and firms. I think other sites have began doing something along those lines by curating the offers and doing away with the meat-market environment.

Overall, I think the budgets are low, developers pick up multiple gigs, some projects get delayed or rushed and compromise is the name of the game.
We called this "HyperCard" in 1987.
The Phone That Could Not Be Killed
This must be why none of the new Kindles have page forward/backward buttons, despite their providing a decidedly superior experience to the awful touch UI.

Kidding (probably)