skysight-inc/HackerNews huggingface dataset:
A very customized perforce setup.

EDIT ah the danger of opening up many tabs and then reading them later. Two people already beat me to the punch by 30 minutes:)
I'm still not sure if it's parody or not. Isn't this the same guy that goes on about the Paradox of Choice ruining Android?

Too Much Hardware Choice

http://www.marco.org/2730711751

"People hate choosing between similar things. The more choice we have at the time of purchase, the more stress we feel making the choice, and the less satisfied we feel afterward because we’re worried that we made the wrong choice."
I'm actually a big fan of compilers, but maybe I'm just old.
I think this game is really better than angry birds:
http://armorgames.com/play/6833/sieger
But why people don't prefer it!!!?!
do what same for Android? go native? haven't tried honeycomb but if it's that slow I say post it as an issue to android dev
The UAC runs in a context called the protected desktop. When the UAC is active things like this won't work. Your program won't be able to press "Okay" or anything.

Secondly, non-admin users can't install most drivers and autorun will ask them if they really want to run the app. Admin users can install but will also have to deal with the autorun dialog.
This is one of my frustrations. You as the company should be able to go in and remove that network - it's for your company at the end of the day.

It's like having a LinkedIn or Facebook page - you should be able to exercise some control over it, including removing it should you wish to.
Microsoft has a ton of stuff here, originally it was mostly localization work, now they do a bit of everything and have a few big datacentres as well. They do enough that "Microsoft" all on its own is a few percent of the GDP.
I agree except I don't think continuous deployment necessarily means automatic deployment. Every deploy should be done by a person and tested right after; none of this "push out all commits at X time" or "push as soon as it's committed" as both are risky.

During the day is usually preferred and never at 4:59PM on a Friday or right before everyone goes to lunch (ever had to clean up a downed cluster when some jerk pushed bad code and the whole team went to Sweet Tomatoes? yeah).

To help troubleshoot breaks, have a mailing list with changelogs showing who made a change, time/date, files touched. Also have your deploy tools mail it when there's a code push, rollback, server restart, etc. Have a simple tool someone can run to revert changes back to a time of day so if something breaks just "revert back to 6 hours ago" and debug while your old app is running (nice to take one broken box offline first to test on).
"It's just policy."
Heh - I'm dramatically different from the 23-year-old me and I'm only 34.

(And thank god, because the 23-year-old me was both insufferably stupid and didn't know it.)

(Now at least I know it.)
That's what happens when you put something on github! In fact, I bet you any money that someone has already taken the code and created a 16-bit logic unit INSIDE minecraft INSIDE your turing machine.
I would actually say that Microsoft's tunnel-vision on everything being a Windows powered "pc" is why they have always failed in the tablet market over the years.
What type of setup do you use to analyze, debug, and follow the code?

Any tips on getting started with module development?
Though I presume you know about it, I haven't seen Homebrew[1] come up yet. It has native support for installing from tarballs and pulling from repos.

[1] http://mxcl.github.com/homebrew/
And if you look at questions on Stack Overflow you've got:
532 tagged [Git]
119 tagged [Mercurial]
Just to give you a (unscientific) sense of the bias in the Stack Overflow community.
Two better approaches come to mind to resolve this:

2. Full-on, properly managed releases like they do in large IT corporations, such as banks, where a "release" is not something you kick off from home via SSH on a Saturday night, but a properly planned effort that involves critical members of the dev team as well as the QA team being present and ready to both test the production system thoroughly and fix any issues that may occur.

What you describe in #2 here sounds like a complete anti-pattern when compared with the idea of continuous deployment and automated verification. This 2nd approach sounds like a huge manual effort.
In order to clarify, I assume when you say "no filesystem", you mean "no user-visible filesystem, but is still muggle-usable (and might well have a filesystem under the hood)", yes? Because we've had computers without filesystems for about as long as we've had computers. Computers with filesystems are a significantly more recent innovation.
Apparently you didn't read what I wrote. Apple cannot prevent you form getting the source code, but the source code does not include information like "the binary will be installed to this location and will be considered a Mac OSX private framework." When something is considered a 'private framework' in OSX it's primarily an install location which does not change the source code as install location is usually a build-time option. Build-time options are not something that is covered by the GPL.
Designing Beautiful Ruby APIs
In my experience , there are two kinds of deployment -- ones without DB changes and ones that are accompanies with DB changes.

The deployments that do not require DB changes are easy -- mirror the prod box(non db) onto a smaller box, , deploy upgrades/updates to prod box . If things go wrong, put mirror box online with a DNS/proxy configuration while apologizing to your customer who complain about slower performance .

When DB changes are involved , you need to have your DBAs do a dry run of backing out changes-- after all practice makes perfect. Communicate scheduled outage to customers, backup db . Mirror your production box. Roll put update -- if things go wrong, restore DB and bring the mirror box online.

I have always focused on DB aspect more -- loss of integrity of data can cause customers to look for your replacement.

But I am not sure if weekly upgrades of production environment with paying customers is advisable .
I can't believe in how misguided this post is...

1. They provide a service to people around the world, yet they don't ensure that someone is available as an emergency contact on Sunday evening, when the first post-deployment usage happens.

2. They don't have a universal list of "this breaks, contact that guy".

3. They don't have a known instant rollback procedure for a release.

4. They don't have cross-component integration tests and they don't do them manually either.

5. They decide that since they can't do a release that doesn't break stuff and can't organise themselves to resolve it quickly during the weekend when it affects only a small number of people, they'll do releases in the middle of the day now, so that they hear customers complaining right away.

Is that for real? Is he serious? Here's what I would get out of that issue (even if it's basically reiterating the "wrong" things above):

They need to do more integration testing before a release. They need to know who to contact and have to make sure the person is on call and ready for action. The person handling the issue needs to have a simple, quick way to reverse the release without manual intervention (tweaking the code). Again, this specific issue should get regression tests right away. And the most important thing - NEVER treat your customers as a test suite.

Of course I'm aware not everyone can afford operating like that. But at least this could be their goal. "Let's make breakage affect more people, so we know about it earlier and when we're at work" is a really silly conclusion.
As someone whose duties include branch management and team happiness, moving the DVCS has been a revolution. Improved my job happiness significantly.
I don't know your situation, and I'm only speaking from my own experience, but I've been in a situation where I was absolutely certain that quitting was not an option (because of mortgage/bills/the usual). Once truly burnt out, I had no choice but to leave, and it was only then that I saw, in hindsight, that not only had quitting been an option all along, but that it would have been far less damaging in every way (financially, mentally, career-wise) to quit before I got burnt out. And there were plenty of other, better jobs waiting.
I wish I knew all that, but the extent of my emacs usage is editing resolv.conf ;)
Their release procedures didn't cover the case, and they're fixing it ("modifying the communication ... [to] fail early and loudly during our initial tests", according to the "with details" post on their status blog[1]).

But I still find their lack of monitors... disturbing.

[1] http://status.fogcreek.com/2011/03/sunday-night-kiln-outage-...
It absolutely is, and I'd be surprised to see this kind of effort from any but the most paranoid corporations (like, as I mentioned, banks). Automation and continuous deployment are definitely the way forward.

But even this gargantuan effort is a better option than just "let's deploy and wait for our users to tell us if anything has gone wrong".
Comscore had them at 25% in December, 24.7% in January.

http://www.comscore.com/Press_Events/Press_Releases/2011/2/c...
Lucknow Pro Biking group; R.O.D.S (Rider of the storm)
Yes, iOS uses a filesystem under the hood. The applications just never expose it to the user. As an application developer you should be aware of it, but as a user? it doesn't matter one bit.
Sure, it's not 'simple', but Livejournal had that feature before I even heard of Facebook. Dreamwidth took that concept and made it even more sophisticated.

Which is part of why I use Dreamwidth. Under a pseudonym, of course. :-)
Being uncommon means…
I think this metric is not really useful: Maybe git is just harder to use (no git/mercurial please, just my first thought on the usage of question tags as a - unscientific - metric).
Oh god. I release 5pm pacific every week because users "can't have a single second" of downtime. We manually test an ever growling checklist fo functionality. There is always, always an issue. The angry emails start to roll in around 5:15 pacific.
XOmB Exokernel OS written in D
If only there was an Android version too
Why is C 'supposed to be primitive?' If C was supposed to be so primitive, there wouldn't even be 'str' functions, it would just be memcpy functions and you would be responsible yourself for keeping track of null terminators.

C just needs a bolstered set of string-handling functions. Much like C++ has the Boost libraries.
I agree. My other thought was 'isn't there a staging server in there somewhere?' Something that is near identical to production, with fake production data, etc, that could surface the problem before a customer sees it.

btw, props to Fog Creek and OP for airing their dirty laundry. They take some heat, but in the end we all learn from it.
From my reading of it (disclaimer: I've only done a tiny amount with ruby) A package uses rubygem to install a-blah 1. This causes packages using require 'blah' that are not connected to rubygems to break if the a-blah installation overwrote an existing version of blah 1.1 (which you installed alongside said packages)
A tribe-friendly ecosystem for Indie games
You might get a better deal in other countries but 12.5% corporate tax is hard to beat. Also the fact that just about every silicon valley heavyweight has significant operations (dev, marketing & support) in Ireland is an indicator something is being done right over there.

Cheap, regular flights from Dublin to just about anywhere in Europe make those trips to London, Paris, Amsterdam and Germany into just day trips. I found it was a pretty good hub.
Good think that I'm only running a Linux machine.
If you're making a big change you first cut a CR and get approval of any teams involved. At change time, everyone knows they need to be on-call if something breaks, preferably in a live chatroom.

The rest of the time devs should just deploy when they think the code is ready and have tested it on a like-production box. They then manually verify the change worked. You use automated monitoring to ensure when something does break you are notified immediately.
Scott Chacon (author of Pro Git, Git evangelist for Github) has said in his Changelog interview that Git and Mercurial are in fact extremely similar. He wrote some kind of tool for letting the two work together, so he had to learn the internals of both to do so. His take was, use either one. Just make sure you use distributed version control.
AOL still has free email accounts, I believe.
A computer without a filesystem that predated personal computers can be called a pre-PC device if you like ;-)

If a device has a filesystem for its own use but does not expose the filesystem to users or to applications, that's a post-PC device. If we merely denude the device of the Finder but all the apps use the filesystem, I'm on the fence. It's a post-PC device in all the ways that matter to users, but it feels transitional to me. Future generations of post-PC device won't expose a filesystem to developers or users.

So yes, iOS devices are post-PC devices, but they can become even more so.
Another apache hacker answering :-)

I use emacs and gdb to muck around the code. Apache has a lot of backwards compat warts with regard to which header files define things, unfortunately, but grep (or ack) and ctags will get you around.

The best way (by far) to learn about module hackery is with Nick Kew's book, http://www.amazon.com/Apache-Modules-Book-Application-Develo...
Well, I prefer TeX to LaTeX because (1) with TeX the documentation is just Knuth's 'The TeXBook' but with LaTeX the documentation is in at least two thick books each with several authors none of whom is Knuth, (2) TeX is rock solidly frozen but LaTeX is not, and (3) LaTeX makes assumptions about what is wanted and, then, is easier to use within the assumptions and more difficult otherwise.

I have over 100 macros I wrote for TeX for tables of contents, cross referencing, verbatim output, putting TeX text on figures as annotation, automatic chapter, section, figure, and table numbering, putting a frame around foil pages, etc.; those macros go back over ten years; due to the fact that TeX is frozen they still run just fine.

But for both TeX and LaTeX, I'm looking for darker fonts, especially for the TeX and AMS math fonts. Any ideas?

For the emphasis on plain text in the article, sure: I do nearly all my typing just into my favorite general purpose text editor KEdit.
Stackoverflow itself seemed pretty Windows-centric last I looked at it. Makes sense considering it was launched by two prominent Windows developers.
Would you want every conversation you have with your spouse/child/parent to be available to every single other person you know?

Regardless of how sincere and honest those conversations may be?

If not, then this idea that "the days of you having a different image for your work friends or co-workers and for the other people you know" is very much not over.

The fact is, people have private interactions with other people all the time and they expect it to be private and society accepts that it's perfectly alright and natural for this to happen.

When I'm with someone else and they get a call from someone close to them, I excuse myself from the conversation in some way. That's just the polite thing to do.

This idea that all this is coming to an end is just wishful fantasy on the part of the owner of a site who's existence and popularity probably depends on this being true.
Jobs4hunt.com - a new job portal
This is pretty cool -- thanks for including DuckDuckGo!
That is why I put it in quotes. They "can but wont" which translates to "We can't because insurance for men costs more because of the statistics". Given that rule of thumb they will increase females premiums.

Not only have I worked for insurance companies, but if I was one, this is exactly what I would do if I was told everyone had to be treated equally.
Biggest statistic is that 60% of people are not using source control professionally!!
The Android team uses git.
will do! I'm mike@subelsky.com in case something gets lost in translation
Did anyone else notice the that the chart, "Do People Love or Hate their Version Control System?" was horribly misleading? CVS gets 3.5 hearts, and SVN gets nearly 4. Meanwhile, far below on the page: "Only 11% of Subversion users said that they loved using it; the number was zero for CVS and VSS."
I don't do Windows (not necessarily by ideology, I just don't do it anywhere I'd learn about IT issues), so this is an honest question: Assuming a decent IT policy that closes off the worst of the security issues in other ways, and which won't change even if you upgrade, and assuming you're not a Windows development shop, what is the big business advantage of moving your company from XP to Windows 7?
The Prosaic, DIY Reality of Software Houses
very much in active beta... looking for feedback
That is why I put it in quotes. They "can but wont" which translates to "We can't because insurance for men costs more because of the statistics [showing men have more claims therefore have to pay higher premiums]". Given that rule of thumb they will increase females premiums to make them equal.

Not only have I worked for insurance companies, but if I ran one, this is exactly what I would do if I was told everyone had to be treated equally. How can I charge men less if I know that they are going to make more claims?
I don't see contact info in your profile, but email me and we'll talk!
So I started using git with my latest project, just to get a feel for what all the Ruby on Rails guys were talking about when they weren't bragging about the size of their Macbooks. The koolaid is delicious. Even in a one-man, one-repo world, I spend a lot less time fighting my VCS for dominance.

Example from today: I was working on my deploy branch, where I typically only make to-be-deployed-within-the-hour microchanges. Then I saw another bug, so I squashed it. Commit. Then I saw another bug. So I squashed it. Commit. Then I saw a major opportunity for a simplification with a refactoring. Then I realized the refactoring was under-tested and that failures would be catastrophic, so I started adding extra tests. Now I'm fifteen commits past the last deploy, I have code that I'm 85% positive works on my must-not-fail deploy branch, there is one commit in there which addresses a bug which I want dead, and it is quitting time.

I have been in this state in SVN before. Recovery is NOT fun.

git branch all-the-work-i-did-today #Creates a new branch whose history looks exactly like deploy's does.

git reset --hard production_deploy_92 #Moves head of deploy branch to the tag of the last deploy, essentially forgetting commits afterwards.

git cherry-pick carefully_copy_pasted_hash #Nabs the one bug fix that I really wanted to deploy today.

Git makes my development and deployment processes better. Transformatively better, in some cases.
I've heard that the server it runs on is the most powerful machine Google owns. Perforce can't be distributed and has to keep track of all the files that are opened by every user (p4 edit). Must be quite a beast.
I know, I thought about that too. We're constrained by the availability of the space and the time needed to arrange all the financing. We're going to be doing this at least once a year though and next year I definitely want to do it that way.
Because throughout history and even today their rights and voices are suppressed. Even in America they couldn't vote up until 1920s.

It seems as long as there is memory of that oppression, and as long as there are still glass ceilings, or places in the world were women are still oppressed because of their geneder it is worth celebrating this day.

> why exactly does she deserve to be celebrated?

Well we didn't need much reason beyond their gender to oppress them all those years (and still do) so it seems we can at least acknowledge their struggle and suffering if nothing else. Or are you worried about reverse discrimination? "Can't celebrate too much now, they'll get cocky and we'll have to set them in their place again"
Another difference that I haven't seen anyone talk about yet is the fact that while in both games, as you progress, you get different types of ammo, in CTC, you can switch between the different types of ammo at will, while in angry birds, you're stuck with the ammo types you're given, in the order they're given.

While this reduces complexity in Angry Birds, it also means you can't always choose the most devastating ammo, which adds a bit to the challenge.
Save money from Agile Development
Ten Things Every WordPress Plugin Developer Should Know
Agreed. The file system is hidden away as an unnecessary distraction from the user's view of the task at hand. The iOS devices are arguably more task-oriented than PCs.

Also in calling them post-PC devices Jobs is signalling his intent to continue moving in a new direction, one that separates them from the pack. Contrary to the article, Jobs did not claim that tablets are post-PC, just that his iOS devices were post-PC.
> Only 11% of Subversion users said that they loved using it; the number was zero for CVS and VSS. Compare that to the over 40% of Mercurial and Git users that love using them!

Is it just me or doesn't this not reconcile with the relevant portion of the graphic?
Netflix has a pretty weak first-run movie selection.
Why You Watch Cats And Epic Fails 13 Million Times A Day – with Ben Huh
This is great news! As a Baltimorean I am extremely excited to see something this ambitious come to the East Coast, and better yet my neck of the woods.

I will most definitely be making an effort to participate in this. Great job, Mike.
Yes, as of now I am also giving up alcohol and sweets. So you have company :) Thanks for the 'push' because I forgot all about it.
The catapult touchscreen physics is enormously satisfying, as is the scale change when you pan between catapult and target.
this is music to my ears! We actually have a very vibrant innovation/startup community in Baltimore. Check out our Facebook Group to get a quick firehose: https://www.facebook.com/home.php?sk=group_160612380624897&#...

Also check out http://startupbaltimore.org/, http://www.baltimorehackathon.com/, and the http://baltimore.startupweekend.org/
A computer without a filesystem that predated personal computers can be called a pre-PC device if you like ;-)

I was pretty sure this was going to be part of the answer, but I laughed out loud when I saw it anyway. Thanks for clarifying your ideas. :)
Clickable: http://www.favilous.com
C macros are not Turing complete, they're a pushdown automaton.

C++ templates are.

Check out this IOCCC entry which does simulate a Turing machine, but only by having another script repeatedly run it.

Edit: Yes, I meant to copy the link, see mchouza's comment for the link.
Taking corrective action with git pre-commit
oh awesome! I'm really glad to hear it. See my comment to Kovar about all the other things you should check out if you like this :-)