skysight-inc/HackerNews huggingface dataset:
I'm not affiliated with either party, but I wanted to chime in and say that I HIGHLY recommend two scoops for anybody looking to learn Django, expecially if you found this screencast helpful and are looking for something more to supplement it. There's so much to learn in that book that I can pretty much consider it required reading for serious prospective Django developers. Thanks Pydanny/Audrey! You guys did an amazing job!
You're right, my comment was not thoroughly considered. Maybe I should start doing some of this plagiarism detection. For some reason the idea depresses me, but you make a good case for it.
That "77 years ago" guy says he's 25 years old in another post.
They have not specified any reason for closing Flyte though.

[Edit] Found post on NextBigWhat where they have explained it.

“We have realized that the music downloads business in India will not reach scale unless several problem areas such as music piracy and easy micro-payments etc are solved in great depth. Which is why, we feel that at present, it makes sense to take a step back from Flyte MP3s and revisit the digital music market opportunity at a later stage.”
Enabling skim-reading seems a decent goal.

As in, write comments such that someone can quickly get a high-to-mid-level understanding of what's happening in a given unit of code[0], with the unabridged version being the code itself.

0: The smallest unit worth commenting being a logical group of lines within a function, usually padded with newlines above and below.
Google didn't get to where it is today by amassing a bunch of random overvalued startups.
Die Grenzen meiner Sprache bedeuten die Grenzen meiner Welt.
That really should not be an issue at all on that device... (although once you are booted, you'll need to do some work in dmraid on account of the HDD situation)
Also, about this:

Have people considered that "credentials and connections" are actually a valuable signaling mechanism? Connections (in the broadest sense of the word) indicate that a candidate is able to form strong personal relationships.

They don't care if you have strong personal relationships. They don't care how many close friends you have, if all of them are plebs. They only care if you have ties to the right kind of people.

Credentials and connections are a valuable signaling mechanism because having them most certainly does create value--knowing powerful and wealthy people is how you close the biggest of deals.
The only way we're going to truly minimize human impact is by forcing developing nations like China and India to dramatically change the way they are growing their economies, which frankly, doesn't seem very fair. They have as much right as the rest of the 1st world to develop their country and nobody is going to be able to tell them otherwise. The only real way out of this mess is a mass exodus away from fossil fuels over to nuclear power or the discovery of some sort of new abundant power source like fusion (solar and wind aren't going to cut it).
The poster wasn't changing the subject from the rape of females to the rape of males. The title of the article is "Facebook agrees to ban sexual assault 'humor'" and not "Facebook agrees to ban sexual assault against women 'humor'" yet the article only seemed to address sexual assault against women humor. Asking if the policy also extends to humor regarding sexual assaults against males is a fair question under the circumstances and in no way diminishes the gravity of both.

According to surveys 7 - 12% percent of males report having been the victim of a sexual assault with the vast majority of victims having been assaulted while minors. The rate of sexual assaults against males is increasing. It is a serious and increasing problem.
It's the new Hello World app that replaces the blog engine :-).
I live in the US and my government certainly doesn't give me files in ODF. They're either PDF or doc/docx.
How the Guardian built multimedia interactive Firestorm
If you're early (5-7 July) you could always try to visit the CCC conference "SIGINT13" (http://sigint.ccc.de).
Don't forget blog engines.
Finally I managed to reach zapret-info.gov.ru and found that IP 69.174.244.50 has been banned on 2013/04/18.
Penicillin isn't the only medical advancement from the past 100 years that is contributing to our high life expectancy rates.
+1. Communication and professionalism are your best bet, here. It's amazing how often engineers think the managers know all these things, as if they've mentioned it a million times, but no one is listening.

Sometimes the problem is that the issues are communicated, but not the severity. So, you might raise that the database is too complex with 100+ tables, but if the manager does not have an intuitive sense for the consequences of that problem, it might not register as a project-destroying issue. That becomes the disconnect later, and when things go pear-shaped, these disconnects become issues of contention.

The worst thing you can do is to raise these issues quietly and just keep trucking, as if you've done your job, and that's that. [wiping hands gesture] If management doesn't realize that the project is headed for disaster, that's on you (and the others on the team).

But, if you're able to convey the severity of these issues clearly and professionally, the conversation might turn to what can get done in the near term that would be valuable. Or, to the point of other commenters, there might be other factors at play, and the manager might want you to keep trucking anyway. In this case, provided you have been clear about the risks and threats, you really have done your job.

As a parting thought, you could also raise an issue around "what type of company" you want to work for. Perhaps if they need to rock out a rough proof of concept with no automated testing (or any testing!), that's one thing, but I wouldn't want to work at a company that doesn't take testing seriously. So perhaps if this is a manic sprint to prove something, we can all get on board with cowboy coding, but once the dust settles, it will take x amount of time to shore up the work with xyz types of tests. If they aren't on board with taking their medicine and putting the right tests in place, then that might be reason to depart even if the proof of concept succeeds.
Honest, "be slightly evil" answer: say absolutely nothing. Just work. Get done what is asked of you. When you have free time (which you often will, due to the chaos as things start to shake) use it to build skills for your next gig.

People will probably lose jobs. Sometimes that will happen based on seniority and sometimes it's just random. Sometimes, that will happens to the PITAs who spoke up and happened to be right. You don't want to be a PITA. PITAs become blame dumpsters even when they were right, because enough people hate them and no one will defend them. You're not the only one who knows that the project is fucked. Just keep your mouth shut about the fact.

There's something I call the Welch Effect, which is that the people most likely to be laid off are junior/least-established members of macroscopically underperforming teams (who had nothing to do with its underperformance, because they had no power). Managers are sometimes sympathetic to the Welch Effect and will set a "no infanticide" rule, but not if you're a PITA.

Keep your head down, do good work when work is asked of you, and start planning for your next move. Start networking and searching and building skills now, not when you need to.

If you lose your job, don't take it personally. It's not your fault, and if you tell the story in the right way, no one will hold it against you. These things happen to good developers, especially early in the careers, all the time. Most projects fail. It's not like school where something has to be going wrong to fail a course, because only 5-10% get F's. It's probably 50-75% of software projects that fail.
If you are the only one that is seeing the upcoming failure, this can mean 2 things:

1) You are wrong and paranoid. The project will be delivered with some hurdles but will not be catastrophic at all. Try to make sure that your concerns are clearly defined. Contrary to most people here advise: don't try to be the nice guy by being subtle. Be polite but be also confronting.

2) You are right and you will not be able to change the situation. In this case, I would choose the easy way and leave for another job. Watch out for the stockholm syndrome: there are other companies where you can enjoy your work. Don't feel to much sympathy for the current situation or be afraid of uncertainties that come with leaving.
New York has a military? Sweet!
We had a fix. Unions. They were dismantled by Nixon, Reagan, et. al. from 1968 to the present because the professional classes believed that they were insulated from the problems of the working class.

They were wrong, and we are paying the price, the profits going directly to the owners of capital.
Even if it's "just politics"—politics is what prevents companies from thriving. It's a sign of poor management, poor culture, and poor understanding of human psychology.

In two words: screw that.
Disappointing that each provider uses a different name. Imagine if they each had their own name for the password field. They should all just call it two-factor authentication.
Sometimes it's hard communicating the situation to a manager as opening that pandoras box can end up meaning you spend more time giving status than doing the actual work.

But not communicating is not going to help anyone, unless you feel confident that you can get the project back into shape.

So the deadline is missed. It happens. The stakeholders need to be prepared and they need to have runway to take action. Finding out in the final week then being asked to train up 10 new contractors is not going to work. Managers know that it doesn't work, but more often than not they feel that is the easiest way to help.

You shouldn't give up your personal time unless you feel there is some reward, otherwise you will just feel bitter and leave the company in the next crisis. I gave up a lot of personal time to save a project. I did it for my own credibility and passion, but money, time off in lieu and promotion are the rewards that keep employees. I got one week off (after giving 5 weeks of personal time), and £250 of vouchers (but only if during this crisis, I worked a Saturday on someone elses project). I left that job within 12 months.

If anything else, you'll learn the experience of what works and does during crunch time.
Historically correct (IBM offered three different operating systems) but it stopped being true a long time ago. PCs are sold as integrated systems, and they are designed and manufactured to run Windows.

You can claim it's an "anti-competitive hoodwink" but Microsoft just spent a decade with the US Justice Department's foot on its neck, specifically to prevent any anti-competitive hoodwinking.

There's also nothing to prevent PC manufacturers shipping whatever they like. Many if not most now sell Android tablets, some sell Chromebooks, the server suppliers support Linux, and so on. Some sell Linux on PCs, including Dell and Asus.

The idea that the market failure of Linux is down to some sort of evil conspiracy might make you feel better but it doesn't square with the facts.
You have to remember that America is a large country. With so many people there are more likely to be these outrageous events that draw a lot of media attention.
In fact, we actually just inherited this project (along with the mess) around 1-2 month ago from another dev team under the same manager, who have worked on it for a few month.

That seems like a serious red flag to me. That manager's career is probably headed nowhere fast...
FBI shared child porn to nab pedophiles; Washington home raided
Will do, thanks.

Never understood why Grappelli removes the button click from admin actions!
I went through public school here, and never suffered through anything worse than the general pettiness that is endemic to teachers and school administrators. There are problems with the American school system, but these outliers are not those problems. Heck, I remember in high school there was a huge protest over attempts to introduce minimum dress standards (e.g. no wife beater shirts, no spaghetti straps) in which the teachers participated in the protest.

And I don't see how this is an example of kids being "manipulated." At best this is an example of a school district not consulting its lawyer before giving a well-intentioned survey. The purpose was to try and identify kids who needed additional psychological support, not get kids to cop to their drug use so they could be prosecuted.

And you know what? It's not even clear the teacher was factually correct here. The school administrator argued that once the surveys were filled out, they would become student records (which are protected by a law called FERPA). I haven't done a close analysis of the issue, but if FERPA kept the documents from being obtained by the police, there was no 5th amendment privilege against incrimination because there was no real and tangible threat of disciplinary action. Moreover, there was no "custody" by the police which would invoke certain requirements for the purposes of the 5th amendment.

At best, the teacher was teaching his speculation about what is still unsettled law as actual fact about the 5th amendment.
Startups and The Sharing Economy
It's probably harder to create a "unit bundle" key with Valve for Steam if you're only going to sell this bundle once and never in the future. You don't need any coordination with Valve to give away Steam keys. You only need coordination with the game developer.
Will Disruptive Platforms Drive a Startup Renaissance?
Hackathons are bullshit, period. If you're working, producing anything of value to the company, even if that be simply "worker engagement," it better be on company time. Simple as that.
It might just be me, but the typewriter sounds are pretty distracting. Also, there is a bit of ironic juxtaposition in an app called "inkpen" that sounds like a typewriter. But it's neat, certainly, I just don't know why I'd use it over one of the native offline apps I already have.
Just ordered this, based on the previous editions feedback.
The downside to such a strategy might be that the reason for the impending failure is the manager, and/or the level up as well.

Most organizations operate (and should operate) according to what the top-level decides should happen. If the top-level defaults on that responsibility, then chaos will ensue.

In those cases a value judgment of the process is a value judgment of the organization, and most astute managers realize it sometimes before the "innocent" (i.e., socially naive on organizational dynamics) system builder guy realizes it.
I would recommend Yourdon's book, "Death March" as mentioned in one of the answers. Although it feels a little dated it is a well reasoned analysis that at worst can give you perspective on a bad situation. When I was in a true Death March project I was surprised that there are so few books on the same issue.
This appears to be a corollary: "Beware of bugs in the above code; I have only tried it, not proved it correct."
More details about the imaging techniques given in the article submitted earlier:

https://news.ycombinator.com/item?id=5767401

Despite that having the better explanation, the HN discussion happened here:

https://news.ycombinator.com/item?id=5773599
http://antizapret.info/site.php?id=763

It because http://stervozzinka.dreamwidth.org/15580.html contains information that it is possible to kill itself by shooting into head.
Interesting. I'm familiar with Tutte's work in graph theory & matroid theory. I had no idea he'd been at Bletchley Park. He seems to have done an awful lot of very significant work.
Is this a good book for someone that uses the language for quite some time, but never studied it deeply?

I'm looking for something like 'Effective C++' (but for Python of course): a collection of recipes and good practices that would allow an experienced programmer make a better use of the language.
Yiroco  Twitter video randomizer
tweets containing #music , @youtube , #nowplaying , music randomizer . :)
I was recently hired to complete a specific task on a project that sounds similar to this one. On the 2nd day of my involvement and having read through the code a bit, I realized that the task I was hired to complete was the last thing they should be worried about given some of the existential issues in the code and architecture given the deadline.

I voiced some of my concerns to the manager of the project. He got upset and defensive. I quit on the spot.

I had never done anything like that before but I'm glad I did. It could have been rescued but that would have taken a huge personal effort on my part that I didn't foresee being appreciated.
You mention automobiles. The historical example you could have mentioned was fully automatic shoulder arms like the "Tommy gun," which was banned after it was discovered that almost all users were criminals.

I have no opinion about the allegations against Liberty Reserve. That needs proper judicial resolution, which takes time. I will note, in light of some of the other comments here, that the United States has international treaty agreements with most other countries in the world mutually to regulate money exchange from one country to another. Once in my work as a Chinese-English interpreter (this was back in about 1997), I had occasion to accompany a Chinese official to the offices of FinCEN

http://www.fincen.gov/

so that he could discuss with United States officials how his country (NOT an "ally" of the United States) and ours could cooperate in fulfilling their mutual treaty obligations.

I'm largely with you, Daniel, in desiring government to have narrower rather than broader powers to regulate individual behavior around the world, but I'm not so sure governmental power is too broad or being abused in this case.
It sounds like this is a 'Kobiashi Maru' Test, which is a no win situation that Starfleet gives to it's cadets.

After this project you will have 5 developers, and several managers that will go on to other projects. I'd say half of those people know what you know, and no one knows how to fix it. If you just work hard on the project one of those developers or managers in years to come might come looking for you to join them on an endeavor. Other than school, I think this is how people develop trust in each other.

If you choose to stay or go, either way you'll build character. It's up to you to decide if you are the sort that digs in and runs to the fire, or the sort that flees to live another day. NOTE: not everyone succeeds that runs towards the fire, but some do, and some consider them heros. Other's consider them fools.
Ladda - CodePen
Don't forget that investigators will sometimes let people do things for a while in order to establish a more solid case.

Ethical guidelines for this kind of bystanding typically allow crimes like fraud to proceed temporarily but not murder or assault and so forth.
Friedman is such a shameless hack.

Using his column as an ad for his daughter's college roommate's business? Honestly? Ugh.

Nothing against the HireArt folks who may be great people, and maybe they are offering a useful service. I even understand why they couldn't tell Friedman not to do this for them. I doubt anyone could turn down the free exposure.

But it's just tacky, and it doesn't help that Friedman is a hack to begin with.
Seconded. I don't think the accepted answer is strong enough nor a very sound advise.
Very simply, they cannot. You need to know how to run a business and how to adapt to changes, if you want to be as successful as Google. In my opinion Yahoo! needs to learn that first.
Pretty sure it's an unwritten rule thing.
It's general courtesy to provide the original link first, and then offer an affiliate link as an option. In a community suck as HN, anyhow. I don't have problem giving you commish by any means. Enjoy.
Your assertions are interesting. I'd like to see some concrete examples of where you've seen this actually play out to make not well understood code.

Having recently read Clean Code as a C# dev, I feel the missing piece in this conversation is that the advice of small methods needs to be taken together with the idea that things should do one thing, and should be composed of items at the same level of abstraction. I feel the idea is hard to defend on its own, but with the other ideas quite easily defended.

I'm also curious about the performance problems you've mentioned above.
I was fortunate enough to experience this exact kind of death march over a period of around 18 months.

Unless you have the authority to guide the project back on track, there are only so many options available to you:

1: Document your concerns and any problems you've identified. Be objective wherever possible (i.e don't bitch about your co-workers even if the reason the project is failing is because they're fucking it up). Any problems that you've spotted and are worried about, WRITE THEM DOWN and email them to your project manager.

2: Keep a cool head. This is incredibly difficult once endless frustration sets in. Bite your tongue, and don't get personal. You will probably fail from time to time, because knowing that you're going to fail is a horrible, insomnia-inducing feeling, and your patience will almost certainly be tested.

3: Offer solutions. If you think a particular decision is to blame for some aspect of the failure, then document it, what went wrong, and what any alternatives may be.

Unfortunately, in my experience and from what I gather from other people, these kind of things tend to come along with ridiculous company politics and emotions. If your gut feeling is that it's going to fail, then your best approach is to try to raise the alarm as soon as you notice. You may be ignored or brushed aside, but you must document everything you do. Don't raise the concerns in conversation, make sure there is a paper trail.

In my own case, the project failures ultimately led to me and several other developers abandoning the company. The project could have been saved if our concerns were taken into consideration and acted on. We even presented a proof of concept redesign which solved all of the existing problems AND presented new opportunities for growth, and were told that our new design would not see the light of day. Keep in mind that we had working code, schemas, deployment plans, addressed scalability concerns, and even had a development roadmap for the new design. Some battles are un-winnable.
Why most people like sass over less?
>At some point, there might be nothing left to do except to roll up your sleeves, brew some coffee, and tell your graduate student to read the paper and report back to you.

Hahaha.
There's an app for that. http://www.cheapriver.com/#?q=python%20cookbook