skysight-inc/HackerNews huggingface dataset:
pedantic: Conceptually, the public key is n, e and the private key is n, d. The other values you mention are secret, in that they can be used to derive d, but aren't the private key. OpenSSL keeps some intermediate values for performance, but they aren't strictly required for RSA to work.
> I have no figures to back this up, but I strongly suspect the % of equivalent mutants will be highly dependent on coding style and the domain in which the code operates.

Agreed. In everything I've written, at least, I can identify multiple places where such equivalent mutants do exist, even with just the default operators. (In particular, hashcode methods - there are very few mutators that break the contract of a hashcode method, though removing entropy in most cases) But I can easily see that not being the case with other coding styles.

Are the mutations done documented anywhere? I had to look through the source to see what's done.
You're in a filter bubble because you're doing your own curation. Historically, many if not most thinking people let someone else do their curation, ie they read a good newspaper or magazine.

Magazines such as The Economist and New Scientist have journalists and editors who keep a close eye on significant parts of the world and then report them in digestible form.

With a good newspaper or magazine, you're exposed to a lot of subjects that you wouldn't normally see in your own filter bubble. Some of those you will find interesting enough to read, and reading even a few of those stories will expand your horizons.
You could work on things for yourself. As a 16 yr old presumably living with your parents there's no risk.

I'd suggest starting with a small mobile iPhone or Android app. Make a little bit of side money while building a portfolio you can use to your advantage later.
Is the high % of mac users still on 2.7 partly because that is what OS X ships with?
Previous discussion (10 days ago) https://news.ycombinator.com/item?id=9458829
If you're offered an intercompany transfer, why don't you counteroffer with something like:

"I'd love a change to test-drive the day-to-day aspects of the job before I can give a full-throated yes. Why don't I spend a month in this new role before we proceed?"
From the site:

Google Summer of Code is a global program that offers post-secondary student developers ages 18 and older stipends to write code for various open source software projects.
What are the things that could urgently need block size increases?
I worked for a physicist for a number of years who refused to give up on Fortran. It wasn't for (computer) performance reasons. It was because he could quickly get his ideas into code with Fortran. He wasn't interested in computing for the sake of computing.
A good place to start learning about finance is always http://www.investopedia.com/.
Further I can recommend reading about modern portfolio theory and the correlation between risk and return: http://en.wikipedia.org/wiki/Modern_portfolio_theory
This isn't bad: https://smartasset.com/infographic/startup

Although it's not as clear as a spreadsheet would be, I think it's easier to start with.
You need screenshots, more detailed descriptions, a video, anything will help.
How would you go about finding a concept to build a app around? You don't want to end up building a so-called "sitcom" app which no one uses.
C is not my thing so a few years ago trying to sort out how a VM works, I created a VM in Ruby.

Practical? Not in the least. But, it was a good weekend's worth of fun.

https://github.com/patrickjonesdotca/carban
> f2py

This is a Fortran-to-Python interface, and has some support for Python 3 so far as I can tell.
Sure but do you think it's a barrier to entry or is it acceptable to learn on the job?
I don't have any examples of code I wrote when I was in my early 20s, but definitely I'm sure I was quite naive. Especially if you consider development process, I had absolutely no idea what it took to build successful teams.

At around 30 I started to clue in and I can recall some designs which were actually not too bad in retrospect. Of course, a lot of the stuff that is taken for granted now (design patterns, TDD, etc) was not well known at that time and so I was exploring and learning things that few other people had experience with.

As another person posted, I'm also nearing 50. I would say that my code has improved a fair amount and I have learned a lot of other techniques which I didn't really know in my 30s (like FP). Rather than technique, though, I think the biggest thing I've learned is patience. I code very slowly compared to how I coded 20 years ago, but I think a lot more about every line. Kent Beck once said that when he wrote Smalltalk Best Practices that he started to evaluate every keystroke and to think why he was pressing that key. I find that I am doing that a lot now and it is very beneficial. The advice I give the young guys on the team the most is, "Stop typing so fast! You need to think about what you are typing" :-)

As I said, the biggest revelations for me are less about pure technique and more about how everything fits together. For example, my less experienced colleagues are often distraught over the perceived sins of the other people on the team. They worry endlessly about how to stop the "crappy programmers" (in their eyes) from "ruining" the code base. Nearly 50 year old me weighs the options and realizes that complaining/campaigning/scheming/negotiating/etc will take an order of magnitude more time than refactoring and will suck the fun out of the room. I like refactoring code and I hate arguing, and besides young people tend to be crap at cleaning (in general). So I clean things and eventually most of the others catch on -- not everybody, but it's enough.

I still get stressed out a lot and I'm hoping by the time I hit 60 I will have resolved those issues :-)
Miami Vacation
Look first for local software development shops and contact the CTO, group manager, or if available, HR about your interests. Consider looking first for services companies (e.g. web development shops, digital agencies, etc.) as they typically can use an extra set of hands. LinkedIn should be a good source of contacts. Explain your background and that you are interested in shadowing or being an intern. Even though you may be beyond the abilities of an intern, take it if the opportunity looks interesting and you have an opportunity to learn and expand your skills.

Be prepared to show your work and have something in a document, or better a portfolio website, describing your background and that you can send on request.

If that doesn't produce results, you could try expanding your search to companies that are not in your area, but it will likely be more difficult.
The first photo in this article pretty much sums it up: someone echoing "banana" to debug PHP. Nailed my life.

Advice to author: learn to stop worrying and love the bomb :)
You aren't asking the right question.

Why do you need investors?

Yes, it's true that many startups get handouts from investors _just because_. That's just nepotism at work. If you have to ask, then you aren't part of that, so you have to make a real case for what you would need money for. It's supposed to be an "investment", after all.
Established venture firms may have multiple vehicles (e.g. a seed fund, main fund, or growth fund), but the majority of venture firms tend to invest out of one vehicle at a time (there may be a short period of overlap when new funds are raised).

If you are not an active investor, getting quality access to information about funds can be difficult. I'd recommend the firm's website and crunchbase as free datasources. There are other, higher quality sources, but you need to pay for access (e.g. dow jones venture source).
There's a difference between generating business value and generating profit. It's common for founders to get liquidity during financing events and this typically involves a sale of equity (i.e. transfer of business value from the founder to another stakeholder).

This is distinct than the company becoming profitable; many companies will increase in value while not being profitable.

The original commenter is making this comment I presume because he/she thinks Spotify is a mature enough business where it should be generating profits instead of operating at a deficit in order to grow and grab market share.
Thanks for answering. I guess then what you had in mind was a change in the syntax of the shell itself, right? I'm a casual user of POSIX utilities and the typical shells, and have yet to try Perl! In any event, your last sentence pretty much validates what I had in mind. Thanks again.
Depth-Cull Optimization of 2D Scenes for 3D Graphics Hardware [pdf]
You probably need users before you can get investors.

Look at it from their perspective -- why would they take college students seriously until you can lead with "we have X000 users"?

That said, there's no harm approaching them -- try to get a sense of what would need to change before they'd be sold on investing. Even better if you can get it in writing.
> You don't want to end up building a so-called "sitcom" app which no one uses.

Why not? The point is to learn. Good software engineering skills take years of practice and experience.

One good experience to have is finding out that something you enjoy building might not be something people enjoy using.
I've never heard a single thing about concerns over PVC until today. Before I even saw this article on HN I was in the process of researching it because a friend brought up how their dad told them not to drink the water from their faucet because it's running through PVC. I'm in the process of buying a house that has new PVC all over and I can't find any reliable info on this concern. Does anyone here have any sources to share?
Those other trade deals were negotiated in secret before being presented to Congress for a vote, or to the public if it was a simple bilateral agreement without treaty powers.

Do we negotiate nuclear policy iwth Iran on live TV with a big audience in the room? Of course not. Do we negotiate clogal warming agreements in public? No. The whole point of international negotiation is to sit down and be able to work out your differences in a de-politicized manner and then submit an agreement to legislatures for approval.

I swear, I've never seen so much paranoid bullshit as I have about his TPP thing. This is diplomacy, not fucking reality TV.
Does donation matching work?
I agree. Public dollars should, as much as possible, be used to implement and advance open software and hardware. It's no longer just about "free" as in no cost, it's free as in no contract, no lock-in; and not "no one owns it" but rather "everyone owns it." There's a certain obligation and clear benefit for everyone to make it better, including easier to implement.
https://www.youtube.com/watch?v=o5kCITsTLtk
Google's 'Bench' Program for Executives
It doesn't sound particularly calm and rational to me. We already know that rice isn't nutritionally adequate (that's why it's usually combined with beans). Why should a new variety of rice need to be more nutritionally adequate than older varieties?
That's just absurd. The rational thing is to be neutral about it until it comes in front of Congress for a vote. At that point you can read it and decide whether you want your representative to support or oppose it.
Those must be some strong magnets, effecting people even before getting under it's effects!
It doesn't matter if you would like investors. You need to make investors want to own a chunk of your business so much that they'll give you a good amount of cash despite the dismal odds of failure for very early stage startups, such as yours that you say is in beta. To do that you have to paint a picture of how big this concept could get and how roughly you intend to get there. Assuming you have your pitch well formulated, then as for actual logistics of how to contact investors, typically having trusted people vouch for you is a good first step. You can contact people directly too. Do so succinctly and with an eye to why you think they in particular would be interested. Friends and family are also a typical source of very initial capital. Since at the earliest stage all anyone has to go on is how competent you are, and to some extent how compelling the concept is. People who know you are much better judges of how competent you are than are total strangers. Other startup founders you may know may also be able to provide introductions to angel investors. Prepare for it bang your head against the wall. Raising seed capital is hard and frustrating, but as they say, it's still one of the simplest things you'll do in the life of your startup.
ctypes overhead is horrendous though, at least in CPython (I don't know about PyPy). Fine if you're doing array operations on huge arrays, but not so if you have lots of small objects.

I wanted to use ctypes to wrap a C library for a recent project (for the ease of installation and development that you mention) but had to give up when it turned out to be more than 10x slower than a wrapper written in Cython, and barely faster than doing a pure Python implementation of the C library itself.
The first thing you need to do is get traction. If you have traction, you will start getting inbound interest from investors.

Connect with other experienced founders relevant to your industry. Build trust, and they will introduce you to their investors.

Most investors don't respond to cold emails. Introductions from trusted people is the primary source for most investors.

I would recommend you to apply to incubators like Y Combinator and TechStars. They don't require an introduction, they will help you groom and connect you with other investors. Their alumni network is also very helpful, which can open a lot of doors for you.
The technology had nothing to do with Spotify winning. There were probably hundreds of startups that built cool music tech but they all failed because they couldn't get the licenses. As far as I know the true story about why the RIAA gave Spotify the green light after saying no to so many before them hasn't been told.

Edited for duh...
Why do you want investors should be your first question. Raising money means dilution and being put on a vesting schedule along with having to deal with liquidation preferences or headaches of convertible debt (see this book[1] to understand some of these terms). Second, finding investors usually takes connections. For young CS grads, easiest way would be through the university's tech commercialization office. Another would be an accelerator or incubator. Then you could reach out to mutual connections in your network to find angel investors or seed funds. Hope that helps. If you need more help feel free to contact me (my email is in my profile). Good luck!

1) http://www.amazon.com/Venture-Deals-Smarter-Lawyer-Capitalis...
How about... http://en.wikipedia.org/wiki/Google_Code-in ?
Thanks for your reply. Yes, the ready availability of the code would be a plus. In my mind utilities like grep or sort are very sensitive in terms of performance, but that's just an impression.
This phenomenon is called the j-curve. Its not that the IRR needs to be sky-high, rather that the fair value of the fund's aggregate investments need to appreciate above the cumulative amount of fees drawn before the IRR can be positive.

http://en.wikipedia.org/wiki/J_curve#Private_equity
I think something similar happens with programmers:

* I vaguely remember ambling around when I first started writing C programs, using a debugger whenever it broke, and generally just slapping for loops and variables together until it worked. I had some intuition for how things worked, but it often took hours of hard debugging. I perceived code purely operationally - "This line sets this variable to 5".

* At some point, you start structuring things into modules, subroutines, etc. You might learn 'best practices' and try intently to practice each one. You'll unit test everything, or otherwise hold strong opinions on how things should be done. Debugging is approached in a more scientific manner. You start to feel like you can get a handle on just about any bug, since you have tools and methods for reasoning about them. There is a lot of focus on verifying code, but not so much on validating. I perceived sections of code as implementing some intuitive concept - "This class represents a bullet, and its methods are reasonable things for working with bullets"

* Now, I rarely spend any time worrying about the best practice of the day just for the sake of it. I generally focus on getting the current task done, but I intuitively know when to apply a certain practice. For example, I might write a test or two after writing algorithmic code. I rarely spend any time at all debugging my own code, since it tends to just work. Since verification is so easy, most of my focus is on validation: "Am I even building the right thing? Will this way of laying things out have acceptable performance characteristics? Does this way of laying out the types mirror how I think about the problem? Is everything I'm writing necessary to solve the problem?" I perceive most code as a formless soup of syntax trees with an operational semantics, and reason about the segments of the trees themselves.

I imagine that Terence's breakdown is relevant to many professions besides just mathematics.
Cool. Did Brendan Eich write it? What's he doing these days?

Keep up the good work Mozilla.

edit: I see MANY people contributed! You can too! https://developer.mozilla.org/en-US/docs/Mozilla/Connect. It still would be cool if Eich could act as an "editor" to JS related articles!
To force Congress into an up-or-down vote on the merits of the whole package instead of pointless thread-pulling that will cause an agreement to founder. There are 12 countries that are a party to the TPP. If we are to wait for 12 legislatures to debate and amend and re-amend then nothing will ever get done; there are times when a simple yes or no vote is more appropriate.

It's like people don't seem to understand the point of having an executive branch in the first place. This sort of thing is precisely why we have one, and why the Constitution specifically empowers the President to negotiate treaties 'with the advice and consent of the senate' - not with the endless amendments and horse-trading of Congress as a whole that bedevils a great deal of domestic legislation.
There's only one path to investment that doesn't involve being born on 3rd base or getting unbelievably lucky. It's 3 things:

1. Grow. Grow convincingly on your own, without investment. Be confident in your product, know where users come from, in fact know everything about your product and your market (everything), and have a graph that is up and to the right.

2. Network. Go to meetups, clubs, professors, friends, family friends, etc and leverage the fact that you have a "growing" app to make those people EXCITED to introduce you to people with money.

3. When you meet investors, don't go for the hard sell just let them ask questions. Keep updating them as growth milestones (even if it's just every 2 weeks how much you grew) are achieved. Tell them you're raising money early on but that you're not sure when - pick the right moment to say "we're raising" when growth AND # of investors you've met is at peak.

If you're like me when I first started out, you're hearing this and thinking "ok, anybody got any easier ideas? That sounds basically impossible I'm kind of looking for a silver bullet here - I think I deserve it I mean everyone is getting seed money and we're pretty good!".

There's no silver bullet. I'm telling you straight up it doesn't exist, especially if you haven't built something successful before. You have to grind, you have to grow, and you have to network. And it takes time. If you're not ready for that, consider your app a side project and move on.
I'm currently working on a new project using Python 2.6. You see, I'm creating an analysis tool that absolutely must run on an old, isolated (no internet connection) RedHat system, and have access to only a very limited number of packages I can install. Which, in my case, means Python 2.6, fairly old versions of NumPy and SciPy, and Tk for the GUI.

This is actually my first significant project in Python, so naturally I wanted to use the latest and greatest (learning opportunity and all), but no such luck.
Just build something - it really doesn't matter what. You have a good window of time where you have very little requirements in terms of paying rent, bills, etc., so take advantage of that and just write as much code as you possibly can.
The Transhumanist Party supports a basic income (along with free education)
No, that is absolutely, totally untrue. Please, educate yourself on the basics before making such foolish claims: http://en.wikipedia.org/wiki/Fast_track_%28trade%29
http://www.reddit.com/r/forhire
My favorite example of mathematics that blends intuition and rigor comes from the works of Archimedes of Syracuse: the mechanical method used to intuit results such as the area of a parabola, followed by the method of exhaustion used to prove the result rigorously.

In the mechanical method, Archimedes imagined, for example, a section of a parabola balancing with a triangle, using the law of the lever (which he also discovered) to derive the area necessary to achieve said balance. He then used inscribed and circumscribed polygons to prove upper and lower bounds on the area thus derived, with (in modern parlance) the two bounds converging in the limit n → ∞, thereby establishing the result. The rigorous method of exhaustion (due originally to Archimedes' predecessor Eudoxus) is effectively equivalent to integral calculus (~2000 years ahead of its time), but guessing the right answer would in many cases have been difficult or impossible without the non-rigorous mechanical method.

Incidentally, the mechanical method itself might have been lost to history had it not been for the discovery of the Archimedes Palimpsest in a medieval prayer book [1], which contains the only known copy of the work describing it. Often called simply The Method, it takes the form of a letter from Archimedes to Eratosthenes, the chief librarian of the Library of Alexandria. When I had occasion to see some original pages of the palimpsest last year (at The Huntington Library in San Marino, adjacent to Pasadena, California), I was struck by the collegial tone of the letter, whose genuine human warmth was instantly recognizable even across two millennia.

[1]: http://en.wikipedia.org/wiki/Archimedes_Palimpsest
I agree with you in principle but find that code editors let me down in that regard.

Say I split a function up into a few sub-functions because it's getting big. Now I have the problem that I'm jumping forwards and backwards through the code when I want to explore what that function does:

SomeMassiveFunction()
{
SubfunctionA();
SubfunctionB();
SubfunctionC();
SubfunctionD();
}

SubfunctionA()
{
}
....

In this case, SubfunctionC() might end up a few pages down in source code. So now it's a context switch to go there and then go back.

Now this can be somewhat avoided with good function names (so you don't HAVE to jump backwards and forwards) and keyboard shortcuts (to make the process quicker), but it's still a trade-off that I think needs to be kept in mind.
Given the ideas that Star Trek and other SciFi planted into our minds, it is sobering - to say the least - how much patience actual space exploration requires.

Having said that, it is, of course, totally awesome to see something like that, even if it looks like the graphics of a 1980s computer game. No plane, no ship, no car in use on earth has ever traveled even remote as far as New Horizons has. You could spend a lifetime zipping around the globe and still come nowhere near the distance this spacecraft has traveled...