skysight-inc/HackerNews huggingface dataset:
> Can run the code... but, not the tests, which would make in-place refactors considerably easier.

That's definitely something that I would love to implement in the future - if I can find a way to make it viable. This was just v1 to see if there is even a path that makes sense.

>Clicking Gear for settings doesn't go back to edit window when you're done and you click the Gear again, which is how I first tried to get back to the editor.

Yeh, I am using the API for Glot.io -- which provides no way to customize that iFrame. So I am stuck with that functionality for now.

>No place to set "license" specifically for each piece (and maybe a default in your account settings) making it impossible to take the code and use it without opening Pandora's box.

Ohh...this is interesting. Never considered the 'license' bit. Is that really an issue though? You can't add a license on SO, and that doesn't seem to stop people from pasting code snippets.

>So little there, and all six days ago... you could grab examples from open source projects and put them in, if you could do that while obeying the license on the code (which comes back to at least showing the license, and maybe also linking to the URL for that piece of code or project).

I agree fully, and it seems like it should be pretty easy to do from OSS projects, eh? The issue I ran into was identifying what snippets of code really needed to be refactored and why. That's the counter-intuitive bit, in order to be able to explain why something needs refactoring you have to fully understand what it does.

I can most certainly do that for some Ruby code (where most of my experience lies), but once we get into other languages I am kind of outside of my depth (to be frank).

So another alternative is to simply search GH Issues for the term "please refactor me". I tried that too, and most of the immediate stuff I found are usually too old or too basic.

That being said, if you have any suggestions on specific bits of code from OSS projects you have used that you have seen that could be a good candidate please feel free to share them.

I am definitely going to be looking myself too. It's just not as 'slam dunk' as it appears at first thought.

>As this is ultimately "one piece of code with several examples of another piece of code to replace it" despite it being for refactoring, you can imagine it'll be used for "this was a bug, this is the fixed version." Might be useful to provide specific support for that somewhere down the line.

This is very interesting and I would love to hear more about what you are thinking. Do you mean like someone would post a snippet of code that has a bug and ask for the community to fix it? Then the site would track the various iterations and show the final version? If so, that does sound intriguing and is inline with some other ideas I have.

If not, I would love to hear what you meant or just some more thoughts on potential future direction.

That being said, thanks for even taking the time to give me such a thoughtful response. I really appreciate it.
Not to take anything away from this article, but the proposition that AAVE is a dialect is self-evident to anyone with a background in a language with strong dialects. German and UK English come lightly to mind.

The politics of the debate were interesting and should not be ignored. For many people around Oakland the question of whether Ebonics is a dialect was a canard. At least for me the real issue was that the Oakland schools were doing an awful job providing basic education to their students. The Ebonics debate was a distraction from fixing real problems. Oakland schools ended up being taken over by the state a few years later [1].

[1] http://www.eastbaytimes.com/ci_12753927
From SEAL to Silicon Valley, special ops vets head to startups
> If rebuilding the world from source is an option, changing the ABI is an option.

It's an option ... but not a very good one.

It tends to create an unstable environment that requires a centralized organization just to keep it working, precluding a healthy diverse software ecosystem.

This is a major reason why it's very difficult to distribute binary packages when operating externally to the distribution packagers, and why commercial software distribution on Linux is a massive pain in the ass.
Thanks much :)
Well this article throws a bunch of different things out there suggesting that, first, Bulgaria will adopt verified electronic voting, and second, that electronic voting is sound enough and ready for deployment. Both of these points are false or unclear at best. Then the blog seems to suggest there is some sort of middle ground between verified voting and non-verified voting and it's OK to make some half-assed step in this direction, which is exactly what the video warns against.

When people talk about electronic voting, typically this means the US-type of voting. And when someone talks about verifiable electronic voting, then they should start by making it clear that this is orders of magnitude more ambitious, it hasn't been deployed anywhere and Bulgaria will be the first country in the world to do it. This is a project of historical scale including the known practical difficulties with the current methods. It should not be advertised like a proven system working in EU and US like it is now. And like I said even if Bulgaria really adopts any sort of verifiable voting there will be so many confused people due to the nature of the process it will skew the results.

Finally, again as the video explains paper vote counting may not be perfect, but it does require more people to involved in the fraud. This is a very important point. Results are available per area and each party makes sure the sum makes sense at least from a small sample.
I think technology is more accessible to people, and even if the general public doesn't understand it they at least feel they can refuse to participate. But it's hard to avoid a bank account and the finance industry manipulates the economy in secretive or abstract ways, which makes them distant and incomprehensible.
Yeh the domain name 'refactorme.com' was taken, so I had to look for an alternative.

My wife suggested the 'plz' and while it wasn't perfect it was much better than the others I thought about...so in the spirit of shipping something, I ran with it :)
I didn't downvote you. I think your comments respect the standard of Hacker News. They offer me the opportunity to express and justify my current understanding. I shouldn't have qualified your comment as stupid. My bad.
There's this weird snobbishness about fMRI: it's uniquely terrible, the people are hacks, etc. It seems particularly common amongst first and second-year grad students who are doing something they think is "harder" science. I hate it.

In the right hands, fMRI can be a really powerful technique for probing neural activity in healthy human subjects; in fact, it's one of the only ways to do so that has decent spatial resolution and thus lets you link brain structure and function.

It certainly does have problems. There are plenty of ways to subtly mess up the data analysis or over-interpret results. The experimental design is often lacking, etc.

However, I think these largely reflect the very low barrier of entry to fMRI research--all you really need is a laptop and somewhere willing to sell you scanner time (almost all major universities or hospitals)--rather than some intrinsic limitation of the field. The good work remains very good.
France is still digging up and disposing of tons of unexploded ordnance from WWI. About 900 tons a year, every year.
Fwiw there's a response to an earlier (preprint) version of that paper from some of the developers of the packages in question.

Preprint version of the "Cluster failure" paper, from last year: http://arxiv.org/abs/1511.01863

Response: http://arxiv.org/abs/1606.08199
This is a major flaw of C++'s ABI design, unfortunately, and one reason why we see so few supported ABI-stable C++ libraries shipped with major platforms.

Most people just have to incorporate their C++ dependencies directly instead, as there is no supported ABI.
Great idea. The truth of the matter though is, I don't really want to make it too restrictive.

I would love to see what people use it for and then we can kinda pivot from there.

The general purpose is, do you have some code that you think could do with some loving, post it and let's see if we can get the community to refactor it.

If enough people start using it for other things, then I would definitely shift in that direction if that's where the usage is taking me.
The classic joke is that Elon runs on Mars time, where 1 Mars year is about 1.8 Earth years. But yes, both Tesla and SpaceX deliver everything they say they will, and usually a lot more with all kinds of extra surprises - but it usually takes 1.8 times longer than they say it will. I'm okay with that, especially considering the incredible achievements of both companies at their beginnings. I think it's also reasonable to suggest that as both companies grow and stabilize their product lines and production facilities, their time estimates might get better. Or maybe not.
Why Trump is in trouble
You target the functionality that resides the application, and its integration with other software. However, you don't need to test Windows functionality, that's for Windows developers to do. 'Total test coverage' is about testing the application under test, not every component of the OS it builds upon.
I just want to throw this in here for some more context:

"During The Somme, the British bombardment consisted of 1,537 guns firing over 1,500,000 shells over a period of 168 hours averaging 8,929 shells fired per minute."

That is just... staggering. I can't find a source for it, but I remember some factoid stating that on average it took several hundred shells to kill one soldier. That's not to say they had to take several hundred hits, but that on average that's how many shells it took to rack up one kill.

(from: http://www.tommy1418.com/wwi-facts--figures--myths.html)

*Edit for caps only
It's not exactly "ashamed" I think, more like cautious. I mean, I've read multiple reports of people being beaten bloody on a candidate rally, so people would just prefer to stay out of trouble - even if they are proud of their choice, why they would risk talking about it publicly to random stranger? I mean, the pollster probably won't beat them up, but what if some crazy person overhears it and follows them and makes trouble? Nobody needs that. Sad, but such intolerance is part of the culture in US, many people just don't get "I disagree with you, but I respect your right to have your own opinion".
Developers should be doing a lot of things. In my experience the trouble is that most developers are too optimistic and tend to neglect negative test cases. So most teams still need specialist testers to ensure acceptable quality.
If you have to change it in six places it just means that you did something wrong. Keeping those six places in the single file is not the solution either: next time you will need something similar, but not exactly the same you will copy that file. And next you will find yourself changing twelve places.
Shitty Listings helped us find a lot of great repeat investor buyers. We actually (probably because of the gimmicky name) got more traffic from Shitty Listings than the launch of Open Listings proper and ended up tying it into our main product -- you can now get a Shitty Feed (tm;) on openlistings.com to see only fixers.

http://www.shittylistings.com/
Could you please edit that quote to not use all caps? (per https://news.ycombinator.com/newsguidelines.html)
It's been a while since I read it, but his experimental evidence was a lot of tiny studies with no replication. I tend to not view a single study as strong evidence at all, especially in the social sciences. And history hasn't been particularly kind to many of those findings.

I went in really wanting to love the book, it was universally praised and I was pretty high on Ariely at the time, but even with that bias I still found large chunks quite unconvincing.

Perhaps it was just the writing style or something, or the fact that the beginning of the book focused a lot on those priming studies at a time when that entire area of research was profoundly embarrassing the social sciences.

(re: Gladwell, that's a good way of putting it, it was uncomfortably Gladwellian! Not that level obviously, but not far enough away!)
> Dividing them up like this the typical "just shows up" person is purely stimulus driven. Nothing happens if you don't tell them to do exactly something. They won't tell you they're blocked on Bob sending a purchase order for a month. They won't tell you because you didn't ask. You didn't ask so they just... they just do nothing.

I'm sorry but I'd argue that I cared more when I was younger (mostly because I was stupid). I've spent entire days in someone else's cubicle (not so much pair programming as me standing guard against distractions such as business analysts and quality assurance who apparently kept popping in) making sure they finish their part of work.

Actual code writing for me was fairly easy once the roadblocks got out of the way.

I've told people to shut up in meetings when they start going off in tangents. Clearly, it was not good for my career.
In Brazil the small-talk culture is also strongly present. I can't speak for all places in the US, but definitely more than NY. I also was able to notice the same type of behavior in Venezuela, Uruguay and Peru.

Maybe West could be replaced by West-of-the-Atlantic?
signals and slots seem like a way of introducing an extra layer of type safety and explicitness - you cannot accidentally pass the wrong function pointer to a handler, and it's easier to extract your wiring graph. they don't make things all that much harder either; they add a slight bit of ceremony, but it's worth it. (mostly based on my experience using qt)
I'd be very interested in reading it if you decide to post it somewhere. I'm working on honing my own skills by reading a lot of books, through my main portfolio, and various paper portfolios.

Do you primarily manage your own money?

How difficult is it to achieve long term advantages over indexing?
How to Secure Apache with Let's Encrypt on Ubuntu 16.04
Out of curiosity, how does PCPP make enough money to hire two full-time devs? Is the ad revenue really enough?
A little over 3 years ago, my brother and I posted a Show HN about Webflow (https://news.ycombinator.com/item?id=5407499), which was just a proof-of-concept / experiment.

At the time, we had been working on Webflow day and night for 6 months with no other income coming in, we had gotten rejected from YC a few months before, I was over $50K in credit (and medical) debt, and the Show HN was our last-ditch effort to get some traction before going back to our jobs.

The post did really well - we had the #1 position for most of the day, got over 500 upvotes, and in the resulting days over 25,000 people signed up for our beta list. This gave us the confidence to keep going and helped us get into YC for the next batch.

Since then, Webflow (https://webflow.com/) has grown into a profitable business with 400K+ users all over the world, billions of website requests served, and 25 employees (also all over the world). I'm not sure any of this would have happened if the Show HN would not have taken off the way it did.

TLDR: A+, would post again ;)
Okay, thanks for the explanations. I will do my best to avoid these things in the future. Cheers.
And then if the message is corrupted you have know way of knowing. Not to mention that essentially nobody uses those modes.

Axolotl and OTR provide signatures, just that they are "non-transferrable" (so to speak). Not to mention that the actual crypto is more modern.
Haskell ArgumentDo Proposal
Tagua VM: PHP virtual machine written in Rust
"Mistakes" only in the context of language B. But if they are speaking language A, why would you even use the word "mistakes"?
Junior Front end Development weekly link sharing #19
Anyone making such claims usually has no idea what native SDK are capable of.
All of these are examples of my claim which is that all concepts in other languages can be expressed in English. Sure you might have a specfic term for the droppings of cows in some language (we have the same thing in English not that it matters), but this concept can be translated into English. It might not be as poetic, or it might not have quite the same emotional association, but it is translatable.

The concepts that can't be translated are all highly technical concepts from the cutting edge of science and technology. These often lack the vocabulary in other languages to enable them to be expressed in that language because the limited number of people that understand them only communicate to each other about them in English. There are a very large number of these scientific concepts hence there are a large number of concepts that can only be expressed in English.
In this context, about PTSD: "What if PTSD Is More Physical Than Psychological?"

> A new study supports what a small group of military researchers
> has suspected for decades: that modern warfare destroys the brain.

Cause: Brain injuries stemming from blast exposure.

http://www.nytimes.com/2016/06/12/magazine/what-if-ptsd-is-m...
So have these studies been invalidated by the software bug as well? If so, do you have any pointers? I. e. which were the infamous studies, and did they indeed use the faulty software to derive their conclusions?
I'm genuinely interested.
Sure, the comment was mixed. Both things can be true.
CPU's, GPU's, RAM, Flat Panels, HDD's, etc require billions to even do something competitive, probably protected by many patents, are relatively stable industries with little market changing breakthroughs by new companies(one counter example is Intel with it's 3DXpoint memory, but it's Intel) partly because it takes tons of money to come up with them, have(i think) a lot of impact on their relevant supply chain.

On the other hand, if you're a researcher that came up with some innovation in those technologies, it makes more sense either to license or let your startup be bought by the big companies.

And on top of that we don't have a working anti-trust system, so companies just buy their way to duopolies.
It seems like the purpose of a bombardment like that isn't to kill the soldiers outright, but to crush their advance and keep them out of your territory.
Being in my 40s and having been there (in my 20s) I can tell you they will grow to regret it.

That said, its up to people like me running teams and businesses to set the tone - encourage balance while not squandering inspired work.

Re inspired work: I once made the mistake of telling one of my employees "slow down a little, i don't want you to burn out and hate working here".
He had an astute response: "Andy, I'm inspired I have to keep working on this until its done!"
He worked weird hours - night and day for 2 or 3 days ..and when it was done I remember him needing some well deserved R&R.

The message from there on out to my teams is - if you're inspired, work. When you're done, rest. I'm not watching when you roll in in the morning, I'm watching the team's accomplishment and morale.
Pro Linux systems spelunking
Thank you for the explanation. That makes a lot of sense.

I use things other than athletic performance for that, but I've come to realize that I was nudged that way a lot by adults when I was younger.
I’m a millennial and my generation sucks
I don't think it is Google twisting the knife. Google is just trying to fix the damage done by the knife Oracle's lawyer stuck in their back in disclosing the magnitude of their deal with Apple.
Speaking as someone who worked in the past for a government contractor (DoD, so these issues may not be entirely the same with the feds, but I bet they're very similar), the issue isn't solely that bureaucrats don't get tech, it's also that the bureaucratic red tape that evolved to try and keep costs down has instead led to them rising, -especially- with software.

From what I saw, government contracting requires all requirements up front. It then floats a bid, and the cheapest bidder wins. Whether or not the contract has been met is determined by that list of requirements; even if you fail to deliver on a non-functional requirement that is obvious ("the system should be able to scale out and handle X simultaneous users"), you aren't penalized if it wasn't one of the requirements. In fact, delivering on obvious things that aren't part of the contract -hurts the contractor-; it requires development time and effort (and thus eats into profits), and the government is legally prevented from taking such things into account on future contracts (that is, they can't say "Well, company A is the cheapest, but the last contract they took was a broken piece of shit; company B is a little pricier, but they delivered quality, we'll go with company B". No, you go with the cheapest, period, because if they fail to deliver what you specify you can sue, and if they fail to deliver what you -wanted-, but failed to specify, too bad). It's possible to renegotiate the contract mid-stream, but it's expensive and time consuming.

So the contractor has every incentive to make sure that there is no time spent on quality, security, stability, scalability, etc, unless that's -explicitly- what was asked for. This article points out that having developers involved from the get go on the Healthare.gov rework led to it being successful, and that's very much true; you need technical people who care about more than just making bank to point out non-functional requirements that are missing. And, in general, trying to list all requirements up front is a fool's game, but such is the government's bidding process.
The "but he did it" defense doesn't work on HN, since people have to follow the rules whether someone else does or not.

But your flagged comment was obviously personally rude, and therefore much worse than what the other person posted. No matter how ridiculous someone's opinion is, if you can't comment civilly and substantively, please don't post here.

I agree with you about the article. In fact I was the moderator who boosted it (as described at https://news.ycombinator.com/item?id=11662380 and the links back from there.) But all that is secondary to the need to be civil, which the life of the community depends on.
I'm self employed. Some of my projects (mostly Ejecta[1] and jsmpeg[2]) spawned a lot of contract and consulting work lately. I'm also selling licenses for my games[3] so other gaming sites can host them and the AdSense banner on ZType[4] provided an impressively stable ~$500/mo for the past few years.

[1] https://github.com/phoboslab/Ejecta

[2] https://github.com/phoboslab/jsmpeg

[3] http://phoboslab.org/#games

[4] http://zty.pe/
Try Microsoft's OneNote. It's amazing good: it's maybe the first desktop product I've seen with fulltext search that actually works.
at least 15 years (last time I checked) of employment before you're up to 4 weeks per year.

Except you can't get there, because you can't work at 18F for more than four years. Or at least that was what I was told when I looked into it last year.

(I have nothing against 18F, by the way -- if it's something you're interested in you should definitely look into working there, and some awesome people I know are currently there)
Mobile web can be as good (or better) in just one case—reading the content.
Javadoc.io/