skysight-inc/HackerNews huggingface dataset:
As a guy with a much younger sister (11F) who has had an elf on the shelf for 2 or 3 years now, this article literally made me laugh at my desk. If you use your elf on the shelf in this way, I do agree it is slightly creepy. IMO, you should use it as a fun thing for kids at an age where they sort of realize the santa and all the christmas stuff isn't real, but is a fun thing to do; where it is a "lets take pictures of the silly thing the elves did last night while you were sleeping!" Most kids slowly start to realize it is all fake and fun, and at that age it becomes fun to play with the elves as family activity. When my sister first got one, she expressed that it was kinda creeping her out and without having to say out loud that santa isn't real etc., they let her know that it was all just fun and games. I have one that was "assigned" to me as well and honestly find it a blast taking pics with my roommates and I with the elf and sending them to my sister/little cousins. In fact I took mine on a christmas themed barcrawl and we had a blast taking pics of the elf with beers and in hilarious places.

But even if a parent is using them explicitly as a "the elf is watching and will report back to santa", while that is creepy, the step they are taking that it prepares children for the surveillance state is the stupides thing I have ever heard. You are taking a ridiculous step trying to extend what the elf on the shelf experience CAN BE with bad parents to psychologically/subconsciously preparing kids to be OK with the government spying on them as adults.

Even if you were to take that step, I would guess most parents don't use elf on the shelf in that very serious kind of way. It is honestly shitty parenting if anything.
I think you need to leave. Start looking immediately even if you are not sure yet.

BTW I am in the exact same position right now myself. I did not follow what I am going to suggest to you next. But I hopefully have learned my lessons and won't be here again. These lessons were learned through mistakes I made and still make.

1. Always be looking for a job.

This means you should often be checking for jobs in your career field, even if you know there is no chance you would leave. Make sure you keep in mind:

Growth or looking for your next step. Too many people go from one job to the same job elsewhere. They are passing up a great opportunity to change their direction!

What kinds of things/skills others are looking for in an employee with your skillset. Helps you keep yourself employable.

Temperature and pay of your field. Is is waxing or waning in popularity?

This also reminds you to keep your resume and profiles updated.

2. Keep in mind it can be 1-3 months to find a new job that works. So, see #1 again to keep that number at the low end. Careers outside of tech can expect much longer timeframes.

3. It is a numbers game.

There are odds that work in your favor and odds against.

Timing is probably the biggest single predictor of your happiness and pay. For example, I work in IT. If I am applying for jobs in Nov-Dec I know I am probably a backfill replacing someone who is leaving. Backfill gives you great negotiation room but are almost guaranteed to be difficult. Why difficult? Logically, there must be some reason the last guy is leaving. And you will be expected to be at least as good, and lastly you will have to quietly clean up his mess.

Timing is also almost impossible to control. So keep that in mind. See #1 again to improve those odds.

HTH.
How You Know
Pirate Bay copy goes online after Isohunt has cloned the database of it
I'd go with your gut on this one and get out of there as quickly as possible, without something else lined up. I say this knowing this cannot always be the right answer for every dev in this scenario, but if you are one of those who is unwilling to settle in life/career, are talented, and are confident in your ability to get hired if you set your mind to it, well...

I've been there myself, and it is hard to go against the herd telling you to play safe and stay for the security/money. Life is short, make yours worth while and take risks on yourself. Jobs, money, and titles are fungible for those who are truly great practitioners of their craft. This might sound like anti-advice, but a great way to ensure you have all the job prospects in the world going into the future is truly falling in love with practicing your craft and be uncompromising for things that get in your way of that.

One thing I would mention before you fully depart is to go for a "longshot" pitch to your superior(s). Put together a plan for how the department could be put back on track and show you can help reach that vision. Find out why the Rail to Springs change was made, why outsourcing is being preferred, what the department's goals are, your thoughts on moving forward, and how you can lead such a change, etc. Worst case, you know for sure this isn't the right fit. Best case, you get a promotion to lead and bring the change the department needs. If you have plans to be more than an employee someday, you might also enjoy finding out how the series of events lead to a poor outcome came about. Something to take insight of, if you ever venture off on your own (plus, it is interesting to know how the world "works").

I wish you the best in life and career!
This from January of last year : http://www.dailytech.com/TSMC+Were+Far+Superior+to+Intel+and... suggested 16nm at the end of this year. Vs Intel doing 14nm.
It works really well with chicken thighs, too. :)
How far ahead and what days are you traveling and how many days apart is your start and return trip. I fly RDU -> SFO regularly. If I'm 21 days out and my trip is 3 days or more I can get it for $500 - $600. If I reduce it to 2 nights it goes up to nearly $1000. So "cheap" tickets still exist but they're much harder to find than they used to be.
I've never seen this be effective. I worked at a place that had quite a few people leave within a few months, all citing more or less the same issues I did, and still to this day the culture and problems are the same.

The truth is if the problem is management then it's very unlikely any meaningful changes will ever be made.
I'm not sure whether my issue with ATS is the style of the author or its type system, although I suspect the former.

ATS is based on ML (the author started with Dependent ML), but the code has a very imperative feel, leading to statements like "let () = expr() in ..." and "let x = ... in ()".

The stuff at http://www.ats-lang.org/Examples.html is just hideous, by the way.
Ask HN: I'm having doubts about LastPass security, what should I switch to?
I am becoming increasingly paranoid about the applications I use - LastPass is a big part of my daily workflow and I really enjoy it.

However after noticing (https://news.ycombinator.com/item?id=6621560) that LastPass' vault is easily broken into when open, even with strict reprompt settings, I'm starting to trust their security model less and less. I opened a support ticket about the obvious password breach detailed above, and they say it's an inevitable consequence of Chrome's broken security model in extensions.

Well, if that model is broken, I don't want to use it. I find it misleading that LastPass even offers a reprompt option, since it is so easy to retrieve passwords from the application when it is logged in, even if a reprompt is required. Sure, it would slow down unsophisticated attackers, but you don't need to be that sophisticated to change the type of an input.

I have been trying to use it with very fast autologout policies but it very annoyingly asks for a password twice (once to login, once as a reprompt) as well as the Yubikey for every single site. The usability is garbage.

I've been looking at 1Password but I was turned off by their lack of meaningful 2FA support (Yubikey), and their exposure of data if used in any sort of convenient fashion (I would like access from my phone, which is part of the reason I want Yubikey support).

What do you use and what do you like/dislike about it?
This is really cool. Just getting deep in to phantomjs myself, I'm sure this will help a bit :)
"Hey, you have this product with some rough edges. Let's smooth them out."
Good idea! I'll check on that!
How broken is discovery on the App Store?
This study evaluates the accuracy and usefulness of Google Translate in translating common English medical statements. There were some serious errors. For instance, in Polish “Your husband has the opportunity to donate his organs” translated to “Your husband can donate his tools.” “Your wife needs to be ventilated” in Bengali translated to “Your wife wind movement needed.”
What straw man am I arguing?

You say, "Of course you can write reliable software without dynamic allocation." Why is that "of course," if the myth being addressed is that you cannot write reliable software without garbage collection? If you're saying everyone knows that you can write reliable software without GC, and it'll just be expensive and such, then we're in agreement, because that's exactly what I'm saying.
Green made a bunch of mistakes. Drop out of school. Leave a job with a pension when instead he could have moved his mother to New York. It sounds like he just moved without a job or a plan. I know the economy is changing but anyone who just bails on a decent paying job and moves with a family and no job prospects would be in the same situation. There's obviously more behind this story.
Hi Jordan, I'd recommend the following.
The Plesk hoster or VPS owner can prepare the environment by himself. See:
http://devblog.plesk.com/2014/09/plesk-and-ruby-on-rails/
http://devblog.plesk.com/2014/10/plesk-and-django/
(full disclosure, I work for Parallels & had our dev team take a look at this question.)
There's a nicer alternative called "the Kindness Elves".

http://theimaginationtree.com/2013/11/alternative-elf-on-she...

This page links the Kindness Elves to Christian stuff, but it's obviously easy enough to ignore that.
>> "...dangerous wild animals to deal with..."

I come from one of the wildest remaining areas in the lower 48, with a correspondingly high density of charismatic megafauna and apex predators.

On exactly zero occasions have I ever witnessed the police or sheriff's deputies interacting with wildlife. There are specialized (and very heavily armed) government divisions for that sort of thing, and the vanilla police would spark a turf conflict by stepping in.

For example, it is common to see Fish and Wildlife department employees tranquilize and cage a grizzly bear in someone's yard, or to find the Animal Control division running a family of moose out of town, or to see NPS Rangers on horseback herd wild bison. I have even seen crews of municipal snipers deployed to reduce mule deer populations in town.

No sane person would deny very heavy weapons to the men who come face to face with grizzly bears in their daily life. Similarly, the deer sharpshooters should undoubtedly have long and powerful rifles with fancy optics.

But that is certainly not an argument for supporting the militarization and firepower expansion of the ordinary police.
Little things I would teach to my younger software engineer me
I've personally seen coyotes near DC, mostly in the Potomac River corridor northwest of town. The C&O Canal park is a nice long wildlife corridor and is chock full of coyote food like whitetail deer, squirrels, chipmunks, rabbits, etc.

That said, the idea that someone would need to carry a gun in that area to protect them from coyotes is laughable.
The television channels have wider reach. http://en.m.wikipedia.org/wiki/BBC_One#Availability_outside_...: "BBC One is [...] available on cable and IPTV in the Netherlands, Belgium, Switzerland and Liechtenstein"

iPlayer is more restricted.
Just as disruption is the new word for pocketing the money you would have spent on complying with the law, as profit.
So the Tacoma Narrows bridge collapse was indistinguishable from a software failure because all software is the product of humans? That makes no sense.

The MCO failure came about because people took the correct output of one program, then incorrectly used it as input for another program, which then performed exactly as it was supposed to on the bad input.

This is an interesting study in human-computer interaction and how to make that robust, but I don't see how you can possibly apply it to the question of how to make "reliable software."
I'm in a similar situation. Started as a software engineer this summer and it was a perfect work environment: boot-strapped with fast-growth ($50m in 2 years), pingpong/food, good team, $85-90k + 0.2% equity. Then they hired some executives who started changing our roles and let go some of our teammates. I'm still technically an engineer but I'm working on functional tasks that a high schooler is capable of (eg. powerpoints, researching prices, documenting).

Not sure if I should stay just because it's paying well and is mind-numbingly easy work or leave because it's soul-draining and the company is likely to fail with the new management.
"If you are wrong, how would you know?"

What evidence would convince you your opinion should change?
> Older people and disabled people make up a measured percentage
> as well. So less than 90%.

How does being older have anything to do with needing more leg room?
Depending on the disability that may not matter either.

> Additionally everyone benefits from more seat pitch

As an anecdote I'm 183 cm (or 6") and I actually find it really
uncomfortable to sit at the optional incline offered by airlines, I'd
like to either be sitting straight up or lie completely level, nothing
in-between. So I'm not benefiting from it, unless it's getting quite
close to 90 degrees.

> It has nothing to do with "comfort. [...] It is what people need
> so they aren't in physical pain for the duration of the flight.

I'm relatively fine with the current seat arrangement, and I'm happy
that airlines aren't being mandated to increase prices for everyone
due to some government-imposed seat size regulations.

I'm happy that I have the option to choose airlines like EasyJet for
shorter trips which are essentially glorified cattle carts with wings
on them, but which would allow me to affordably go somewhere over a
weekend. If I want more seat space there's always something like KLM's
Economy+, or other similar premium arrangements.

> If airlines want to save some money, remove recline completely.

Aside from the fact that you're entering into a voluntary business
arrangement with the airline, and it's somewhat presumptuous to assume
that you're better aware of how they could save money than they are:

When you're sitting down in a chair your upper body isn't taking up
volume in the space going up vertically from your knees, so there's
space for the seat in front of you to recline into that space.

So this suggestion doesn't make sense. It's not an either-or, maybe
airlines would benefit from removing or reducing recline, but that's
not mutually exclusive with saving money by reducing the space between
seats.
There's a silicone bag available:

http://www.amazon.com/Lekue-1-Liter-Fresh-Bag-Clear/dp/B0049...
These are a great read every month.
This goes both ways.

Sometimes I avoid rereading books for the same reason. There was a Summer where Catcher in the Rye felt very important. I'd hate to reread it under my new, adult perspective. I'd prefer to let it linger in nostalgia.
Snowden, Greenwald, Omidyar: Corporatizing the Means of Dissent
I'm really sorry I will try to dig up the source myself, but I've read basically the opposite argument in a few technical papers -- that GPU is NOT as fast as claimed for many classic test algorithms (actual speed-up is more like factor of 2 than 10) and that the performance gap between traditional CPUs and GPUs is actually lessening.

I'm going to read this article anyway to hear their take & for the learning experience, but does anyone remember any of the counter-arg articles?
These Teenagers Have an Adventure Like the Movies [video]
I concur with this. I use C++ daily and have been for about 20 years, and I still run into gotchas and things I misunderstand all the time.

I feel it's even worse than that, though. There seems to be a culture among C++ programmers to do things in overly clever ways and to push the limits of readability and understandability. Just look at the headers for the standard C++ template library, for example. (I'm currently looking at the ones shipped with gcc.) They don't even use consistent indentation, and have single letter variables that are meaningless to all but those who wrote it. It's pretty frustrating to deal with.
A lot of people seem to believe Microsoft has a moral obligation to protect humanity here and that because they didn't protest before, they shouldn't be supported. I completely disagree with both of those sentiments.

Microsoft has an obligation to stay in business- it will protect its users so that they don't go elsewhere. That's pretty much it. The US Government has begun to clash with this core objective and so Microsoft is fighting back. This is good for everyone, regardless of the profit motive behind it.
I pretty much agree with all your warning signs, so I guess it mostly depends on your love for the product/startup. If you feel compelled and love it, and it is concerning you that this direction is wrong. Which by your account it sure seems to be. Then use the holidays to do some searching, talk to the CEO to feel him out and see where you are in the first week of January. You may find out the CEO is just as confused and dumbfounded as you are, but is trusting the people he hired. Or you may find out that he is a technology chaser and wants to be able to say Golang to whomever asks.

Either way, they aren't overly dedicated to making this happen given their schedule, so I wouldn't bust my ass in this case, but I wouldn't half ass it either. I would give it 100% because it is your reputation that you are protecting here.

Lastly, sometimes we don't see all the details or have all the answers even when the issue looks so clear from our current seat. So asking direct questions without being accusatory or sounding derogatory can really be enlightening. And that new knowledge can go either way of course, but that makes your decision easier.
Cool let me know how it goes. We can go over a plan to iron out some kinks cause I put this together really quickly and there is technical debt that I have incurred.
The structuring of this debt has to be prioritized based on feedback from real users :)
Especially with Dolphin - I was surprised how gripping those progress reports were. And I like how it feels like you're reading about the latest victories of a bunch of superheroes. Which is a nice way of looking at open source projects.
Ha, I'm too disconnected, I never saw these services. 'idvroom' name doesn't ring much but time will tell. They fishing for low hanging fruits, they have other problems to deal with instead...
Curious. Where have you run into them (so I can run the other way :)
So far, all the comments seem to be missing Stroustrup's biggest point: garbage collection only works for memory. Destructors work for everything - memory, file handles, semaphores/locks, database connections, everything.

Garbage collection handles 90% of the problem transparently to the programmer. That's wonderful (really - I'm not being sarcastic here). But the problem is, garbage collecting languages usually don't have destructors, and so you're left having to manage the other 10% of the problem yourself. You have to remember to close all your own files, clean up all your database connections, and so on. Garbage collection usually makes the 90% trivial, at the price of giving you no tool at all for dealing with the other 10% (non-memory portion) of resource management.
The last one. Types are stored as metadata in the object files, those types are verified at build time, and then assumed correct at run time.
What are the odds that this will ever work properly? That it won't break every few months?
This is an amazing approach to making some hard-to-understand aspects of software more visible. This sort of improved information is how software process and tools evolve over time. I look forward to seeing where this project goes.
Ouch! That's really unfortunate that your job has changed so much since new management took over.

I'm on the same side of things -- weighing the good monthly pay vs. finding something I actually enjoy.
I think the absolute dynamic pricing is what annoys me - it's like an inverse Lake Woebegone effect - simply everyone who gets on a plane assumes that they overpaid.

I suspect there is somewhere in the behavioural economics literature a pricing mechanism that has many benefits of dynamic pricing but allows the buyer to feel I control - they know the complete range of fares and the complete range of prices and so feel able to buy without the fear if missin out.
"The same book would get compiled differently at different points in your life. Which means it is very much worth reading important books multiple times. "

I also find that this rings true with movies as well.
Very Cool. Fortunately packaging and "virtualenv" problems are moot due to Maven and Gradle among other things which is why python needed this kind of a solution.
But on the other hand, with that $400 you also get free Global Entry & PreCheck, $200 of airline incidentals per year (in-air food, baggage overages, upgrades, whatever), unlimited free companion tickets when you purchase tickets for yourself via their concierge service, free gold/elite status with most major car rental and hotel chains, and whatever other non-travel benefits there are. For frequent travelers it can pretty easily pay for itself.
Literate programming is a method introduced by Donald Knuth (http://en.wikipedia.org/wiki/Literate_programming). I've stumbled upon it whilst reading Physically Based Rendering, and then LCC: Retargetable C Compiler.

There are some programs that can turn the "documentation" into code : http://en.wikipedia.org/wiki/WEB , but most of them are quite old AFAIK.
I don't like the flavor of this post. It feels very much like navel-gazing and, if it wasn't for the domain name, it likely would have been lost to /newest.

Where is the knowledge here? That we don't have immediate recollection of retained information? Knowledge is based on a beginning and ending context.
One man's price gouging is another man's hazard pay.
Would this help you with bulk requests?

https://news.ycombinator.com/bigrss
I had the same same thing with the much less erudite Stranger in a Strange Land. Re-read it 20 years later and was disappointed. On the positive side, I should consider how much I've moved forward in that time :) or sideways :-S
I remember working on a small in-house C++ library with a colleague.

Being mostly a C programmer, my code in C++ was basically (as he coined it) fancy-C. Then he rewrote my code in "the C++ way," after which the code became completely opaque to me.

My initial mistake was that I expected C++ to be like (or similar to) C, a mistake I believe many of us make. C++ is a lot more complex in scope (not necessarily in a bad way, either) and requires proper learning.

I came to the realisation that C and C++ are not even similar languages. Yes, you can write proper C code in C++ (with a bit of added strictness), but that's not how one should write C++. Also, I think that lot of the "anger" towards C++ is that the the names makes you think it's like C, but then you start learning the language and realise that in fact it is nothing like C on the outside, just on the inside.

Anyway, I'm not hating on C, I actually haven't taken on the quest to learn it properly, and I still rely mostly on C.