skysight-inc/HackerNews huggingface dataset:
In most use cases I can think of the generated data is used only in a closed (testing) environment and won't be visible to web crawlers and spambots. Many developers like me use these libraries for prototyping different UI views for their apps.

The bigger problem, in my experience, is when you accidentally spam people yourself, while testing some function that somehow generates an outgoing email. I think almost everybody that's ever worked on code that sends emails has - at one time or another - ran a job that somehow wound up sending 6,712,374 "test" messages to every user in the production database. :-) Dummy addresses are better, but it's better still if they use @example.com so you know there's no way they'll actually get delivered to anybody.
Like I said, this is not much doable in Brazil.

The average wage here is 500 USD/mo

The best wage I found for a programmer is around 2000 USD/mo (unless you work with SAP, then you can get 7k/mo but I don't work with SAP)

There are no way that I would cover my debts with a normal job unless I got really lucky and someone decided to make me CTO of a medium company or something like that
We'll look into this, but how are you going to be able to send a mail without signing up on that app?
I'm surprised this isn't flooded with comments - this is great. Have been playing with the demo across a few different devices and it is really sweet.

Great work - definitely will be following your progress
It seems so strange to me. We share the articles we read, we comment all over the internet (sometimes using our real names), we share and publicize our code on Github, send tweets into the eternal ether, post pictures of us and our families -- but ask someone I worked with what they think of me and OMG THAT'S SO TERRIBLE, IMMORAL, AND POSSIBLY ILLEGAL.

The dichotomy blows my mind. You should be proud of your career and the impact you've made.
Due to the high number of signups, we will not be able to accept new users. To be notified when we will allow new users to join the system, follow us @bitcointipper .
Facebook events have always been broken - in many ways, as you correctly states. This is a nifty little tool to fix those mistakes and must've been a fun evening hack-it-up project :) GJ
Apple pessimism is at an all-time high (podcast)
Great work David, glad to see an update after almost 5 years!

I looked into Clue for compiling C to Common Lisp before writing https://github.com/vsedach/Vacietis because I wanted something that would interop better with CL types and be able to run self-contained.
I don't believe anyone said it was good, but it is what people use instead. Worse is better.
Google killed sparrow because Gmail is better than sparrow Google din't kill YouTube because YouTube is better than Google videos. Facebook dint kill instagram.

So,I think Dropbox has just acquire mailbox not for killing it but to enter a different domain.
And their comments.
I would find it difficult to believe that Google+ wouldn't have already been looking into getting news feed subscriptions into their product. An RSS-style solution with discoverability would leap-frog Facebook's News stuff and could even put them into quasi-competition with Twitter.

It seems an inevitable sort of feature.

So the idea that they were surprised by this and are going to start from zero to build a new bit of G+ seems... a stretch.
Plenty of apps force updates through the play store by disabling functionality remotely in the currently installed application. I've had games and other applications that have no legitimate need for remote server interactions become disabled because a newer version is available, where any attempt to launch the application redirects to the play store page instead. This isn't good, and most of those applications don't last on my devices, but that isn't a completely unheard of practice.
Well, at least they had some women on stage, unlike the PS4 launch event. http://www.theverge.com/2013/2/21/4013500/no-women-onstage-a...
Well said. Pretty easy way for all files you receive to immediately be in your Dropbox, and for Dropbox to either

a. launch an email service that runs off the space in your dropbox, or
b. automatically create dropbox folders shared between all recipients of an attachment and automatically set permissions.
This sounds like useful information to have on the KickStarter page. You sort of obliquely reference this stuff in the first few paragraphs, but it would be great if you fenced off a whole section referring to the kinds of tools that could use this (with links to Ace/Cloud9) and talk about the reasons why they can't do this right now and how cool it will be after you implement this and you can use them offline.

If you want to jump on a particular recent buzzword hype bandwagon, you can talk about "Always-online requirements" and how you can fix that.
Dude, do I need to put a sarcasm tag?
I still haven't figured out how to find references who might not accidentally leak the fact that I'm looking elsewhere to the whole office.

I tend to end up putting people from jobs previous to the current one to avoid this, which probably makes the whole process somewhat pointless.

It's all part of the picture when it comes to explaining why the hiring and job search process itself is more of a problem than the availability of hires.
>>Makes me wonder if it's not arrogance...

Trying to parse this sentence, you are implying that you thought their actions could be explained by arrogance and now you think it is something else. Correct?
Most corporations don't behave particularly responsibly in terms of your data security, and the financial industry is one of the worst when it isn't an issue that they are statutorily liable for. So you end up with odd extremes where credit card fraud is treated with extreme care (statutorily liable > $50) and business banking is usually secured quite poorly (no liability, typically). It's up to you to provide or ask for any extra security measures you find appropriate, like asking to call them back.

Anyone using common security questions is already balancing a risky behavior with ease of use.

They might also know that risk is low - if they don't allow any difficult to reverse transactions like outbound fedwire there may not be a lot they can't easily undo.
Hi there, I've also run into this issue. I've opened an issue on your github: https://github.com/bombela/backward-cpp/issues/2

Thanks again for the really useful open source contribution! I will be integrating this with my C++ projects.
What you described is similar to my process (though on Windows I always install MSE now too), but it's important to acknowledge the limitations of such an approach. For example:

- do not open any email attachments from unknown senders (seriously, it's 2013, who does that anymore?)
- do not open any URLs from unknown senders (same as above)

These only work as longs as no one you know gets hacked. You're vulnerable as much as the weakest person in your trusted network, and I guarantee others in your network aren't as careful as you. So it's not just avoiding URLs and attachments from unknown senders, it's avoiding URLs and attachments even from people you know and trust that you weren't expecting them to send you. I've come really close before to clicking links from friends that said something along the lines of "Holy crap, this is you", which is actually sometimes expected because I have friends who see articles or pictures written about or by me.
"an engineer", Chief Architect, same difference, right?
It makes sense if they want to compete with Gmail by integrating dropbox and mailbox; providing an alternative to Google Drive.
The Future of the Feed, the Read, and the Reader
Circles don't have up and down. :) Going clockwise is always a fifth, counterclockwise is always a fourth.
In the original EEE, the only extinguished products would be the competitors', not Microsoft's. The point was to capture market share, and that doesn't quite work if you eliminate yourself as well.

And Google never really "extended" either. They didn't add new fields to RSS or made it incompatible in any way. The proof is that I was able to move to Tiny in 5 minutes using Google's own export tool.
Except caller id / phone number is easily spoofed
if not there already, we should put up quick poll of top x Google Reader alternatives that everyone can vote on (put it on Google Docs to add a bit of irony) w/ a light column for use case (which OS, browsers, etc).

every blog publisher then points to the poll as addendum to each post going fwds, informing readers to choose one in order to keep reading via rss.

can include some directions on exporting GR feeds for any of the GR subs that don't already help the reader do so.

granted requires some work, and we still will lose some users, but overall isn't something like this (or a better idea?) required to ensure blogs/rss ecosystem don't lose readers that don't know there are good alternatives and won't necessarily seek alternatives on their own?
Communal living in Silicon Valley [video]
Software Eats Hardware
While I get the point you're trying to make, and even somewhat agree with it, there are two definitions of "death" in play. The problem isn't hyperbole; it's simply one of equivocating between them.

There's clinical death, which the author of TFA very likely did experience. If VF continues for anything longer than a few seconds, asystole frequently occurs. Among other things, asystole is definitive of "clinical death."

On the other hand, there's death death. This is the one where we bury you and mourn you and so-on.

Yes, they're very much not the same thing. Yes, the author is probably equivocating between them, at least a little. But no, his describing what he experienced as "death" is not hyperbolic — at least not according to the clinical definition.
>The craziest set of downvotes I've ever seen on a comment of mine are here

Haha, it didn't take very long to make that into your profile. I'm sorry you are getting downvoted and I upvoted you to make up for it, but I would strongly advise you to not cold call people from a company about the candidate. An employee at my last company almost got fired when they found out he was looking elsewhere. It was terrible of the company, but they needed someone stable in his position for a long project. He was on a visa, and he told me he could have been deported before he had a chance to accept another offer if he had been fired.
I was under the impression that in most states it's required in a gym...
When I was an MP (military police), they taught us a bit about escalation, wherein you only use what is necessary for the task at hand and reevaluate as the situation changes.

Cops certainly do not need to be using 'weapons that belong on the battlefield' as their go-to weapon for any raid unless it is suspected that there may be body armored opposition (an absurdly rare occurrence - worth treating as an outlier). It would not be unreasonable to have one or two rifles on standby, in case a situation escalates beyond what was expected.

I do not like this trend of increasing para militarization of the US police forces. You are supposed to trust a police officer. It is hard to trust someone wearing BDUs and carrying assault weapons - you are more likely to respond fearfully, which can often make things worse.
This is one of the most tone deaf requests for feedback I've ever seen. Astonishing.
What I find most interesting from this post is his belated admission of the brokenness of G+ when he writes "(NB: If you're seeing this via a reshare, please remember to comment on the original post if you want me to see what you're saying!)"...
A corollary is that people approaching references as an opportunity to get answers to questions they missed in the interview will flag false alarms because busy involuntary referees decide they don't want to list specific examples of where Candidate X was unusually productive, or have no idea whether X was in the top 3 or top hundred team members they've ever worked with for accurate record-keeping.
Django project settings structure
The RedNose of Drupal
Lemme explain why it matters:

Suppose we were coworkers, and you found out that I was entertaining a job offer with another company. How would you react? Would you be asking me to do more work (knowing that I might not be there soon)? No, most likely you would try to wind down any work we were mutually involved with, in anticipation of my announcement.

Take it to the next level. If my boss found out I was looking for a new job, I'd be on very thin ice. The boss wouldn't entrust me with any long-term or cool project, nor would he give me a promotion unless there was a strong sense that he could retain me by giving a promotion. And even if I did stay on, it would still nag at the boss and would forever tarnish the working relationship.

The problem isn't the actual opinion. It's really the ramifications of others knowing you are looking for a job. And that's something I do care about, regardless of how proud I am of my career. (and for the record, I am proud of my accomplishments :)
At the very least, they should call you and direct you to vanguard.com where there would be a link at the bottom that says "call us back" at which point if you call back you'd be promptly put back in touch with your rep. another factor that helps broker trust in a conversation.

I follow this protocol with American Express and it's always effective. I'm also a high dollar monthly spend (corporate account) and so I get answered within a couple rings and they can pull up my account and notes immediately.

-David
Yeah, go write a wall of text, just in order to receive "you are not allowed to comment on this post" after you hit the "comment" button.
Bravo G+, you bring us real value.
I'm not sure if it's arrogance or ignorance. Consider that Google has access to an extreme amount of user data and usage data. Did they analyzed that, then draw conclusions? Did they "assume" they knew best, since they are some of the smartest folks around? Actually asking users for opinions after the deciding to shut Reader down and getting a backlash seems to be a misstep on their part...
What's wrong with tabs?

I'm personally not a big fan of designers trying to out-clever user familiarity by getting rid of tabs (or other standard interaction models to which users are accustomed).

Are tabs sexy? Maybe not, or at least designers don't think so. However, tabs are very well placed in terms of usability, very familiar to users, instantly understandable, and a lot less complicated than the back-bending design gymnastics some designers are doing just to be different from Apple.
You are right, I assumed it was installed by default because it syncs wherever I log in. Sorry about the confusion.
I think you bring up a couple of great points. It can be hard to escape the sort of lock-in effect if you've got a larger app on Heroku. For instance, I'm guessing it would be difficult for RapGenius to move somewhere else at this point. I think you also touch on the key argument for Heroku which, as far as I can tell, is "If the amount you pay is less than few hours of your time, why not?"

Thanks for the amendment to the comparison. In a sense, an ORM can still have ongoing "costs" as it tends to run a little slower and require more processing, so it might require additional hardware eventually as the scale goes up. Maybe I'm belaboring the analogy too much at that point.
I lost my dad last week to this exact same event. My parents live in the country, and my elderly mother didn't have the training (or lack of panic) to attempt CPR. Although members of the local volunteer fire department were on site within 7 minutes with an AED, I'm actually quite comforted in the knowledge that there never really was any hope for him. One of the few nice things about vfib is that it's quick and painless, and the grim survival statistics mean that there wasn't really anything that could have been done differently in my dad's case.
watch clip #1
A couple of notes on the article:

1. I'm really surprised legit vendors like LastPass don't become verified authors on the Chrome webstore; it's trivial to setup. We were able to do this for Meldium easily.

2. Joe's comments that it's hard to write an extension that steals data does not seem very true. Someone who is dedicated can do a lot with Javascript.

3. The author doesn't mention the model Mozilla follows with its addons: actual humans code review extensions to determine trustworthiness. They reject extensions containing obfuscated code for example.
QR codes turn dynamic 
When I write about the black and white, crossword puzzle-like QR code, I feel like I’m talking about the stone age of human development. The few years of existence for the QR code in marketing efforts, seem like they were first experienced by our grandparents when you look at how the code itself has evolved to walk upright. Whatever you read in this article, chances are, as with buying a new mobile phone or computer, it will all be obsolete almost immediately… or possibly not with this latest step.
How can anyone expect serious and fair treatment when half of their post is threatening what he'll do with posts that don't conform to his specification? Trolling everyone in advance is not a good strategy for gathering feedback from community. If he can't face the regrets of the community, he should just keep his mouth shut, have a bit more respect towards others.
Honestly, a company that doesn't innovate, doesn't treat its talent right, and is run by suits who mass produce junk. Don't expect them to have any taste what so ever.
tl;dr

> Shut up and make me a phone.

Exactly.
Easier than having someone else maintain it?

The bar is 'If I never ssh into this box and leave this app alone for 3 years, how likely is that box to get rooted?'
This is what is said LITERALLY EVERY SINGLE TIME a company is acquired -- right along with "nothing is changing" and we'll "continue to operate with the vision that made us attractive to $acquirer in the first place"

Without a more clear rationale for why things won't change, it's pretty reasonable to assume that the product is at risk no matter what you say. The fact is, almost regardless of your intentions, your organization is going to put its thumbprint on the product.

What that means is unclear to external customers, and is also often unclear internally. If you do know what your plans are for it internally, you're still probably not going to say (though I'd love to be wrong).
MakeGamesWithUs (YC W12) is hiring an iOS Game Dev
About us:

We teach people (primarily high school and college kids) how to build iPhone games. Our site (http://www.makegameswith.us) contains project based tutorials which culminate in building a clone of Angry Birds. After completing the tutorials, developers get started making their own original game. We also provide a toolkit to speed up development of games, along with forums to enable developers to show off their progress and get help. Once their game is nearly ready, we skin the game with professional art, and finally publish and promote the games for a share of the revenue. You can check out our first 10 games here (http://www.mgw.us).

We're currently a team of 4 who live and work out of a 4500 sqft house in Palo Alto, it would be awesome if you're willing to move in with us, although living elsewhere in the Bay Area works too. We're a young team with a relaxed work environment, and we love our work so we tend to do it most of the time. When we're not working we're throwing a big party or just kicking back and playing fifa or super smash brothers. We also take the occasional company trip for a change of scenery, our last one was to France, and our next will be to New Orleans.

We are striving to build a big gaming business while inspiring people to explore computer science and learn to build complete products. We're well funded by Y Combinator and undisclosed top tier VCs/angels. It's a great opportunity to join an early stage startup on the ground floor and work with a young and dedicated team.

About the Job:

We're looking for someone with iOS experience who really understands mobile games (cocos2d experience is a bonus). You'll need to think strategically about what the games in our catalog need: a better tutorial, better monetization, retention strategies, etc... You'll then help our developers improve these things, at first by doing them yourself, and eventually by building tools and tutorials to make it easier for future developers to build their games the right way. You'll be writing plenty of original code, but you'll also be sifting through a lot of other people's code to fix things up and add new features where it matters. You'll have your hands in dozens of iOS games at once! This should be exciting to you. We like fast learners and autodidacts (people who constantly learn on their own). You should be passionate about what you do and hopefully about what we do as well!

Interested?
Contact jobs@makegameswith.us
Show HN: inspired by pg to hack together a FinTech startup. What do you think?
The am>ventures site is here: http://amventures.co/

We're really happy with the work they've done for us. For early stage startups, they're a great option.
There are a bunch of tutorials as a service companies out there. Awesome to see one as F/OSS though! Nicely done!
Why WE don't use Heroku:

it's f'n expensive!
Well, that's the first time I've seen Puppet and Chef criticized for being poorly tested...

You say "lets you do way too many stupid things" and I hear "you can't necessarily do everything in Salt if they didn't anticipate it"...
I once received a reference-verification call for a previous coworker and friend which started to go in the direction of asking for more than confirmation of employment and general pleasantness to work with, and I wrapped it up as soon as possible with the old "hard stop." It's not my job to pause my actual work to sell you on a candidate. A job reference is not analogous to a letter of recommendation. If my previous coworker was a colossal jerk, I might say, "Hmm, I'm not really sure about that, it was a while ago," and that's it.
The video:
http://www.youtube.com/watch?v=p6GRFKWGn1k
Swapbox (YC W13) Launches And Aims To Pick Up Where Bufferbox Left Off
> If VF continues for anything longer than a few seconds, asystole frequently occurs. Among other things, asystole is definitive of "clinical death."

This isn't true. VFib can persist for a long time (at least 20 minutes, maybe more). Furthermore, defibrillators aren't applied to an asystole heart. Nor do practitioners typically continue working after clinical death has been declared.
ssh http://(HACKTHELINE (car pg rules (cons (hack `the line`))) --+ scala.node(Js) + import ruby.gems %% equals = HACK THE LINE
My 11yo has a ChromeBook and uses Cloud9 IDE to do all his coding at home. When he's on the go with mom (home-schooling at the park) he can't code; sadness...

If he had a git clone in a sandbox he could keep coding; happiness...

.

backed!
Ouch. I didn't know their passwords were case insensitive.

I thought they didn't accept all special characters either, but I just successfully changed my password with special characters that I don't remember them accepting last time I changed my password. I was successfully able to log in using a version of my new password with the case changed for some letters.
Same here, what the guy doesn't understand is that tab based scale easily when doing universal apps.

The tabs move over to a side panel on the iPad. Works out of the box and offers the ability to write a single code base for both platforms.

Most designers ("UX monkeys") are too dumb to realise this as they are just Photoshop slingers and can't code for shit nor know the SDK.

It has an amazing cost benefit when you're a small startup and want to push to both platforms without compromising design.

Seriously, Tab based works wonders when doing universal - mostly because it's out of the box. Another way is the side panel. Now that comes out of the box for iPad, but not iPhone.

Using a tab gives you the ability to have a tab on the iPhone and side panel on the iPad with as little change as possible.