Hacker Newsnew | past | comments | ask | show | jobs | submit | 2013-07-23login
Stories from July 23, 2013
Go back a day, month, or year. Go forward a day, month, or year.
1.The slippery slope (90percentofeverything.com)
520 points by justinph on July 23, 2013 | 135 comments
2.Block NSA funding for collecting the call records of all Americans (defundthensa.com)
482 points by sinak on July 23, 2013 | 220 comments
3.The sad story of Facebook Platform (pandodaily.com)
335 points by rpsubhub on July 23, 2013 | 100 comments
4.Leaked report shows high civilian death toll from CIA drone strikes (salon.com)
298 points by stfu on July 23, 2013 | 151 comments
5.How Gmail’s New Inbox Is Affecting Open Rates (mailchimp.com)
287 points by duck on July 23, 2013 | 213 comments
6.Hillbilly Tracking of Low Earth Orbit Satellites (travisgoodspeed.blogspot.com)
280 points by wmat on July 23, 2013 | 33 comments
7.The unprofitable SaaS business model trap (asmartbear.com)
223 points by aaronbrethorst on July 23, 2013 | 98 comments
8.Sneak peek of Macaw – a code-savvy web design tool [video] (macaw.co)
218 points by jack7890 on July 23, 2013 | 71 comments
9.No filter: the meanest thing Paul Graham said to a startup (brandonb.cc)
216 points by brandonb on July 23, 2013 | 107 comments
10.Life in the Boy's Dorm: My Career at Sun Microsystems (consultingadultblog.blogspot.co.uk)
211 points by casca on July 23, 2013 | 61 comments
11.House forces vote on amendment that would limit NSA bulk surveillance (guardian.co.uk)
210 points by uptown on July 23, 2013 | 35 comments

And this is why you do "ghost employee" audits. In a past career I used to work in the Controller's office for one of the Big 3 auto companies. One day, I was sent some bullshit email that I needed to do about 100 audits including "ghost employee audit" and check a box on a web form that all were complete. For shits and giggles, I decided to take it seriously. I altavista'd "ghost employee audit" and learned it is a reverse recon of the payroll system.

I did the audit by making every manager certify a list of employees. I found two employees that none claimed. One dude was well known within the plant and fixed any broken motors. No one had heard of the other guy. I convinced the payroll clerk to just stop paying the other person. He got pissed, and eventually tried to get a union rep, but the union decided not to rep him.

It turns out this "ghost employee" had collected over a million dollars in salary and OT, yet not worked in about a decade.

I asked about an award for the savings, but I was shot down because the union didn't want to let it out that they didn't rep a guy, and the company didn't want it known the ghost employee audits weren't actually being done.

In the end, I realized I was rearranging the deck chairs on the titanic, and switched careers by becoming a programmer. Haven't looked back since.

13.Reginald Braithwaite is a GitHubber (github.com/blog)
202 points by llambda on July 23, 2013 | 63 comments
14.Impressions of Go (bensigelman.org)
187 points by icey on July 23, 2013 | 268 comments
15.Little Lisp interpreter (hackerschool.com)
187 points by maryrosecook on July 23, 2013 | 46 comments
16.Leaked Samsung exFat driver relicensed as GPL (gpl-violations.org)
164 points by synchronise on July 23, 2013 | 195 comments
17.Security Researchers tell court: We do what Andrew Auernheimer did (groklaw.net)
162 points by walid on July 23, 2013 | 110 comments
18.Is This The Future of The Airline Website? (f-i.com)
157 points by ahmadss on July 23, 2013 | 107 comments
19.Ubuntu Edge funding level over time (movebits.net)
151 points by rcaught on July 23, 2013 | 101 comments
20.Falling Crime: Where have all the burglars gone? (economist.com)
151 points by thejteam on July 23, 2013 | 183 comments
21.The Web’s longest nightmare ends: Eolas patents are dead on appeal (arstechnica.com)
138 points by eksith on July 23, 2013 | 50 comments
22.Famous Emacs Users (that are not famous for using Emacs) (wenshanren.org)
130 points by Meatball_py on July 23, 2013 | 82 comments
23.C.S. on the cheap (fogus.me)
134 points by llambda on July 23, 2013 | 16 comments
24.Licensing in a Post Copyright World (pocoo.org)
129 points by llambda on July 23, 2013 | 192 comments
25.PyPy.js: First Steps (rfk.id.au)
129 points by rfk on July 23, 2013 | 49 comments
26.Bootstrapped, Profitable and Proud (37signals.com)
132 points by brainless on July 23, 2013 | 38 comments
27.$99 Parallella supercomputing boards start shipping (parityportal.com)
119 points by WestCoastJustin on July 23, 2013 | 57 comments

It's worth noting that a lot of the apps that Facebook "killed off" (iLike, Social Reader, RockYou, Zynga games, etc.) really did detract from the user experience. Let's take Washington Post's Social Reader as a case study. You had to authorize the app in order to read the articles (that were often loaded with linkbait-y titles), and any time you did read (or click on) an article it automatically shared it with all of your Facebook friends. Zynga is another example; I'm sure I wasn't the only one constantly bombarded with invites to Whateverville. I had to unfriend some people to avoid them, because there was no way to turn them off.

It felt like these apps had found a hack that was taking advantage of the platform, but really this was just the result of the platform being poorly designed itself. The selling point for developers who picked up on it was, "You can make everyone who uses you spam all of their Facebook friends." Unfortunately spam, especially when it's coming from your friends, works like a charm. Facebook eventually had to stop allowing that before it let itself turn into a MySpace filled with little widgets.

Facebook's real problem wasn't just that it wanted to own everything itself, but that it didn't build the platform the right way in the first place.


I worked in a government setting where there was an entire unit of about 12 people called "the island of misfit toys".

They basically took inept employees that were too dumb to give real work to do (but not dumb enough to successfully terminate) and put them into a "Security" unit that allowed salaries to funded by some special source. As far as I could tell, their job was to assign password-reset permissions to "key users" in the field and do some sort of audit function. One of my interns automated their jobs in about 2 weeks when they all retired. They spent most of their time filing discrimination complaints about each other.

The Director was brilliant about it, he'd nominate them for awards for exceeding their KPIs or meeting project milestones, or some other nonsense, which allowed him to expand the group and put them in a separate room.

In the Fortune 500 space, I saw a similar behavior, but for a different purpose... the company did stack-ranking with 5-10% annual layoffs, and the Director-level people would scheme and fight to collect the most inept people possible. When it came time for their unit to be culled, these people would basically serve as fodder for the layoff. It was bizarre to watch.

30.Court: Chevron can subpeona Americans' email data in Ecuador case (motherjones.com)
100 points by Libertatea on July 23, 2013 | 26 comments

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: