skysight-inc/HackerNews huggingface dataset:
Since people liked that one, my Dad also had another good engineering disaster story, though this one is pressure related, not electricity related.

He used to work for a company called James Hardie, that made asbestos cement sheeting. Part of the process involved baking the sheets in a huge autoclave, like the one pictured here [1] (note the size of the man). An autoclave is an oven, filled with high pressure steam.

One day the door blew off the autoclave. The door disappeared, and the autoclave itself acted as a rocket, about the size of a shuttle solid fuel booster. It sheared off the bolts holding it to its foundation, rocketed though the back wall of the factory and ended up in a body of water about a mile away.

[1] http://museumvictoria.com.au/collections/items/756810/glass-...
It's the waiting that's the hardest part
Git's commit log is a hash tree (like the bitcoin block chain). When you commit you get a SHA for that commit. Part of the SHA contains the SHA of the commit before it. When you rebase it changes the SHA's of all the commits you've made. That's a lot of why you end up with conflicts when you don't know what you're doing. Never rebase if you've pushed the commits to a central repo because git will detect conflicts of the changes. You end up with duplicate commits with different SHAs after you resolve the conflicts and continue.
Ask HN: Why everyone is trying this pinterest layout?
All my favorite website are now having pinterest like layout. Is there any evidence that this is a better layout ?

Has anyone done AB tests ? Or is it just the new fad in the web world ?
That.is.awesome!
One item of curiosity: We all know who recognizable figures such as Lincoln, John F. Kennedy, and MLK Jr. are. When did they decide to name streets after them?
First, while conceivable, that's unlikely.

Second, and I think more significantly, they've still got a database of plain-text passwords sitting around. The fact that they might have some systems in which they are stored hashed is kind of irrelevant.
I've fleshed out the details. It's not quite realistically feasible today, but this should be available in 10 years.

The biggest hurdles to overcome are:

-Creating the flight management software

-Networking 260,000 devices with wifi technology

-Getting 5-6 MWh into the air to charge these 260,000 devices each hour.

-Battery life expectancy.

http://gilgatech.tumblr.com/post/49231953391/quadcopter-bill...
Hey Osiris, thanks for giving me some of your insight. I would like to follow up to with some questions:

Why are you not understanding the code other devs are writing (and vice versa)? Are you finding code reviews difficult in such an environment, or is it that the tools that are available aren't that great to use.

With those quick little things. Are you finding that real time chat tools such as GChat or Campfire not properly facilitating that issue?

A lot of people don't like the tap on the shoulder, but Sqwiggle kind of encourages that (I really like the idea it makes it much less lonely).
Agreed - it just takes a small amount of time now to start tracking, so in the future you'll have a clear idea of where you began and how far you've come.
I would build one for new email alerts, a different color for each account...
I've never tried, let alone use Opera. I just keep hearing something like that exists.

For now it feels like a 'me too' product which simply exists in the market.
Out of curiosity, why do you say that?

I ask because I'm planning on going there next year for computer science.
In all honesty, I would be more concerned about availability than someone breaking the encrypted data. Especially so if this satellite provides mission-critical support for the warfighter.
So... does enjoying dressing up for work count as a personality plus or minus?
git checkout -b branch_fix; # for safety

git reset --hard HEAD~1

git fetch;

git merge origin/master;

git push origin HEAD:master;

git push origin HEAD:old_branch;
Postgresql-async - an async, Netty based, driver to PostgreSQL using Scala
Ah. Yes, well then those too. Although, I fear I won't see an end to either of those in my lifetime and (honestly speaking) the lifetime of our species.
Not saved, but it adds up when you have a torrent of "Merge branch master of http://myownrepo.com and merge conflicts every day.
Asynchronous Block Operations in Objective C
What protection do you use for the Pi's GPIOs?
According to Last Call by Daniel Okrent, Gough St was named after famed temperance orator John Bartholomew Gough.
I'd assumed that was true until I saw this site.
Wikipedia has support for both theories, but it looks like Charles H was the real namesake.
I almost read 'faster than speed of light', my jaw dropped...But then it was sound. A great feat, nevertheless.
Quality of Communication is what i see as a challenge. It is as simple as the quality of voice/video calls, Skype and Hangout handle well when ppl speak on the microphone, but when there are folks sitting behind the laptop or comp, the voice clarity is impacted drastically. I have to keep reminding ppl to come close to the microphone and talk, i do it once, twice, thrice, then i give up.

From a person on the other side of the phone where all the action happens, i need to be focused and aware on getting close to the microphone and speaking, this impacts my natural posture(body language) while communicating.
The Most Difficult Bug
I used to run a consulting practice where all we did was technical project rescues. I can say it is never really fun, almost always sucks and is never easy (which was the draw for me). The range of issues is huge, from entrenched teams unwilling to adapt, to horrible leadership to just a general lack of experience.

The recipe is almost always the same though, identify the gaps, increase communication, organize the project, reduce the initial scope, set some realistic deadlines, get some easy/quick wins and get both sides (IT and business) to the table to discuss reality regularly.

Also, quickly get rid of negativity, if you find someone that pulls the team down and out, try to pull them aside and get to the root of it. If they can't be influenced to help positively get them off the project or out of the company quickly, like ripping the band-aid off. No one likes to talk about firing people, but reality is what it is, one bad apple on a team can destroy a project by killing morale and feeding FUD. And frankly, you aren't doing that person any favors by letting them stay and be miserable either.

My 2 cents, projects need to be rescued because of weak leadership and decisions that went without being made for too long. A bad decision is almost always better than no decision, at least you have something to work with. No decision is almost always a mistake and guarantees nothing changes.
Honestly, it surprises me when people say money doesn't buy happiness. Obviously I can only speak for one person, myself, but I've absolutely become happier as I've made more and more money.
Yes, but today as I was leaving work it told me there was heavy traffic. There wasn't any way to reroute so I used google maps and this time it told me traffic was light and gave a different commute time. All happened within a minute so it seems unlikely that it was right in the middle of updating traffic conditions. I drove the usual way and the traffic was normal.

So I'm not sure what its up to.
Because Opera has

a.) a bookmark manager that doesn't suck (split view for life)
b.) configuration dialogs that aren't boiled down to the utter newbie minimum, and a context menu that actually has a bunch of things in it
c.) a GUI that's configurable like play-doh (even more so if you get into .ini files as well)
d.) if that's your thing, there are skins available for it that seriously maximize screen estate

What are you calling gimmicky? And are all the CLI commands unix comes with gimmicks for you, too? Do you consider having more than one mouse button a gimmick as well? Heh.
A couple of years too late for Russian boycotts, Opera already got itself the most rapidly decreasing market share:

http://gs.statcounter.com/#browser-RU-monthly-201103-201303

http://gs.statcounter.com/#browser-UA-monthly-201103-201303

http://gs.statcounter.com/#browser-BY-monthly-201103-201303
When I was a kid growing up, it was common to see vehicles from the outback with a square water bag suspended from a frame in front of the grill.

The bag was canvas and leaked slightly--enough to keep the outside moist so that the contents would chill from the wind as the vehicle drove along. The water was nice and cold, just right for a hot summer's day.

Oddly, I don't see them any more. Perhaps there are enough roadhouses along the highways that anyone can pull in and buy a chilled soft drink when they want.
In this case I'd like to be able to revert the merge.
Maybe if you've never written C before...
No numbers?
The Silk Road hit by DDoS attack
Was this meant to be a response to my question to `coldtea, or a general comment? The exact same words could be used by an IE user describing Chrome, or a Windows user describing OS X. They make no reference to "better."

(Not to mention that Opera - the source tree and the product - is older than most of major browsers today, so technically others are the "me too" products...)
This would encourage companies to engineer products with longer useful lifespans, or to facilitate refurbishing instead of destruction.

Or just bake the cost of disposal into the sales price of the item.
Best Java Summer Training Noida 2013
Java Summer Training – Join our summer training program in Noida in Java, also for various course like Embedded Systems Training in Noida, Ethical Hacking Training in Noida, HR Generalist Training in Noida, Java Training in Noida.
Ampere - A bittorrent client that runs in chrome without plugins
I built this for our company using IFTTT; we have a little blue siren that goes off when a user converts. It's powered by the production app sending an email to IFTTT which power cycles a Belkin WeMo. Very simple, and it works quite well (excepting for a 10 second or so delay between the conversion and the siren going off).
Empirical study finds consumers face risk of losing money on Bitcoin exchanges
Arduinos can (supposedly) host webpages, and pins can be powered or depowered by (properly parsed) HTML POST commands. Combining this with a relay means we can create WIFI website interfaces for anything that uses electricity.

The opportunities to improve current products are so endless that I become overwhelmed whenever I think about this. We all have the parts to do this today, but so few are assembling them.

---

Want to set an outlet to turn on or off at different times? No need to buy a timer, just goto that outlet's website on your WIFI LAN, and set it on a timer. Or you could depower the outlet to make it child-safe.

Are you going on a trip and you're afraid you left the toaster plugged in and your house might burn down? Just VPN to your home LAN, sign into your kitchen's website and have it power off all outlets.

Locked out of your car? Pull out your phone, securely sign into your car's website, and tell it to unlock the doors.

Power and depower garage door openers, sprinklers, RC cars, even industrial equipment from a simple web interface.
I suspect the other student was more susceptible to this sort of thing since he was a non native speaker. I'd be curious to see if it would've worked on an American.
It's a comp submission: http://www.ludumdare.com/compo/ludum-dare-26/?action=preview...

In the final graphic he says it took him only 8 hours though.
No, of course not - how often do you actually look at extended windows of history... But it still pains me to no end when my coworkers constantly commit history like:

Commit d
Parent a b
Merge branch origin/mainline into mainline

Commit c
Parent a
Something they did

Commit b
Parent a
Something I did

Commit a
Or better yet, make it interactive with something like this:

http://shop.evilmadscientist.com/productsmenu/majors/150-pan...

Peggy's could be fun too:

http://shop.evilmadscientist.com/productsmenu/tinykitlist/75...
Bcron - a cron system designed with secure operations in mind
As someone who works with a fairly large number of committers with many branches, I prefer merges to rebases.

The reason is simple, you always know _why_ something happened, which is quite important when looking for clues in the history. When trying to figure out what old code was intended to do it's much better to see it in the original context, not a re-written to merge context. As a benefit it also preserves change dates.
Feature branches and feature flags are orthogonal.

I have no idea how toggles could negate the need for isolated development branches on an 'important' codebase with multiple contributors working on the same areas of concern.
Both Hong Kong and Singapore are larger financial centers than Tokyo. I agree about Frankfurt -- in Europe, Geneva, Zurich, and Frankfurt are all about the same size.
Legos - so very much a personal pet peeve.

see this discussion:
http://english.stackexchange.com/questions/10839/legos-not-l...

Although I very much disagree with the upvoted answer which essentially says we're free to invent words and call it english.

1 Company called Lego
1 lego brick or piece
1 lego set
1 lego construction
2 lego bricks or pieces
2 lego sets

To me, it's like 'sheep'. One sheep, flock of sheep - never 'sheeps'.

It's not so much the problem of pluralising the word, but by pluralising it, you're saying that individual piece is a Lego, which makes no sense to me.

EDIT: To prove my point. Take this story:
A man walks into an Apple Store. He buys 1 Apple MacBook, 2 Apple iPods and 3 Apple iPads.
He takes them home to configure and set up.
His wife walks in. Does she say:

a) Oh look, my husband is playing with his new Apple products

b) Oh look, my husband is playing with his new Apples
Programmers are Not necessarily bad designers
Thank you elango. It's worth noting that something this basic is still an issue to a lot of us.
I think this is an unfair standard, and although I am a founder at my place of employment you can be assured that I will not use "we" to describe my positions on topics without sign off. As a general rule my opinions and those of the firm are divergent.

When I speak I speak only for myself.
http://source.android.com/source/building-devices.html

"All configurations of Nexus S and Nexus S 4G can be used with Android 4.1.2. On those devices all the hardware is functional."

That's the only compatibility I've seen offered by on the vanilla Android.
It's only complicated because people don't realize how it works. Half the people in this thread advocating to use rebase aren't saying when it's ok and when it's not ok and why.

When it's ok: You are working on your own line and the commits you've made are not in a central repo.

Why: Git commits are a hash tree and when you change one commit it changes all the SHAs that come after it. This makes git see your commits pushed remote as different then the ones that are local. The commits have the same changes so it puts duplicate conflict markers everywhere.

Most people love it once they realize how it works.

A lot of people use version control also as a backup in case their hard drive fails. Because of this they are scared of staying on a topic branch for very long, so they push then rebase often leading to conflicts which are scary.

https://en.wikipedia.org/wiki/Hash_tree
I think you hidden your point a little too well. If you tried to say that kids are not adults, I agree, but that makes telling them when they are wrong even more important, instead of encouraging them to be "clever" in such ways. When they make a mistake, it should be recognized as such, not treated as "yet another wonderful expression of their creativity and free spirit".
such a layer would be difficult to provide in a way that isn't misleading, if the hypothetical subversion expatriate currently uses any functionality involving multiple (SVN) branches.
There are "feature branches", and there are "patch sets with four patches and three merge commits that are there just because the submitter did a bunch of pulls while working on it."

If you're dealing with a large code base with many submitters, you have to demand that individual submissions apply cleanly. That is isomorphic to demanding that they be rebased.
ZX Spectrum all the way!
Some people have done A/B test on that vs. their old layout. I'm sure it worked great for a lot of people - again, vs. their old layout. That doesn't mean it's the best layout. There's no such thing.

It's now being copied by sites that should probably not use it. The key is always to test, never assume, and never assume you get to the final answer. Constant optimization is key.
Or just use mercurial which tends to do the Right Thing by default more often.
I don't think that's really fair. Even if you work on a failed startup and invested all your money in it, you still have more programming experience than you started with. And programming experience is worth plenty of money in our field.
Question: why have commercial airlines not added solar panels to the wings to power things like the a/c systems or other auxiliary power requirements? Could that not reduce fuel consumption?
Box's Sam Schillace on enterprise software's hard curve ahead
There's a simple concept at work here: origin wins.

Whatever is on origin at the moment of you wanting to merge your code is what your code has to work against.

When you use a rebase strategy you're allowed the opportunity to make sure your commits actually work on top of what's on origin, and fix merge issues with those commits as they happened.

So you rebase, run into a conflict, fix the conflict, run your tests, make sure everything's green, and continue the rebase.

When you do the same thing with a merge strategy what happens is you end up fixing the conflicts as part of the merge, and your fixes are hidden in the merge commit.

This means your commits prior to the merge commit are broken. They didn't take into account the work that was on origin at the time, and thus they are useless without considering the conflicts that were resolved during the merge.

The history you describe is not useful unless it's green and could be applied to origin without conflict. The only way to ensure this, both before and after your commits end up on origin is to do so via a rebase strategy.
I am interested in any study that actually measures the effect of rates of tax on overall happiness.

> Other theories exist - such as that people resent being taxed

That part is a fact in my experience. Some people resent being taxed. I think all people seem to resent some tax or another.

> with reduces their utility more than what they paid, or that people resent being given underserved money, which raises their utility less than what they received.

I inferred that kind of thing from the grandparent comment.

Perhaps the solution to this problem is just in better marketing, rather than in not doing the transfer.

Convincing/structuring payment so that people think they are deserving can't be that hard.

>Maybe there comes a point where, instead of finding Kaldor Hicks optimums of Pareto efficiency, one cares more about fairness, and see this redistribution as unfair. And Kaldor Hicks is about redistribution as can be.

Thanks for this reference. I just looked up Kaldor Hicks and think it is an interesting tool.
It's one of those wrongs that will never be righted - like brits calling Los Angeles 'Los Angelease', or those who, after all these years of hearing it pronounced correctly still insist on calling Linux 'Lynux'.
Cool project!

Maybe iterate it to use LEDs instead of incandescents.

For hardware hacking- you have 3 types of hardware that can make life easy- but there are tradeoffs:

1) Arduino
2) Raspberry PI
3) Beaglebone

Arduino is great when you want low power, but it isn't an awesome internet platform.

Raspberry Pi is great when you're going to leverage a full blown PC Monitor, but using it for hardware hacking requires a bit of elbow grease

The Beaglebone is great for when you are doing something internety & hardware hacky, but without a full blown pc monitor.

I would have done your project with a beaglebone, fwiw. I'd also have used LEDs instead of incandescents. But this is a great project! Nice work!
Not too long ago, opera was one of the best mobile browsers for Android... That was before google released a decent mobile build of chrome.
Same kinda concept to create a shelf 3D effect : http://codepen.io/chriscoyier/pen/gGiAE
I remember reading that Palo Alto streets (or maybe some subsection of them) are named after Authors. I've always been curious about this, but never looked into researching it further.

Maybe I'll give it a shot now :)
Not at all. When we have an opening I get dozens of those a day. I honestly skim them to see if there is any relevant information (there usually isn't)... and then go straight to the resume. So the language just doesn't register with me, at least not consciously.

Well done versions include a couple of nuggets of information telling me why I should open that resume, but that's surprisingly rare.
No kidding. Nothing makes you miss svn more than an inappropriate rebase. I've done it twice now, & sorely regretted. Heck, once, I was bit so badly by it that I actually said something positive about Rational Clearcase.
Your example is incorrect.

If you're the maintainer of wonnage/foo and bar submits a pull request from bar/foo, bar/foo should have been rebased on top of wonnage/foo, not the other way around.

(And if you are in a situation where rebasing on top of bar/foo would actually do anything, that means you have local commits that haven't been pushed to origin, in which case accepting the pull request is dangerous.)
And yet, because of DRM when I think about buying an electronic version of something, I still feel in my gut "It's not really mine", and I hesitate to buy.
LOC was used extensively in costing models with waterfall development, and even some with iterative dev. But things have changed some.

One thing I still use it for is monitoring features to maintainability. In other words, in established products/projects I will monitor my teams LOC checked in and I look for it to stay as small as possible or to decrease with revisions. Obviously this doesn't always happen, but I would rather reward the guy who removes 50 LOC versus the guy that adds 200, assuming they both got the same job done and features were delivered.

I feel that LOC should never be used outside of the development team. i.e. No non-technical business mgr should ever see the metric as it is too easy to misunderstand or abuse.

Also, LOC as I use it for established teams is almost totally useless in startups as the amount of code is usually pretty rapidly changing and expanding. Thus making LOC deceiving and misleading in my opinion.
I hate to comment only on details and not on the actual content itself, but the aggressive use of bold text led me to read only the bold text. I didn't even bother to give the full text a chance. I saw typography that seemed geared toward the skimmer, so I skimmed. I'm not sure if that's the desired result, but that's the result it had on me.
I'm sure coke thinks trade secrets are both quite important and last quite a while.

The quality of evidence tends to outweigh the quality of lawyer, assuming reasonable competence.