skysight-inc/HackerNews huggingface dataset:
When I feel like I'm doing good work, I'm a lot more productive, and I care more about doing things right vs just getting them done. Obviously constructive criticism needs to happen -- the author isn't disputing that. In fact, she says "it's been tough to get useful feedback" because people care more about cutting the other person down than actually evaluating the work.

It's very easy to couch constructive criticism in a few words of sincere praise/recognition of their work, and it generally results in them doing better work in the future. In fact, they'll be much more likely to listen to your criticism if you haven't immediately put them on the defensive. Once either side gets at all defensive, it's extremely difficult to have any kind meaningful conversation. If you always say "this is crap", then you're literally asking them to defend themselves.

If you haven't already, I would recommend reading "How to Win Friends and Influence People" by Dale Carnegie.
What effect would the reclass of ISP have on privacy (un)lawful data collection?
Sorry for the butchered title, I had to get it under 80 characters:
What effects would reclassification of ISPs to common carriers have on privacy, (un)lawful data collection?

I realize the importance of imposing net neutrality. I'm curious of what side effects reclassification of ISPs as Common Carriers would have regarding privacy and security.

I'm curious if there would be any changes in the ability for the government to (un)lawfully collect information, or make it difficult to secure our own privacy. Would it afford us any additional protections, or take some away? Would it make it easier for gov't agencies to route traffic through their facilities? Would/could it impose restrictions on the use or types of encryption? Would it make it easier for gov't to make changes to the classification with out over-site, or democratic process?
Manage your marking workload AND get students to respond to your feedback
Meshnet and Bitcoin Tech Meet the IoT. New #ePlug Whitepaper Seeks to Dump ISP's
Works on a Dell U2713HM. The noise (well... at least the portion of the noise I'm capable of hearing) occurs when the bars are at their fattest. It's barely audible.
Pursuing promising avenues is not wasted time, even if it ultimately comes to nothing.
> Let me give an example — say a new coder had somehow, impossibly, in their first month of coding, created an app that would save the planet, plunging us into a permanent state of world peace and 100% clean energy. What’s the first thing that you as a senior developer would say to that person before seeing or testing their project? Let me guess — you’re thinking, “Is it responsive?”

You built an email visualizer and are comparing it to some sort of utopian omnisavior.exe

This reads as an incredibly defensive diatribe about someone who didn't get a job because she interviewed poorly in her space.

You don't need validation at every turn, and providing that kind of false validation only cheapens actual accolades.
> Backups - Take regular backups of all user data. It's also VERY important that you actually try restoring the data as well, as it's quite possible that backups are not occurring properly.

The part about testing your backups is huge. I can't count how many projects I've been on that had problems where we needed to restore and we looked only to find any number of problems. Oh, backups actually stopped last month when we ran out of space, oops the backups only backed up these 3 db's and not the one you want, things like that. I'd also stress the importance of off-site backups. If you're using AWS for everything and your account is compromised can they delete your backups (assuming they have full, 100% unlimited, admin access to AWS)?

Which is also why if you're using stuff like AWS, Heroku, or any other third party provider (hosted Mongo, hosted ElasticSearch, Stripe, NewRelic, etc.) it's very important to ensure those passwords are secured and only the people absolutely necessary have access. Also, when offered, two-factor authentication should always be used.
The real key to success? Consistency
This seems a good reason to consider the Erlang model, of processes that fail early and exit on any error, with monitor or supervisor process to restart it.

Are there any Clojure libraries that do something like this? I think Akka supports this kind of design.
Markov Chains Explained
If you're down with eating disgusting things and only interested in nutritional value why bother with insects and not skip directly down to algae/bacteria - my guess is since these are simple organisms they can be genetically engineered for mass production with low maintenance and "tweaked" for desired nutritional values. Risks of disease sound much lower too.
Really cool. I would definitely be interested in trying this out depending on the price point.
I think you're being a bit cynical, and detracting from the point of the article. Yes in this particular case democracy didn't work so well. But the takeaway is that such a large group of people were not only OK with having a transgender as a mayor. That is good news anywhere.
In addition, those junior devs could also be hypercritical of their own work. However, they may not have the same experience or context of a senior developer and could simply be unaware of the scope of improvement. That's where mentoring and teaching should come in!
Wow, thanks for the feedback!

Here is my comments on your suggestions,

-- Flowcharts
I think I need a bit more data on how users use the app and in what direction I should take the app and features before implementing this, but it's very possible I will in the future.

-- Conditionals
Yes, I'm thinking of adding something like this, but on a higher priority I will add Triggers, so a checklist can be started automatically based on for example, a time interval or a callback over HTTP.
I will also add Outcomes, so you can set up a action that should happen when a checklist is completed, like trigger another checklist.

-- Finder control over headers and items
I will work on this, with the goal of making as simple as possible to get started with the first checklist, but over time be able to use more advanced features for creating items.

-- Extended item details
Markdown is in the backlog. Alos item audit trail, like, Frej changed the description from ... to ... (5 min ago), and so on, so you have a complete track record of changes.

-- Merge items from "started-checklists" to parent checklist.
This is something I'm going to implement pretty soon, so that, when a person perform a checklist and discovers a the need of a new item, or an obsolete existing item, they should not need to make the change first on the active checklist and the same changes on the parent checklist.

-- On the roadmap for the near future
Triggers (se abow), Outcomes, Audit trails for checklists & items, "News feed" and Notifications center is things I have on the roadmap.

Thanks again for your thoughts!

/Frej
Except the good ones know how to properly obfuscate the C&C servers. These morons ran everything through their public IRC server, hosted on the same network as the website advertising the service.
> When I feel like I'm doing good work, I'm a lot more productive, and I care more about doing things right vs just
getting them done.

What you're really saying is that you have the rewards system of a child. The application the author wrote is very simple and has no use - what kind of feedback is she looking for?
Maybe its is inclusive but it isn't Charlie like.
And its a lie, most people do not have the guts to be Charlie, I certainly don't.
We censor ourselves: they win.

Charlie Hebdo was not made to hurt people or a religion, it always pointed out the obvious stupidities, contradictions of the world, them being religious or not. It also had the message of never taking things too seriously.

I often disagreed with Charlie, often was disgusted by their drawings... but they made one think. The muslims I am with are far more offended and disgusted by the killings made in their name than by the crazy drawings. And publishing them still isn't as bad as bombing people, preventing people from getting jobs because of racism etc. A lot of the drawings were not of the prophet himself but of caricatured radical muslims.
FWIW, Google Maps biking time estimates are for a very leisurely ride. If you're not already comfortable on a bike, by the time you are, you should be able to easily shave half an hour off that time, unless you're going uphill the entire time.
Ask HN: Turning a full-time job offer into a contracting proposal
Last week I had a reunion with the owner of a business looking to hire someone to refactor their application. I'm thinking about building an API between the modules and the db. This way the code gets cleaner, better distributed and new modules can be created in a more transparent way.

The problem is that this guy offered me a job but what I'd want is make him a contracting proposal, I've some other things going and getting a full-time job is not something I would think of. I'm trying to come up with a way to turn this into a contracting proposal, but I find it hard to make it because I don't know how bad and big is the codebase thus how much work is it going to demand. Maybe someone here with more experience can give me a hand.
Show HN: Woocommerce Android Converts Wordpress to Android App
"I expect to be criticized on nearly every project, because that makes me a better coder."

A great deal of the criticism is not intended to make you a better coder, and it probably won't do so. It's intended to make the critic appear superior or at lest feel superior.

Yeah, I've done that. It's a bad habit to get into, and a hard one to get out of.

"There is always something that can be improved, and beating around the bush with flowery language doesn't really help to fix it."

"Great. Now tell me something I don't know."
> This seems like a great way to break CDN geo-ip, get served ads, and get non-standard "typo domain" messages.

A lot of ISPs do (or try to, before backpedaling quickly) the same things. I've settled for using Google's DNS servers.
Because of this: "Parents of Head Start participants in the 4-year-old cohort reported less aggressive behavior in their children at the end of 3rd grade than did the parents of the other children. For the 3-year-old group, Head Start parents saw better social skills in their children."

Learning is great. Being sufficiently socialized is more important. I'd like to see data from when these kids are in their teens or twenties.
I'm confused. There have been articles posted here some time ago that said black holes aren't real and they don't exist, and there were comments here that confirmed it, as far as I reacall written by people knowledgeable in physics.

So which way is it? Do black holes exist or not?
> If name constraints were implemented more widely, that'd be great. But someone has to write the code, debug it, ship it

Without name constraints I assert the system is inherently broken. You cannot limit trust other than yes/no.

> ultimately wildcard certs work well enough.

Well enough is arguable. The problem is that your attack surface grows with each machine rather than having a private key per machine.
But how much are you "married" to a jew, really?
Supermassive black-hole binary? Sounds like some projects I've coded on...

/rimshot
Agile is a cancer we have to eliminate from the industry
and one server to rule them all...
In the 20th century, the frequency of the definite article “the” decreased
Diagnose Service Performance Bottlenecks with Google Cloud Trace Beta
My LG W2242P does it for a range where the bars are at there thinnest. When they start getting close to thinnest, it gets higher pitched, and then reverses when they start to thicken again.
I mostly run Windows on my MBA, FWIW. Dealing with yet another *nix variant beyond Linux and Cygwin is not high on my priority list.
The article author's name sound futuristic enough to be the protagonist.
Computers used to “solve” two-person, limit Texas hold’em
I believe what pcmonk is trying to say is that you are stupid and arrogant, and that is a poor combination.
Here's hoping a physicist is reading this, because I'm curious: what happens at a point where two event horizons overlap? Can such a thing happen? And if so, do you then get two choices of future time-like dimensions, one for each black hole?
Valid arguments, and after buying the first model I didn't follow the Amiga story after it was clear it was going to fail.

Doom requiring GPUs would seem to be adding to the argument that for a very long time period as these things go, their specialization paid off given the volume in which they sell.
If/when GPUs get almost entirely subsumed into CPUs (I don't have any 3D requirements, and I'm typing this on my first, 1 year old computer with integrated into the CPU graphics), I don't think it'll invalidate their "success by specialization".

However, I think I'll still go with my thesis on the Amiga: the failure to gain sufficient market share and therefore volume, plus poor to bad management, doomed it just like the Lisp Machines. And perhaps the NRE costs on the chipset, perhaps the experience of doing it and facing having to do it again, deterred the managers from going for 3D.

As for modern PCs ... I'm not sure I really buy it. Look at all the discrete TTL in the original PC motherboard: http://mit-a.com/disp/mb1.shtml Look at all the TTL in standard cards for it: http://www.minuszerodegrees.net/5150_5160/cards/5150_5160_ca... And a 2nd generation 3com Ethernet card: http://sishardware.com/unt/20622-3com_etherlink_ii_tp_6330__... All computers, especially all designed for volume production, looked like that, and were filled with cards like that.

I submit that the steady accumulation of all that logic into fewer and fewer ASICs, and much eventually into the CPU (nowadays memory controller and PCIe lanes) and a single chip "chipset", is just natural cost reduction aligned with (massive) volume sales. How to square that with the Amiga's chipset, I'd need to think about. Perhaps later.
Life without Police
Java code hot-swapping and REPL for Android UI dev
An acquaintance taught at a NY state CC for a while after retiring from a state school in the Midwest. He said that he found a bimodal distribution in his classes: the highly motivated and well prepared on the one end, the unprepared or unmotivated on the other, and not that many between.
"A candidate decides to try out this election thing without any agenda and plans, and they win without any reason. They don't even know why they won and what they can really do for the community. Giving government jobs to beggars isn't a plan."

Actually, that sounds like normal democracy in action to me. Unprepared candidates being voted in happens all the time in all democracies. And this candidate seems reasonable and may end up doing a good job.

If you look to other democracies for comparison, Talkeetna in Alaska has had a cat named Stubbs as the elected mayor for years. Mel Carnahan got voted into the US senate in an election 3 weeks after his death. And Tiririca the Clown got voted in to Brazil's congress and was completely inexperienced and was accused of being illiterate. He apparently worked really hard and did a very good job of it.

Remember, democracy is not a plan and nobody is ever 'ready' for it. It just tends to be usually less objectionable than the alternatives, especially the planned alternatives.

edit - Also, Ms. Kinnar did not win for no reason.

"I have no experience, I’ve never made a public speech, but while campaigning, I went to every household."

And she seems to have a clear idea of what she wants do to for the community.

"I feel the most-important responsibility I have is towards my people. My community. I have to stop them from begging for money on the trains. Instead, I want to give them jobs in municipal corporation. Apart from that, the deplorable condition of roads and drains in the city worries me. Raigarh doesn’t have a water shortage but taps often run dry. I want to make sure people in Raigarh get adequate water supply."
Hashing client-side is not a good idea in practice — a leak of your password database leaks direct credentials for logging in. If you're going to go this route, something like the zero-knowledge SRP protocol is necessary.
Now all we need is for a millisecond pulsar to float through the middle...
It strikes me that most of these points can be automated (well depending on the language perhaps). I prefer automating and blocking checkin's based on criteria like these. Leave code reviews for design discussion.
Have you talked with the moderators about your concerns , and if so what did they say ?
When I first came to Silicon Valley, I had a couple of senior engineers as my mentors. The most important lesson I learned from them is that they were extremely supportive. I had a couple of ideas for new features, and instead of shooting them down and telling me why it wouldn't work, their responses were always "Hmmm, sounds interesting. Why don't you spend some time on it and let's see how it works out." When I did something dumb, they would point out the mistakes after implementation, but never in a "I'm smarter than you" way.

Of course, since then I've had many jobs where the other engineers were always hypercritical as this article points out. In this industry there certainly is an undercurrent of everyone trying to prove how smart they are by showing why everyone else is dumber than them.

However, I'll never forget my first mentors and I try to respond exactly as they did, which is be supportive to any of the junior engineers that I mentor. I always try to not say "no", even if I feel they are wrong, and I always engage in a conversation. Even if I disagree with what they want to do, I'll try give them the opportunity to prove me wrong (within reason) as opposed to simply shutting them down with a curt "you're wrong, no."
I suspect even "I can think of no use case for this app" would be more appreciated than "is it fully buzzword-compliant?"

Additionally, phrases like "What you're really saying is that you have the rewards system of a child" are exactly what I'm talking about. That statement is intentionally worded as an attack, so I have to make a conscious effort to not get defensive. If you want an actual discussion about how rewards systems may change as people grow up, we can talk about that. That was an extremely ineffective way of starting the conversation, though.
Just be yourself. Interviews are not equal to acting like an extrovert, and any attempt to "fake" will likely backfire. But indeed I have to admit I was quite shocked at how incredibly unsociable and inexpressive those programmers are at my first work. Probably it's just because I'm not working at a world-class place yet and the sample size is way too small, I can only assume.
> Let me give an example — say a new coder had somehow, impossibly, in their first month of coding, created an app that would save the planet, plunging us into a permanent state of world peace and 100% clean energy. What’s the first thing that you as a senior developer would say to that person before seeing or testing their project? Let me guess — you’re thinking, “Is it responsive?”

Not like I think there is no truth to TFA, but it's pretty much "You think newbs are dumb, but it is actually you who are dumb." Well, OK, I already spend a lot of time considering that. And, for what it's worth I think the senior ones are mostly not so hot either.
The Roots of Obama’s Ambitious College Plan
Nice comic by FIRST participant to inspire girls into robotics/STEM
GothamGo: gophers in the big apple [videos]
The exact phrase you're looking for is "I don't know, but ..."

Saying "I don't know" is often a defense mechanism. It saves you from having to know. If you don't know, and you wash your hands of it, whatever happens isn't really your fault is it? And you're not going to know either.

But if you say "I don't know, but" and try to figure it out, or find out more, etc. ... that does take guts. That is actually admitting you're fallible AND it gives you a chance to improve and get to know.

Those are the people you want to hire.

You need people who recognise their ignorance and do somethign about it. Not people who use their ignorance as an excuse.
Largest MMA forum on the web needs a front-end designer
A huge community over at the MMA Underground has been stressing out the server infrastructure for quite some time.

They are in the process of building a new a site and are seeking a front end designer.

I figured I'd drop a link here in case anyone is interested.

http://www.mixedmartialarts.com/thread/2405012/UG-needs-top-men-for-front-end-work/?&page=1

original post:

We are looking for a front end designer to take compositions and cut them into responsive HTML. Skills we are looking for:
1. Ability to cut up comps into html.
2. Ability to code on a modern css framework like Foundation or Bootstrap.
3. Design ability to extrapolate from the comps to produce other non comp'd pages in the same motif.
4. Comfortable using GIT.
5. Desire to make the new UG badass.

No resumes necessary. Please just send a couple sentences with your experience for items 1-4 and concrete examples of your work product to Kirik@MMA.tv
What’s the first thing that you as a senior developer would say to that person before seeing or testing their project? Let me guess — you’re thinking, “Is it responsive?”

Does it reflect poorly on me if this sounds like a rather convoluted hypothetical? Then again, I'm not involved in web development, for what it's worth. Maybe there are people who actually think like this.
Harborly Launches New Website in Canada
Works fine on my end: USA/Cali/CharterCom cable.
NAR Discusses the Professional Liability Insurance Program Mailing
Am I weird if I say "thank you" for the checklist? I think it's a good starting point and has some helpful reminders.

As always, there are some really great and insightful comments and suggestions here, but I'm a bit surprised about the overwhelming negativity around code reviews and this post.

FogCreek's post is just a starting point, and they said so right in the post. It wasn't intended to be taken as the end-all-be-all of code review checklists, but that seems to be getting ignored, sometimes in favor of unconstructive criticism.

It's a decent starting point, and the main takeaway is that there are lots of angles to think about when reviewing commits, every single time, not just whether the code works. It's easy to forget all the angles because code reviews are hard to always do well, so having a checklist, even with redundant items or minutiae really isn't the awful idea it's being made out to be.

The included video, which based on comments I'd be forced to guess almost nobody watched, also clarifies their process and intent, and addresses some of the comments here, for example pair programming. Joel mentions pair programming being the most extreme form of code reviews. In my own experience, he's spot on when he says pair programming is really useful in certain situations, and very hard to use frequently.

One angle that hasn't been discussed that that a long checklist is actually a good thing when it comes to justifying time spent code reviewing to managers (as well as fellow coders). In my own experience, I've witnessed the attitude that code review time is unproductive, and the thinking that code reviews shouldn't take long. Having a specific process that demands a minimum amount of attention is a good thing on its own, completely outside of the benefits to the code and code quality.

Edit: spelling
Probably? Do you think that's strange? Pretty standard if you ask me.
Personally I do the "remap caps lock to control" trick. That being said, I would hope the power button would be flush with the surface of the laptop, so you'd be more likely to hit the protruding escape key.
I wish you the best too.